Hi all, I am wondering if this happens to others before or after the upgrade to Rhino 8:
When I hide or show objects (via commands ‘hide’ or ‘show’ in Rhino) that are set as references in grasshopper, the canvas freezes, and so does Rhino. This happens with any viewport style (wireframe, shaded, rendered, etc.).
I’m working in a file I’ve had for a while. All things normal - however after the Rhino 8 upgrade from the beta I’ve had the issue I mention above. Sometimes the software won’t respond again and I have to quit it and start over.
Again: this happens when I hide and/or show the referenced objects in Rhino while the grasshopper file is running - however never deleting the objects, which would obviously affect/freeze the entire algorithm.
Any clues?
Do I have to go through the painful process of finding a possible ‘culprit’ within grasshopper? The only errors I have always had present in the file are some failed curve offsets and some ‘degenerate’ (for whatever reason) extrusion - nothing wrong with the extrusions but GH still warns of that.
Can you run SystemInfo in your Rhino command line and post the results?
One way to quickly test if it is a Grasshopper plugin causing the issue would be to start Grasshopper from Rhino with the GrasshopperLoadOneByOne and say no to all (especially the obscure or outdated ones)
I don’t have many plugins in use but not sure I can do that? That means disabling ALL plugins, including ‘basic’ ones like MeshEdit, or Kangaroo 2 - at that point many things wouldn’t be working in the script…how would it be helpful?
What exactly should I do there? Say no to all the plugins then run the script anyway?
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 1.3e+02Gb)
.NET 7.0.0
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro RTX 5000 (NVidia) Memory: 15GB, Driver date: 11-9-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 546.17
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port 0
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: None
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 11-9-2023
Driver Version: 31.0.15.4617
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 15 GB
Rhino plugins that do not ship with Rhino
C:\Users\MONSTRUA\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\RPC\0.0.11-beta\RPC.rhp “RPC”
Ok I did run the ‘load one by one’ command and said no to all, and it says I have 185 ‘unknown’ objects, most of which come from the ‘plug-in’ grasshopper:
This is sad - how do I tell the grasshopper file to bring itself up to date so it works properly? I don’t get the option to ‘upgrade components’ for whatever is ‘old’.
Do I have to ‘manually’ replace these place-holders (note how many below) with their ‘new’ version of themselves?
All things seem fine except the performance of the algorithm has been severely affected after the upgrade - prior to that I was working the same script in the WIP then BETA releases.
*Here’s some more material - I’ve duplicated the script and deleted almost everything to try to isolate the case from the start with the referenced shapes I occasionally hide.
Notice the little ~1 second lag when I hide the objects in Rhino. Not a big deal - just new/strange for a machine this capable. The preview goes blank then already-previously-previewed objects are previewed again (however I never “unpreviewed” them in grasshopper). This wasn’t happening before:
Then, if I hide the objects in Rhino, then undo that (Ctrl+Z) so they come back, the Grasshopper window glitches for a second with a white ‘vignette’ around it until I click it:
This second video is pretty much what I’m dealing with - you can see when the white vignette appears, the grasshopper wires turn ‘orange’. It quickly goes away because it’s only a few components, however when the actual algorithm is present, hiding the objects in Rhino causes the entire script to become ‘orange’, freezing the program.
I have tried a few things and it seems the issue occurs regardless of the file I am working with.
In summary:
The GH canvas freezes when I undo a ‘hide’ command - it doesn’t matter what the referenced object is. If I use ‘show’ instead of CTRL Z, the freezing doesn’t happen.
However the issue somehow ‘scales up’ ? If I have the full algorithm loaded, simply hiding an object can trigger it, I don’t even have to undo the command.
This issue did not manifest in the WIP/BETA.
It doesn’t happen in R7 either.
I did a clean reinstall of Rhino 8 and deleted Rhino 7 as well.
Got rid of all plugins.
The issue persists:
Reference geometry from Rhino - set within grasshopper
Hide geometry in Rhino, then undo hide
GH canvas freezes (white vignette around it) until clicked
extra:
I realize the same bug is triggered via Ctrl Z of other things like:
scale the object with gumball, then undo that, GH canvas freezes.
Sometimes if I internalize the object, the issue goes away but if I create another object and reference it, the issue returns.
Repairs are better than a re-install. This is done in Windows by going to the Add or Remove Programs then Modify the Rhino 8 install and select Repair.
Just to make sure all setting are fresh please run the Reset command in Rhino 8.
Then run SystemInfo and post again and an image of your GH canvas as well please. Thanks
For some reason Rhino does not show up in the Control Panel and it doesn’t show up in the ADD or Remove section for Windows. So I had to double-click the install file for the prompt to repair or modify. I must say I’ve installed Rhino in my additional SSD, not in the usual C:Program Files - does this matter?
Here’s the result from SystemInfo:
Rhino 8 SR1 2023-11-21 (Rhino 8, 8.1.23325.13001, Git hash:master @ 8a4a437248efac5d9cb04d3904481b83e4c23a64)
License type: Educational, build 2023-11-21
License details: Cloud Zoo
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 1.3e+02Gb)
.NET 7.0.0
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro RTX 5000 (NVidia) Memory: 15GB, Driver date: 11-9-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 546.17
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port 0
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 11-9-2023
Driver Version: 31.0.15.4617
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 15 GB
@René_Corella When you say it “Freezes” after an UNDO, are you referring to the white border that shows up on the GH canvas (until you click back on the canvas)? If so, that was reported earlier this week (also in this thread) and I believe should now be fixed in the next 8.3 release (which should occur next Tuesday). This might be why @Gijs is not seeing it in 8.3.23342.10001 but is seeing it in 8.2.23341.12001.
Hi there,
I suggest changing the thread title to something like “Grasshopper canvas border turned white after undo”. I suspect more people are looking for this bug using the “white border canvas” keywords. Took me a bit to find this.
So I have the same issue and it’s making Rhino a pain to work with. Simplest example:
Draw a bunch of connected lines inside Rhino. Join them together. Open GH, put a curve battery inside GH. Set the joined polyline as a reference for the curve battery. Back to Rhino, undo the Join command. GH canvas border turns white and the crv battery won’t accept any other crv/polyline/line object as a reference from the Rhino viewport anymore. It does not show an error, but says it is empty when you try to “Set xxx curve(s)”. Fix is to restart Rhino. This is on both Mac and Win, Rhino says I am up to date.
You are up-to-date on service releases. Those generally are published once a month. In between those, however, there are weekly public service release candidates. If you change the update frequency in the Rhino options, you’ll be able to get a 8.3 release.
-wim
Thanks Wim, I can confirm basic issue I described is fixed on both Mac and Win with the candidate release. Haven’t tried more complex object referencing issues.
