Significantly worse Grasshopper performance on Rhino 8 - Warning

Upgraded from RH7 to RH8 recently, I have found some fairly extreme issues with the new software which I’m quite dismayed by.

  1. Switching from between the RH and GH windows freezes the solver, incurring a 10-15 second wait almost every time
  2. Grasshopper Preview does not behave predictably
  3. Locking or hiding Rhino objects appears to clear whatever memory was in the solver

Also just straight Rhino things like, hiding and showing curves caused it to hard crash!

Looks like I’ll have to switch back to Rhino 7 for the time being. My advice to any Grasshopper or Rhino user considering upgrading: hold off until McNeel has fixed the bugs in their new software.


1 Like

Hi Les, Some of this sounds like a plugin conflict or system configuration issue. Can you post your SystemInfo (run SystemInfo in the Rhino command line). Thanks

is this with an existing definition or are you using the new Query Model Objects components?

Can you provide additional detail & context on these? Thanks

Hi Japhy,

This is an existing Rhino 7 script, it is not using any new components.

  • This would appear to be related to how the plugin I am using is ‘drawing’ to the viewport. In that the preview only shows information as far from the camera as there is other geometry previewing, either Rhino or Grasshopper. The plugin is no longer in development so I don’t think this is something fixable.

  • If I select some Rhino geometry and type ‘Hide’ it recomputes the Grasshopper script. This happens using just a regular C# component too.

System Info:
Rhino 8 SR2 2023-12-12 (Rhino 8, 8.2.23346.13001, Git hash:master @ dbefe46c12cda06610a9ab683a211aa3d16f0030)
License type: Educational, build 2023-12-12
License details: Cloud Zoo

Windows 11 (10.0.22621 SR0.0) or greater (Physical RAM: 32Gb)
.NET 7.0.0

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

Hybrid graphics configuration.
Primary display: Intel(R) Iris(R) Xe Graphics (Intel) Memory: 1GB, Driver date: 7-11-2023 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA GeForce RTX 4060 Laptop GPU (NVidia) Memory: 8GB, Driver date: 11-2-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 546.09
> Integrated accelerated graphics device (shares primary device ports)
- 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-2023
Driver Version:
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8188 MB

Rhino plugins that do not ship with Rhino
C:\Users\chris\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\ColorPicker (336da4ab-03d3-42ca-b1fb-313bfd4c1157)\2019.2.15.811\ColorPicker.rhp “ColorPicker”
C:\Users\chris\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\Fologram for Rhino (468a328b-20d9-494b-b9e1-cbe9f827d3a2)\2024.1.56.0\XR.Rhino.Plugin.rhp “Fologram for Rhino” 2024.1.56.0
C:\Program Files\Chaos Group\V-Ray\V-Ray for Rhinoceros\V7\VRayForRhino.rhp “V-Ray for Rhino”

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.2.23346.13001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.2.23346.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.2.23346.13001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.2.23346.13001
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 8.2.23346.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.2.23346.13001
C:\Program Files\Rhino 8\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 8.2.23346.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCode\RhinoCodePlugin.rhp “RhinoCodePlugin” 8.2.23346.13001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.2.23346.13001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”


don’t know if this might be useful, GH recomputing the solution each time a Rhino geometry gets hidden/shown is something that was fixed in a recent release candidate (I was also very affected by that)

in my case,Rhino Options → Update, choose “Release Candidate”, and updating to the most recent release candidate solved the issue entirely

1 Like

Lets get you updated and then try to isolate your issues.

You can get the latest in the Rhino Options>Updates by opting for the Service Release Candidate.

When troubleshooting please disable 3rd party plugins (via Properties>Plugins> sort by plugins that do not ship with Rhino)

What is the no longer developed plugin?

If you are still seeing this after the update please post the steps to repeat, or a file showing the issue.


Hi Japhy,

Yes, the Service Release Candidate update has fixed the issue of the solver recomputing. Was this a known issue when McNeel shipped Rhino 8?

The no longer developed plugin is Nursery. I’ve switched back to RH7 for anything using this.

New issue today, the Grasshopper preview is now inhibiting preview of geometry in perspective mode. I have disabled the third-party plugins as you have asked.

GH Preview On

GH Preview Off

Does McNeel have a returns policy? I’ve always been very happy with Rhino products until now, but I feel as though I am doing beta testing for unreleased software.


1 Like

From the info you’ve provided it looks like your issues are about incompatibility with a plugin that is no longer maintained.

With Rhino the objective is to provide value in the upgrade, not force anyone to buy the latest. We still have plenty of users on Rhino 5 because it works, simple as that.

If you aren’t finding value in Rhino 8 you can always get your monies back by contacting sales.

Thanks for the information Japhy, and for your prompt responses. One last question if that’s okay.

The preview issue documented in the two screenshots has happened after I disabled any other plugins, and the Grasshopper script doesn’t contain any other plugin nodes, nor new RH8 ones. Could this issue still be related to plugins installed for Grasshopper though not utilized in the script?

Hi @Les_immateriaux,

Could you share your problematic GH file with us? I’d like to see if I can reproduce the display issue you’ve reported.


– Dale

Offhand (without the file) i would have to say its because nothing is selected and you have Only Preview Selected objects enabled.


preview (28.0 KB)

This is the script, unfortunately I’m not sure how much use this will be as I can’t share the Rhino reference geometry as it is project-related. I’m sorry.

@Japhy Thanks for the thought, probably I wasn’t specific enough in my post. The two screenshots show a selected box that’s modelled and visible Rhino and is not operated on with the Grasshopper script in any way. The issue is when I have the GH preview on, it hides the Rhino shaded box in perspective.

Can post the file or internalize the geometry and we can take a look. Thanks

1 Like

As I think I mentioned above, unfortunately it’s project work and covered by an NDA so I am unable to share the model data. Which I understand means the script isn’t a lot of use.

That’s okay. I’ll just switch back to 7 for the immediate future and check back into 8 in a few months. Rhino/Grasshopper is easily my favorite program in the world, and I’m very thankful to your company for putting out such a tremendous piece of software. As you said, I was not made to upgrade to 8 but probably I was just excited to see what was new. I should understand that a few teething issues are too be expected, and for the integration into an existing workflow to not be completely seamless.

Thanks again.

Hi Les -

Just note that this issue is not something that we are seeing here, and, thus, is not likely to simply change on your setup during those few months. If you can reproduce the behavior with something that you can share, we can take a closer look.

1 Like