i’ve been using _ExtractClippingSlices command on a very simple object and wondered why it takes so long to compute. Turns out it sliced some hidden SubD test object with 200k faces and created the results also hidden. Once i’ve shown the hidden content of by doc i got a big surprise.I did not expect that hidden geometries are involved at all, is this supposed to happen ?
Also happens when using _ExtractClippingSections. (8.17.25023.14001, 2025-01-23)
below is what i see, the hidden object in this example is a render mesh extracted from a SubD box. If this mesh is hidden and i run _ExtractClippingSlices, select the ClippingPlane object and press Enter, i get a section on the visible brep as expected. If i show the hidden mesh, i have a section for it too. Not sure if this is supposed to happen ?
Hi @Gijs, i’ve noticed that too when i was trying to replicate the bug, it did not make a section for the (visible) SubD, so i extracted the render mesh where it worked when it was visible. But i’ve been surprised it made the section for the mesh when it was hidden. There is definitely something broken, eg. if i move the section objs in shaded mode, they dissappear and only the gumball indicates there is something selected:
I can still see the section objects in other views which are not shaded. Can you repeat that as well ?