I am getting an error with my code in Rhino Compute, and it tells me it’s a tree item component with a missing path and its ID, but all components on the canvas are fine, so how do I find a GH component with its ID as listed in the Rhino Compute console, so I can solve the error?
Rhino Compute console error.
Also, if I close the console window, how do I get it back without restarting Rhino?
Hey @AndyPayne
Is this something you could help me with? The same issue came up again today when the Fillet edge component breaks on Rhino.Compute, but works in the code without errors.
If you know the instance guid of a component (which is what is being returned as that long string of characters after the “Tree Item”), then you can simply open the Find dialog and enter it and it will automatically point you to the component in your definition that matches that id. To get to the Find dialog, go to Edit → Find… Then enter the guid into the search bar.
This is great, thanks. Super easy way to debug my code.
The other question was, I know I can get the Rhino. Compute console to launch when Grasshopper starts, but is there any way to relaunch it if you accidentally close it, rather than minimise it, without restarting Rhino/Grasshopper again?
EDIT :
Ok, so it’s great you can debug from the Rhino Compute window, but how do I check why the components before are not working but not throwing up an error, ok, this was actually the Python component, when they work fine in the open Grasshopper script, but fail to work as expected in the compute version? How can I debug the headless version if I can’t see what’s wrong with it!
See this thread about the Python component. RhinoCommon CreateSpiral method works in GH but fails in Compute/Hops
The other question was, I know I can get the Rhino. Compute console to launch when Grasshopper starts, but is there any way to relaunch it if you accidentally close it, rather than minimise it, without restarting Rhino/Grasshopper again?
If you accidentally close your Rhino.Compute console window and you need to get it back, you can hit the Child Process Count button in the Hops preferences section. This should start a new instance which will spin up a new child process.
Great, Thank you!! you have just saved me a lot of Rhino restarts.
