Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 16GB)
.NET 7.0.18
Computer platform: LAPTOP - Plugged in [100% battery remaining]
Hybrid graphics configuration.
Primary display: Intel(R) UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 2-25-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 GTX 1050 Ti with Max-Q Design (NVidia) Memory: 4GB, Driver date: 11-21-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 546.26
> Integrated accelerated graphics device with 4 adapter port(s)
- Secondary monitor is laptop’s integrated screen or built-in port
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-21-2023
Driver Version: 31.0.15.4626
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB
Rhino plugins that do not ship with Rhino
C:\Users\ivan_galik\Downloads\blockeditnew20231220\BlockEditNew.rhp “BlockEdit” 1.0.0.0
Posting again with some more information in hopes of getting some heat on this one. This bug is extremely repeatable from my experience. I haven’t been able to successfully complete a hatch in a couple days and will need to start rolling back to R7 and undoing significant work unless we’ve got a fix inbound.
Seems to be triggered by creating or editing hatches, including defining boundaries, changing scale, changing layers, etc. In the clip below, it was modifying the scale property that did it.
This bug’s pretty painful. Let me know if there’s anything I can do to help.
Version 8 SR6
(8.6.24101.5001, 2024-04-10)
edit: there’s should be a fairly large collection of submitted bug reports from me by now, but if you’d like the file direct, just let me know and I can send it over. This bug is repeatable on every attempt.
Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 64GB)
.NET Framework 4.8.9232.0
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 4090 (NVidia) Memory: 24GB, Driver date: 3-12-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 551.86
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1
- Secondary monitor attached to adapter port #2
- Secondary monitor attached to adapter port #3
Secondary graphics devices.
Intel(R) UHD Graphics 770 (Intel) Memory: 128MB, Driver date: 1-18-2024 (M-D-Y).
> Integrated graphics device with 4 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: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 3-12-2024
Driver Version: 31.0.15.5186
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 24564 MB
Rhino plugins that do not ship with Rhino
C:\Program Files\Chaos Group\V-Ray\V-Ray for Rhinoceros\V8\VRayForRhino.rhp “V-Ray for Rhino”
C:\Users\clayt\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\D5Conv (e0d5e210-02f6-4ee9-a2b0-1675e225d958)\0.10.1.0001\Rhino 7\D5Conv.rhp “D5Converter for Rhino”
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino7.rhp “Datasmith Exporter” 5.3.2.0
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo”
for testing purposes please go into File>Properties>Plugins and disable plugins that do not ship with Rhino (there is pulldown to sort). Restart Rhino and try again. Thanks
One other thing I’ve discovered. By copying over the hatch geometry from the file that is crashing to a new file, I’ve been able to replicate the crash in the new file. Otherwise, the new file is totally stable.
Disabled plugins and I can’t seem to replicate the crash anymore. I’ll start isolating the non standard plugins and seeing which one is our culprit.
Worth noting, this isn’t the first time that Datasmith and Vray have given me issues in R8.
Thanks for your quick responses! You just pulled my bacon out of the fire.
Great to hear, thanks for sending in the crash reports. That speeds the troubleshooting process up. If you identify the culprit please do tell. Thanks again.
It appears the crashes only happen if Tibidabo and VisualARQ are loaded. I’ll take this issue over to the VA forums and see if their developers can help out.
Edit: Even more specifically, it appears to be the VisualARQLABS plugin, which is much more innocuous to remove from our workflows.
Hi @Clayton_Muhleman! can you share a file to test this crash? If it happens due to VisualARQ I’ll need to reproduce it. I’ve never experienced such a crash before, and as you can imagine I always have VisualARQ, (and the VisualARQ LABS) loaded.
After collecting some data on plugin use and crashes, I’m afraid I don’t have solid evidence one way or the other. I’ll be doing some more drafting over the next couple days, if I get any hint that it’s VA, I’ll shoot you a file to see if we can replicate it.
After quite a bit of kicking this one around, the most consistent way of stopping this crash is by disabling the VA plugin. There should be about three hundred crash reports, but I’ll shoot you a link to the file as well.
When the crash occurs, it’s very consistent between crashes. Any interaction with a hatch will cause it. If I disable VA, the crashes will immediately stop.
The weird part is: if I re-enable non-default plugins (Visual Arq + V-Ray), the crashes don’t return immediately. Eventually the do, however, and I’ll need to disable VA again in order to stop the crashes.
