I use Rhino a lot to create sections, elevation and floor plans from 3d scans, so I import a mesh and use MeshTrim to cut away the part of the mesh, that’s hidden behind the cutting plane.
Problem is, sometimes, I import the mesh as a Block and don’t always notice this before cutting.
When I try to cut a block object using MeshTrim, Rhino freezes completely in such a way, that I can’t even shut it down and I have to restart the whole computer using the hardware button.
What I would expect, is a first stage to the MeshTrim command, that checks, if the selected object to trim is really a mesh and if not, instead of running the tool on a block, generate an error message.
Hi Ivan - so far I cannot reproduce this with a simple blocked mesh - an example file (simpler the better for trouble-shooting purposes) and file to insert would be useful when you have a chance.
I’m terribly sorry for wasting your time, last week, during a presentation, I lost around 3 hours after the whole thing froze more than 6 times in a row after choosing a Block instance and I was forced to restart the whole computer, but now, I’m following the same workflow, using the same model and MeshTrim just doesn’t allow the block instance to be chosen as the object to be cut, as it should be. So I’m really stomped as to what might have been going on there last week.
Either way, sorry again for the false alarm.
Hi Ivan - two of us here found that MeshTrim does allow selection of a block instance as the trim target - it does nothing, here, as far as trimming goes but it does turn yellow as an accepted target, it’s not completely inert like in Trim