Hi everyone,
I recently started to use compute to power a web configurator, and I found that for some reason there are a couple of very simple components that constantly fail in compute. My findings are cull pattern, dispatch, round to nearest and offset curve (only the extended one).
I’m using rhino 8 for Windows, both on the vm and my pc.
Anybody has a clue as to what am I missing? Or are they known bugs?
Thanks a lot!
Tomer
Hi תומר ניימן,
We’ll need more info to help efficiently.
Please run systeminfo in Rhino and post the results and a small example of what if failing for you. thanks!
Is there a Grasshopper definition that you could share so that I could test this on my machine? Are you using Hops (and rhino.compute with the Hops plugin)? Or are you building rhino.compute from the source code? If you’re using Hops/rhino.compute, what version are you using?
Thanks for the reply.
I have here attatched the exact workflow that’s failing, and the full file.
Everything is working fine on my personal PC, using rhino 8. As the file is solving in the VM (also rhino 8, no hops) i can see in my configurator console that the dispatch componenet has an output of 0 items.
Thank you again,
Tomer
origami lamp for forum.gh (40.3 KB)
I haven’t loaded this up yet, but are you trying to have rhino.compute return the points from the dispatch component? If so, you need to pass them into a Context Bake component (a separate bake for each output)
Yes of course, this is just a middle part of the definition, the end is connected to a context bake. When the end didn’t produce anything I traced it back to that dispatch component. When I switched it with a different component it worked.
