This new hops thing looks really awesome and I love the concept. However I get some strange errors that I cannot figure out the reason for when I run it. The error message that I receive is just that the definition is “unable to solve on compute” like in the picture below.
When I try the same input for the script itself it works fine and it only crashes for specific inputs (probably like 1/3 of the times for this particular definition.) It always seems to crash for the same inputs though, even when I have the cashe data options turned of so my interpretation is that it is not random but has to do with the specific data it’s fed.
I’m using the latest release candidate of Rhino, 7.5 and I have a bunch of toolkits installed. I’m only using native grasshopper in the definition however. Any ideas on what could be the problem here? I’m attaching the definitions if you want to try it out.
Not sure what your error is, but to help you debug you can disable ‘Hide Compute Console Windows’ in your GH preferences. (Thanks to @stevebaer for this tip).
Hi Erik,
Your sample works on my computer, so I suspect a 3rd party component is at play. I would suggest showing the compute console window and let me know if you get any errors.
Thanks for this tips - it’s a really useful trick and makes it much easier to debug. Do you know if there’s an easy way to figure out what component the error is referring to? Is the string, e.g. 7e755336-c455-471f-bd07-7c38c32fd39a, the GUID of the component causing the error?
Thank for your reply. I’m planning to try removing all the 3rd party libraries and add them back one by one to see if one of them is causing the problem. I’ll write to you if I find anything interesting.
Hey @erikforsberg95. Off the top of my head you can use Metahopper to expose the list of component GUIDs within the GH definition. You could search the list for the correct GUID and dispatch the component name from the DocInfo list to find the correct component. I think you can use Metahopper to highlight GH components as well, so then you should be able to quickly find the problem component.
