Hello. In this video, simple 0.2m chamfer doubles the file size from 221MB to 440MB. Please pay attention how selecting the first edge takes nearly 1 minute (second edge is being selected immediately). The area is 2x2 kilometers which I believe doesn’t affect to memory. If this 1 simple underpass doubles the file size, how can I build several underpasses?
My GPU became unusable, so I switched into inner Intel GPU and expected some speed problems. But I believe, this is not the size issue.
Hi -
It’s hard to debug a model from an image or a video. Please upload the 3dm file and refer to this thread in the comments field.
Also always run the Rhino SystemInfo command and copy-paste the result when reporting an issue.
Apart from that, you could try to change the mesh settings in Document Properties -> Mesh to Jagged and faster or a custom setting to create a lighter display mesh.
-wim
Well, it is a polysurface and has 221 MB size. Can it be attached here?
You’d have to use DropBox or a similar provider and post an url.
Uploading from the link I provided should work.
-wim
It’s already chamfered. I couldn’t find unchamfered version. Can you please figure out what makes it so heavy?
You can get to the unchamfered version by following the instructions in the Edit section on this page pertaining to removing edges.
Rhino can edit the chamfers because the unchamfered version was saved in the polysurface. The majority of the data in the file is in one polysurface made up of over 4000 surfaces. That is also why the file size doubles.
By the way, _FilletEdge and _BlendEdge work similarly; they all use the same plug-in that creates their history.
If you don’t want to keep the history of the chamfers, one way to remove it is to _ExtractSrf _Copy=No any surface then _Join it back to the rest of the polysurface.
If you want to retain the ChamferEdge history, not significantly increase the file size, and have Rhino model it more quickly, before adding the chamfers, extract the surfaces that will be affected by the chamfers and join them into their own polysurface. If you need a closed polysurface at a later stage, separately save the working file to retain the history and _Join the polysurfaces to create the finished model.