Hi.
I have a permanent issue of crashing while trying to rotate view in active Detail of layout.
I’m talking about v8 WIP.
I’ve sent a crash report already.
Is that a known issue? And how can I find if some issue is already reported?
I didn’t find this problem on YouTrack.
Thank you.
Please run SystemInfo so we can see what computer resources Rhino sees.
What are the specific steps to follow to repeat the problem?
Based on your description, I can not repeat the problem.
Steps are:
Here is a system info
Rhino 8 SR0 2022-12-27 (Rhino WIP, 8.0.22361.13135, Git hash:master @ c51c915253258ed1c83aaed86199b3e81cefede0)
License type: Commercial, build 2022-12-27
License details: Stand-Alone
Expires on: 2023-02-10
Windows 10 (10.0.19044 SR0.0) or greater (Physical RAM: 32Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro RTX 5000 (NVidia) Memory: 16GB, Driver date: 1-28-2022 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 511.65
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
Secondary graphics devices.
Intel(R) UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 5-26-2022 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- There are no monitors attached to this 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: 1-28-2022
Driver Version: 30.0.15.1165
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 16 GB
Still okay here:
Your Quadro and Intel drivers are old but I don’t see any other issues in your SystemInfo.
If it were me, I’d update the drivers:
Nvidia - Official Drivers | NVIDIA
Intel - Download Intel Drivers and Software
Any luck?
I’m not seeing any crash reports linked to the email address you’re using here in the Forum.
Yeah. It’s on different email.
Without that other address, I can’t find it.
And could you explain please how to track it?
No crash report there either.
Did you add your email address to the crash report?
I don’t recall, but think so.
Anyway I can make a new one if drivers’ update won’t help.
No luck…
Same issue with both updated drivers.
I’ve rebooted PC after update.
Sent the report with email above.
Current System info
Rhino 8 SR0 2022-12-27 (Rhino WIP, 8.0.22361.13135, Git hash:master @ c51c915253258ed1c83aaed86199b3e81cefede0)
License type: Commercial, build 2022-12-27
License details: Stand-Alone
Expires on: 2023-02-10
Windows 10 (10.0.19044 SR0.0) or greater (Physical RAM: 32Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro RTX 5000 (NVidia) Memory: 16GB, Driver date: 11-23-2022 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 527.27
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
Secondary graphics devices.
Intel(R) UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 5-26-2022 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- There are no monitors attached to this 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-23-2022
Driver Version: 31.0.15.2727
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 16 GB
Thanks
I’ll watch for it.
I see a crash report now.
I’m looking for a developer to have a look at the call stack.
Thanks
Just to your knowledge, everything works fine in v7.
That doesn’t matter. There are too many changes and differences between the versions to compare them.
The developer tells me it looks like you may be running a Space Mouse, and it’s use of the depth buffer is causing the crash.
Please disconnect the Space Mouse, start Rhino, and see if a regular mouse avoids the crash.
Yes, it works! No crushes.
Thank you!
But is it possible to handle that situation with space mouse?
Not currently, but there is a new Bug report to figure it out:
The report is not available for public viewing currently.
RH-72262
It will be fixed before V8 ships, and probbly long before then.
This will fix the problem in Windows, but we’re still testing if the fix causes a new problem in the Mac V8 WIP using the Metal display tools and a Space Mouse.