This is a post mostly to let @eirannejad know about a new bug that was introduced with Rhino 8 SR3. I searched the forum but it doesn’t seem to be reported yet. Also, there is a simple workaround for it but, from what I can tell, it affects all Ladybug Tools users of Rhino 8.3. So it’s more of a large-scale annoyance than a real blocker for people.
The issue is that the first time a Legacy GHPython component is dropped on a Grasshopper canvas of a given Rhino instance, we get the following:
1. Solution exception:Object reference not set to an instance of an object.
Disabling and re-enabling the component makes the message go away and every subsequent GHPython component that is dropped on the canvas after that will work correctly. So it’s just an issue that affects the very first Legacy GHPython component on the canvas for a given Rhino 8.3 instance.
Since all Ladybug Tools components are Legacy GHPython components, you can imagine that this gets pretty annoying for us after opening Rhino for the upteenth time and having to find and rerun the first GHPython component that ran on the canvas. So we would be very appreciative if this could be fixed soon.
@chris12 Do you see that in any other component in GH1? I can replicate this but only on the legacy-legacy script component (the first one from bottom on the list)
I have not found this message on any other component so far. Only the first legacy GHPython component from the bottom of the list, which is what we use as the base for all Ladybug Tools components.
This used to be - probably still is - an issue in Rhino 6 and 7 on macOS, when launching a Grasshopper file from Finder, without opening Rhino first.
The file would usually launch Rhino, then Grasshopper, and when the GH file would contain a now legacy GHPython component, this exact exception would pop up.
