Bug: Rhino Compute - Grasshopper Files with Hatches

Rhino Developer compute.rhino3d
,
1

Hi McNeel,

@AndyPayne

I just started looking into running Grasshopper files through Rhino Compute. It’s really amazing!

However, I’m having an issue with hatches. It seems like the component doesn’t work when solving through Rhino Compute.

Compute - Hatch.gh (6.1 KB)

import compute_rhino3d.Util
import compute_rhino3d.Grasshopper as gh

ghFile = "/Users/johanpedersen/Desktop/RhinoForum/Compute - Hatch.gh"

compute_rhino3d.Util.url = "http://192.168.0.139:5000/"

tree = gh.DataTree("path")
tree.Append([0], [])

out = gh.EvaluateDefinition(ghFile, [tree])
print(out)

This output reads.

{'modelunits': 'Millimeters', 'dataversion': 7, 'algo': '', 'pointer': 'md5_B32EFD2B23411493DACAB904BEA43397', 'cachesolve': False, 'values': [{'ParamName': 'Tx', 'InnerTree': {'{0}': []}}]}

Note that the InnerTree is an empty list.

However, in Grasshopper, it has an output.

image
image1404×1026 114 KB

Version: 8.11.24254.15001

3

Hatches really won’t work with Rhino.Compute until we are able to fully support Model Objects in general. Basically, Hatches make references to other objects (ie. hatch patterns) which are stored in a document. Right now, the way serialization happens, model objects do not serialize other references (only it’s geometry), so hatches, and linetypes, and layers, etc. will all fail because the objects don’t contain the information needed to fully build out the data type. We have been working on this and I think we are close to getting Model Objects supported. However, until that work is fully tested and ready to be released, I’m afraid that Hatches really won’t work in Rhino.Compute. Sorry.

1 Like
4

Hej @AndyPayne

Thank you for getting back to me. The introduction of model object in gh is amazing! I’ll look forward to rhino.compute support. Is there a way to follow the state of the implementation (you track or GitHub)?

best,
Johan