I’m still working on a large model of a tubes-and-clamp scaffolding assembly (see the illustration above). For design purposes the tubes are represented with curves assigned thickness and the clamps are represented by blocks containing simplified NURBS objects or even low-poly meshes…hundreds of them so that I can accurately study the relationships of the scaffold components. If I have these blocks, which are all on a layer with sublayer organization, visible in the model and then I add or make active a Clipping Plane so that I can study the interior arrangement of the design, Rhino will freeze. Even worse, it will completely lock up my Windows 11 PC, so that I can’t even force Rhino to quit. To resume work, I have to manually turn off my PC and restart it…so we are talking about a complete system restart requirement. That’s pretty annoying.
I’ve attached the current model with which I am seeing the issue. The Clipping Plane “vert interior plane” is in place and the layer containing the clamp blocks is visible, so simply activating the clipping plane in the Properties Panel for the current perspective viewport will reproduce the system freeze for me.
Even without the Clipping Plane active, having it visible in the model along with the many blocks visible appreciably slows Rhino down, so that even doing tasks like renaming the Clipping Plane in the Properties Panel becomes a painfully slow process.
Turning the layer containing all of the clamp blocks off eliminates the Rhino slowdown and does not seem to cause the system freeze when I activate the Clipping Plane.
I’ve also attached my current Rhino System Information.
conceptual htndtm 04920240628_174258.3dm (18.9 MB)
Rhino System Info for clipping plane thru blocks system freeze.txt (2.7 KB)