Rhino and Grasshopper Not Responding on File Opening


Yesterday I was working on a big Grasshopper file… today, I can no longer open it. The Rhino file is still slow to open, and when I try to open the Grasshopper file the app goes into “Not Responding” mode indefinitely.

It’s not a performance problem-- I’m only using 29% of CPU and 52% of memory when trying to open the file.

I am able to open small Grasshopper files, though it is slower than usual.

It’s not a virus-- I just performed deep cleans of my system this morning.

Here are the sizes of the files:

Here is the Grasshopper file:
20221126 - Fractals.gh (3.1 MB)
(Sorry, nothing is internalized… I can’t open it to edit it!)

Here is my Rhino system info:

Rhino 7 SR24 2022-11-4 (Rhino 7, 7.24.22308.15001, Git hash:master @ cb2ad12922ceb989b185972675bb705a00abb97d)
License type: Educational, build 2022-11-04
License details: Cloud Zoo

Windows 11 (10.0.22621 SR0.0) or greater (Physical RAM: 16Gb)

Computer platform: LAPTOP - Plugged in [100% battery remaining]

Hybrid graphics configuration.

  • Primary display: Intel(R) UHD Graphics (Intel) Memory: 1GB, Driver date: 9-24-2020 (M-D-Y).*
  • Integrated graphics device with 3 adapter port(s)*

  •    - Windows Main Display is laptop's integrated screen or built-in port*
  • Primary OpenGL: NVIDIA GeForce RTX 2070 with Max-Q Design (NVidia) Memory: 8GB, Driver date: 11-2-2020 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 457.20*
  • Integrated accelerated graphics device with 4 adapter port(s)*

  •    - Video pass-through to primary display device*

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-2-2020*
  • Driver Version:*
  • Maximum Texture size: 32768 x 32768*
  • Z-Buffer depth: 24 bits*
  • Maximum Viewport size: 32768 x 32768*
  • Total Video Memory: 8 GB*

Rhino plugins that do not ship with Rhino

  • C:\Users\orion\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\Lumion LiveSync for Rhino (839d6175-32d1-4ffe-a0a4-b7fb43cf0ff5)\2021.3.25.899\Lumion\Rhino 7.0\LumionPlugin.rhp “Lumion LiveSync for Rhino” *

Rhino plugins that ship with Rhino

  • C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.24.22308.15001*
  • C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit” *
  • C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.24.22308.15001*
  • C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.24.22308.15001*
  • C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI” *
  • C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots” *
  • C:\Program Files\Rhino 7\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 7.24.22308.15001*
  • C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.24.22308.15001*
  • C:\Program Files\Rhino 7\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 7.24.22308.15001*
  • C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.24.22308.15001*
  • C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse” *
  • C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”*

I’m really desperate for a solution at this point… I’m grateful for any help or suggestions!

You’re probably having your script do something very, very heavy. Not everything in Rhino nor Grasshopper is multi-threaded, thus not capable of using 100% CPU utilization.

I don’t have anemone nor ngon plug-ins installed, so can’t further help there. But try opening your GH file without opening the 3dm first, then disable looping and see that you don’t generate more than you need.

Disabling preview of all components before reopening with 3dm file might help as well, in case there’s lots of meshing going on.

1 Like

I managed to finally get the file open after letting it run during the night… I think part of the problem was a Solid Difference component, which I deleted. I will still have to perform the Solid Difference at some point, though. When I eventually do that, would you recommend turning off the preview for everything?

What does it mean for something to be “multi-threaded”?

The base geometry is a simplified fractal… so the Anemone loop is kind of the basis of everything. I’ve reduced the number of iterations of the loop, which helped a lot.

Turning off preview doesn’t help much on a boolean operation component. Maybe it’s just because your geometry (fractal) is too complicated and it takes a lot of time for Rhino to calculate the operation.

1 Like

Good to know. Unfortunately, I can’t reduce the complexity of the fractal too much without… you know, destroying the point… :frowning:

I simplified it from this image to thisimage

It helped a lot, but… gah.

The more geometry you put through certain actions like boolean operations the longer it is going to take, probably on an exponential scale.

You probably will just have to let it sit for a good time longer. It easily can take hours for such operations to complete if you have a huge amount of objects that partake in the booleans.

If simplifying doesn’t give what you need you could maybe try breaking the work up in steps in different files, like you did with the solid difference essentially.

1 Like