Hello. Whenever I try to add a clipping plane in the attached file the entire system freezes. I updated Nvidia Drivers and still the problem persists. Can anyone help, because i cannot find what is causing this. It sometimes does this even for smaller files but it’s pretty random.
SysInfo: SysInfo.txt (2.4 KB)
i can confirm that this issue happens on my system as well. 8.5 with latest nvidia studio drivers (clean install).
created a clipping plane in the top view (wireframe shading) - worked.
selected the clipping plane and turned on perspective in the properties - this lead to system-wide freeze. had to manually force a reboot.
@dale The crash doesn’t trigger a BSOD and it’s system-wide so i don’t really know if i can send you a mem dump…
but i did notice something curious.
if i open the file op uploaded and make a clipping plane as explained previously, it triggers the system-wide indefinite freeze
however - this is where it gets interesting
if i hide most of the geometry first (i only left the blue base), create a clipping plane directly in the perspective window, then unhide - the freeze doesn’t happen ( @Dan_Iliescu this might help you for now )
i realize that, but i can’t do anything with the system after the freeze - it’s system wide. the whole system become unresponsive, indefinitely. Meaning i can’t open a task manager to make a dump for rhino app only. Sorry for the confusion.
(and since it doesn’t trigger a bsod, i can’t even send you a whole system mem dump either)
Can you repeat this with just an empty scene, or is there a specific file you’re using?
What display mode is the Perspective view in when you enable “Perspective” for the clipping plane?
I’m still trying to reproduce this here and cannot… so the more details you can discover (ever so slight) might help me isolate this faster.
That being said, an application can’t really freeze your entire system, even if it tried to purposefully. The OS prevents any such attempt. System freezes come from faulty hardware and/or drivers. Since you’re experiencing this when running Rhino, it seems like it’s Rhino that’s doing this, but it’s most likely something to do with the current drivers, your current config, your power consumption, etc (or combinations thereof), and Rhino is simply “revealing” it.
My gut tells me that this is most likely related to certain shaders that Rhino is using on the GPU and the drivers are collapsing on you when they kick in.
Something you can try…
Go into Options->View->OpenGL and UNCHECK the “GPU Tessellation” option, close the dialog and restart Rhino… Now see if things still crash. If you are still crashing, try turning off Antialiasing next…still crashing?.. Then try moving the OpenGL slider (in the same OpenGL options page) to the left 1 notch and restart Rhino… You can repeat the slider test until it gets all the way to the left…at which point, Rhino won’t be using any hardware at all…so the chances of you still crashing are slim to none…but the usability of Rhino will also be pretty much useless.
Note: None these suggestions are to be considered “solutions”… They are simply attempts to locate and isolate where the problem really lies.
crash only happens when clipping plane is created in top view, then have its properties modified to also apply to perspective view (default shading mode)
doesn’t happen with gpu tesselation off (@Dan_Iliescu this might also help)
Great, thanks… We’ll start there and see where things might be going wrong… In the meantime, you can continue to run with it off until we can get a it figured out and fixed.
Hello. Thanks for the help. I found something else weird. After deactivating GPU tessellation and adding a clipping plane, surface edges and isocurves don’t show up in shaded viewport. In wire frame mode only the section is shown. Deleting the clipping plane makes them reappear. But at least it doesn’t freeze the entire system.
Please know that unchecking GPU Tessellation is not considered a solution…it’s for diagnostic usage.
I can probably fix (and will) the YT item Wim just created, but we still need to find out why tessellation is crashing the drivers on some configurations.
There are probably other things that will not work right with tessellation disabled, so just be aware of that.