Released Version of Rhino 8 locks up adding panels

I bought the upgrade version of Rhino 8 and was previously using the WIP version. Now Rhino locks up almost immediately when trying to add or remove panels to the right sidebar.
My PC is more than capable (i9 12900K 64gb RAM MSI Radeon 8gb Video card)
Any thoughts why this might be happening?

Hi David - please run the SystemInfo command in Rhino and post the reasults.

-Pascal

Pascal, Here it is. Thank you.

Rhino 8 SR0 2023-10-31 (Rhino 8, 8.0.23304.09001, Git hash:master @ 20e15cf9bd66e6676f849f22e485cb3e82a8beac)
License type: Commercial, build 2023-10-31
License details: Cloud Zoo

Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 64Gb)
.NET 7.0.0

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: Radeon RX Vega (AMD) Memory: 8GB, Driver date: 10-17-2023 (M-D-Y). OpenGL Ver: 4.6.0 Compatibility Profile Context 23.11.1.231017
> Accelerated graphics device with 7 adapter port(s)
- Secondary monitor attached to adapter port #0
- Windows Main Display attached to adapter port #1

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: ATI Technologies Inc.
Render version: 4.6
Shading Language: 4.60
Driver Date: 10-17-2023
Driver Version: 31.0.21905.1001
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 8120 MB

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.0.23304.9001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.0.23304.9001
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.0.23304.9001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.0.23304.9001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.0.23304.9001
C:\Program Files\Rhino 8\Plug-ins\RhinoCode\RhinoCodePlugin.rhp “RhinoCodePlugin” 8.0.23304.9001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.0.23304.9001
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”

Hi David - nothing jumps out at me here - does the problem you describe happen in a new, empty file? Does it happen with any panel you try to add or remove?

-Pascal

It happens when I right click on the right panel and chose to add a panel. If I add them from the menu bar at the top it seems to work. Something about that pop up selection panel that is weird.

This panel. Also, it happens whether its a blank document or a part document.

Hi David - when this lock up happens, please run TaskManager in windows and find the V8 process - right click and choose ‘Create memory dump file’

This will take a moment and generate a gigantic file - Windows will tell you where it is:
image

Please zip that file and upload to my attention to
www.rhino3d.com/upload
You probably want to delete the original and the zip on your machine once uploaded. Note for very large files, upload can fail so it may take a try or two, or three…

Thanks.

-Pascal

Okay, I’ll do that. thank you.

Hi David, I have the dump file, thanks, I am trying to recruit a developer to take a look.

@David47 - some questions from the developer.

  • does the Properties panel come into play with this or can it be any panel that is being added or removed?
  • Is the container with the panels docked - I think yes - and does it behave any better or differently if the whole thing is un-docked and you do the same things?
  • a for-five-year-olds blow by blow of the exact steps would be helpful - the problem may occur in some seemingly inconsequential detail in your process…

thanks,

-Pascal

So I open Rhino from a fresh install and in the right panel I try to add the panels I use regularly by right-clicking to open the popup box. I usually chose the following: Render, Materials, Lights, Textures, Environment. I might select one or two of those before the mouse stops responding. Then I have to wait several minutes before it will respond again, maybe 2-3 minutes. But when it does respond, it’s choppy and unusable, I generally have to restart. It’s like what happens when something is using almost all the computer resources. But I can never check it because the mouse is so choppy and the system is so unresponsive that I have to restart, killing everything. As mentioned, this is a Core i9 12900K with 64 GB of DDR5 RAM, it’s not a wimpy machine and it only happens when I try to use Rhino. It does not happen with any of my Adobe software, Blender, or Plasticity 3D.

The panels are docked, I never tried to undock them.

I thought it was isolated to the panels on the right side because I was trying to set that up first. But it happened when I was trying to make some changes in the properties panel and I also made not when selecting any of the menu items (File, View, etc…), Rhino was slow to open them, and/or the dropdown would open but it would take a second or two before the mouse could make a selection.

A couple of things to note. It behaved normally with Rhino 7 AND with the WIP versions of Rhino 8, only the commercial version is misbehaving.

Also, The other things running are usually just Microsoft Outlook and YouTube playing in Chrome.

I think that’s it. I’ll add more if I think of it.

P.S. I have Rhino 8 installed on my Macbook Pro M1 and it runs without issue, its only on this Windows PC that I have problems.

I’ve attached my “about this PC” info as well.

Corrections on the third paragraph. Illegible.

It happened in the properties panel when trying to make changes there. Also, I noted that when selecting any of the menu items (File, View, etc…), Rhino was slow to open them, and/or the dropdown would open but it would take a second or two before the mouse could make a selection.

Hi David - thanks. This bit catches my eye -

they are all ‘rdk’ panels - If you open/close other panels - Layer, Display, Help, Properties, MacroEditor, BoxEdit, MoveUVN and none of the ones you point aout above … do those behave better?

-Pascal

I closed all panels in that group. Then I reopened the following with NO issue.
Layer, Help, File Explorer, Properties, Tutorials, notifications.

Following this I again closed all the panels in the group and opened the following WITH LOCKUP ISSUES
Render, Materials, Textures, Material Library (this is the one I got to when it locked up).

(BTW, in notifications it says “AMD Video Driver Update Recommended” but I updated it to the current version and it still says that). AMD Radeon Vega 64 for FYI.

Hi David - thanks for testing, that is very useful infomation.
@David47 I might try a clean install of the gpu drivers - if the hang does occur on material library panel, then it may be trying to generate preview images.

-Pascal

I uninstalled all the video drivers and reinstalled fresh. No change.

You might have a second look into the clean install of video drivers under windows.
This is nearly impossible to do without 3rd party software as windows interferes with the process.
In short: if you have problems with your graphic card driver you may need to use the free utility DDU Display Driver Uninstaller (DDU) V18.0.6.9 Released. | Wagnardsoft
to properly remove your old driver and then cleanly install new drivers.

Here is a Youtube video explaining the process:

I used the amd uninstaller and cleaner tool which only works when windows is in safe mode.

That sounds like it does similar things as DDU.

I did try DDU, and it DID make a difference. Although laggy because of the Windows default display drivers, RHINO did NOT lock up when adding or removing the panels.

After this, I reinstalled the AMD drivers, but NOT the full Adrenalin version, just the driver alone. This seemed to work.

This could be an isolated thing that is only affecting me but it is worth noting that the Full version of AMD’s Vega driver software, Adrenalin 23.11.1 released 11/2/23 appeared to cause an issue.