I hate to bring it to you, but it is again meshing settings in your document that cause the bloat. The three selected parts in the screenshot below take 85MB of the file size…
Now, if I set document properties meshing settings to Jagged & Faster I end up with a 1.7MB file.
Even setting it to Smooth & Slower saves the document as only 2.3MB
My guess is going to be that you have a template set up such that it uses insane meshing settings.
Each time you see something like this happen, please first check your document meshing settings, followed by a check for custom render mesh settings on objects you just pasted from another document.
Holes still look good with Smooth & Slower
And IMHO even with Jagged & Faster, although there a bit of jaggedness is visible
But mostly only when zoomed in very closely
Addendum:
Now how to find complex objects yourself? Use the _Audit3dmFile
command and inspect your objects. Look at the amount of bytes used by an object. As you can see from my first screenshot I highlighted for you three objects that together take 85MB of the file (two objects with over 20 million bytes, one with over 45 million bytes). Then copy the Id
of each object in turn and use the command _SelID
with each Id
in turn to select the largest objects. Then inspect.
Furthermore you can check the embedded images and materials table for info on how much data that part takes up in the file. In this case the verdict is: not much, a measly 340KB.
Embedded image Table:
EmbeddedImage[0]: /D drive files pending replacement cos IO error/Agisoft Exports RAF Bomb Trolley Mk1a Chock Channel Bomb bearer/_MG_18_7315 RAF WW2 Roller Chock splitpin crop.jpg
1 embedded images, 339175 bytes (offset 203934 to 543109)
Texture Mapping Table:
0 texture mappings, 24 bytes (offset 543109 to 543133)
Material Table:
material[0]:
material[1]: Picture Frame
2 materials, 1669 bytes (offset 543133 to 544802)
In any case we essentially already addressed this type of problem, and gave many, many pointers on how to fix in this not-so-old-thread from this year: Effect of meshes on save time Rhino V5 v V7 . The problem is exactly the same.
I know some users like to blame images, but in most cases the culprit is elsewhere. Therefor it is important to learn how to investigate your files. From now on make Audit3dmFile
your best buddy.