Unable to convert resthopper data

Hi - I’m getting an error from hops “unable to convert resthopper data” while trying to use a large definition which has some C# and python components. I’m getting a partial response (2 of the 3 geometry outputs returning curves)

Details:
it works as a definition and as a cluster.
running hops 0.16.0

2 ouputs that are coming into grasshopper: RH_OUT:TWEEN LINES, RH_OUT:ORIGIN CURVES
the output that isn’t : RH_OUT:IMAGELINES (but it still shows geomtry in the json just not coming into grasshopper)

my response json doesn’t show any errors and looks to return
solveResponse.json (9.0 MB)

image

I can’t post full script, but can send partial if helpful.

The 9.0 MB JSON file is useless without code that reads it, eh? Hops code.
What do you see if you connect text panels to the outputs?

hey - here is the value out
image

The JSON file is semi readable, the object data looks correct for the return type to make what i’m expecting - it should be producing rectangles.

its unclear to me where the issue is with what HOPS is expecting because it looks like everything is being returned in the json object.

UPDATE:
process of elimination, started working backwards moving things outside the scriptand found that something about this highlighted group seems to be culprete of the error - at least if i return the rectangles, if i output the driving values and move this construction of rectangles outside the hops definition everything works correctly.

Hi there - I have also had a very similar issue to this but found I only got the error when I tried to return a box. Every other bit of geometry - mesh, curves, closed brep cylinder - worked fine. I’ve attached my test script to this reply
test_function.gh (9.2 KB)
The issue only occur when I plug the box rectangle into the geo component (ignore the volume bit, was just testing the number output functionality)

1 Like

Same issue for me, if i converted the Box to a Brep then the Hops component worked again.

Hi @William_Curwen and @RD3,

The problem transferring boxes is solved, not sure if will be available in 8.1 or 8.2.
@AndyPayne knows the details.

@RD3 @William_Curwen Actually, I did need to make a change to the rhino.compute code in order to support boxes as a data type. I’ve just pushed a new build of Hops (0.16.4) which should rectify this issue. Please try to install the latest version of Hops via the package manager and let me know if this fixes the issue for you.

Hi @nbarnes I’m sorry for coming to this thread so late. Rectangle3d was added as a data type supported by Rhino.Compute back in Aug 23’. I believe if you update to the latest build of Hops/Rhino.Compute that this issue should be resolved now. Sorry again for the delay.

2 Likes

Works for me now, thanks!

1 Like

Thanks Andy!

Hi Andy, loving the Hops plugin, been using it for months supercharging my GH workflows. Is 0.16.4 specific to R8 because in R7, latest version on Package Manager is 0.16.2 on my machine.

Yes. There are different versions of Hops/Rhino.Compute for Rhino 7 and Rhino 8. Rhino 8 switched to .NET 7 which required us to rewrite some things for Rhino.Compute and thus there is a change in the versions and how they work.