Hi,
I’ve installed Drafthorse from the PackageManager v1.1.31.
I was trying to create a script creating a layout from a bounding box from all the geometry in rhino.
Here is the Script
LayoutManagement.gh (22.3 KB)
But it keeps crashing Rhino when i run the provided example file too.
What else should i post here in order to solve this?
Thanks @sftgen - can you remove the visualArq components from the script and internalize any relevant geometry? I can’t replicate your conditions with the script in its current state.
Thanks, Jo
@sftgen Please also share your Rhino file - Drafthorse has had some bugs in the past with Rhino unit settings, which are set separately for the document (aka drawing space) and layouts (aka paper space)
Untitled.3dm (4.5 MB)
I have the same issue without VisualArq components, because the same thing occurs when i use the drafthorse example files provided. Please check the rhino file provided.
Hi again, did you manage to find out what’s going wrong? Should I send additional files?
can you provide your system info - the output of the _SystemInfo command in Rhino?
The reason I want a “clean” version of your grasshopper script is so that I can have as close to exactly the conditions that are causing your crash. If I can repeat it on my system then I will have a much better chance of being able to fix it. If I can’t repeat the crash, its very hard to know what’s wrong.
system_info.txt (2.9 KB)
Please find attached the system_info.
@sftgen I haven’t been able to figure out what’s going on. I can open your file and definition and the Drafthorse components work as expected. I can’t replicate the crashes that you mention.
You could try a clean load of grasshopper (_GrasshopperLoadOneByOne) where you exclude all non-native plugins other than Drafthorse to see whether it might be an issue from an interaction with another non-native plugin. Other than that, I don’t have any other ideas right now.
@Japhy - do you have any additional troubleshooting recommendations?
for troubleshooting purposes lets disable these Rhino plugins that do not ship with Rhino.
Go to File>Properites>Plugins to disable then restart Rhino for the settings to take effect.
Rhino plugins that do not ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo” C:\Users\user\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\Karamba3D\3.1.41125\net7.0-windows\Karamba3D_LicensePlugin_Rhino8.rhp “Karamba3DLicense”
Hi, @jokamm it seems that when starting Rhino without VisualARQ and Tibidado loaded, the drafthorse new layout is executed smoothly without Rhino crashing.
When loading only Tibidado without VisualArq Rhino crashes when grashopper starting prior to any drafthorse involvement.
When loading again Tibidado with VisualArq Rhino does not crash when grasshopper is starting but again crashing when executing example layout creation with drafthorse.
When loading with Tibidado and VisualArq but with Landsdesign unloaded Rhino does not crash when grasshopper is starting but again crashing when executing example layout creation with drafthorse.
When loading with Tibidado and Landsdesign but with VisualArq unloaded Rhino crashes when grasshopper is starting prior to any drafthorse involvement.
Please note this: After grasshopper initialization when executing layout creation from drafthorse examples, it actually does something, it created the layout and then it laggs for a bit and then crashes.
I hope this helps and there would be a solution as i need to use drafthorse for a solid workflow.
@sftgabriel Thanks for all that testing! Hmm… that’s a lot to take in. I don’t have or use any of those plugins, so I won’t be able to test for these specifically. If you want to experiment with the Drafthorse code, all of it is available, open-source, on the github page. That’s the best I can do for you short term.
at the moment i do not have the confidence of messing around with the code. Do you think that I should report this to the Visualarq team or is this a bug or misfunction related to Drafthorse code? From the testing, i understand that the problem is related to VisualArq plugin, am I wrong?
It seems to be a combination of the multiple plugins, so I’d guess that VisualArq will not see this as “their” problem. However, if I’m understanding your post & testing, there do seem to be some issues with the individual plugins that could get us closer to solving the combined problem:
Maybe Tibidado would have some insight on this issue?
The other approach I would take to debugging would be to recreate the drafthorse components as C# Script components on the canvas. This would lose some functionality that is built in to the compiled plugin, but might help to identify which parts of the code are conflicting with the other plugins. I have a version of these somewhere from early in the dev process - they are behind the current version on github, but I’ll dig them up this weekend and see whether I can get them up to date for you. They won’t have all the functionality, but they may help us narrow in where the conflicts are.