Is this a new system / did you just start using it with Rhino or was this working correctly before and the crashing started happening when something changed?
I’m trying to understand if the crashes have something to do with the Ladybug Tools (and, perhaps, version 1.4.0 specifically), or if you are also experiencing crashes when just using Rhino to create models.
When Rhino crashes, does it pop up a crash reporter, and, if so, are you sending that in?
The GPU in your PC is a bit underpowered to be running Rhino but that alone shouldn’t be causing a crash. Do you use your laptop screen as well, in addition to the external screen? If your crashes are more general than just using Honeybee, I’d at least consider updating the drivers for the Quadro P520 card. Don’t rely on Windows tools to check for updates - the Rhino Notifications panel has links to the download page for your card.
-wim
No, this is not a new system, but we are trying to use honey bee for the first time on this laptop and my colleagues’ laptops as well.
Using just Rhino to make models and any analysis using Ladybug works great, I experience this crash only with Honeybee.
Rhino does not create a popup, it just crashes without any notification. I have updated the driver via Rhino->Notifications, but still, I have the same issue.
I’m afraid not, no. This sounds like something that @chris or @mostapha might have ideas about.
Can you perhaps narrow down which component leads to a crash?
Also, I take it that the Ladybug components that you are using successfully also are from the 1.4.0 release?
-wim
Also on the other hand I read @piac 's post and tried enabling the (subprocess_test.gh). The grasshopper script works but unfortunately, both Honeybee components and Cumulative Sky Matrix crashes along with Rhino.
It’s also possible that the UUID module might be to blame as described here. Let’s see if the Grasshopper definition above works and, if so, I’ll confirm that the problem isn’t with UUID before I try to fix things.
Woohoo! This is looking very promising, then. We just need one final test to rule out the use of UUID as the culprit. Can you try running the following Grasshopper file and send a screenshot of the output?
Hi @chris,
I tried loading the “uuid_test.gh”. Unfortunately, the Rhino and Grasshopper crashes just like before when I tried loading Honey bee components.
I just wanted to second what Mostapha said. It seems this issue is different than I originally thought and you should try deactivating your antivirus, @Prethvi .
Hi @mostapha ,
We are using SentinelOne and our IT team said it is not possible to turn off this software. However based on the link you shared above, the IT Team added the path to rhino and rhino.exe to the exclusion list. Despite the effort, the Honeybee component is crashing in my system.
There’s only so much that we can do if your IT insists on using settings for the antivirus software that cripple the usability of your computer. It looks like @Paul1 said that they also modified some settings for error suppression:
Just as a note for future users that encounter this… the problem is related to method 1 uuid1() in uuid.py as it accesses the mac address.
Honeybee doesn’t actually require uuid1() method of generating guids, and it uses uuid4.
If you modify the uuid.py in the Rhino/plugins/ironpython/lib folder … comment out or delete the code related to scanning and accessing the address and just leave random inside the uuid1() def instead. The script wouldn’t need to attempt to call this.
and placing components should now be possible again
NOTE reinstalling Rhino will reinstall the uuid.py so it would be good if Honey bee made an adjustment to avoid importing all of uuid.py
so basically changing the def uuid1() to only use a random generation for the node component, and removing the defs above related to getnode will form a valid guid in accordance with RFC4122, but not affect Honey bee anyway since it calls uuid4()