This shows you the differences between two versions of the page.
rhino:checkreducefilesize [2017/10/19] |
rhino:checkreducefilesize [2020/08/14] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== How did my file size get so huge? ====== | ||
+ | |||
+ | |||
+ | > Periodically there is a post on the Rhino forum by a user that has seen their relatively simple file grow to a huge size and they don't understand why or how to reduce the size back to " | ||
+ | |||
+ | ===What causes "file bloat"? | ||
+ | |||
+ | Several things can dramatically add to file size: | ||
+ | |||
+ | * **Display meshes** - Rhino uses special meshes to display surface objects on the screen. Very fine display mesh settings can cause large file sizes without you realizing it. You see the display as normal, but you are not necessarily aware of how many polygons the display mesh has. | ||
+ | |||
+ | * **Textures/ | ||
+ | |||
+ | * **Materials** - it is possible to have a large collection of materials which can take up a significant amount of file space. | ||
+ | |||
+ | * **Plug-ins** - Rhino plug-ins can add all kinds of additional functions to Rhino from advanced rendering to branch-specific design tools to CAM. Plug-ins are allowed to store their own data in the Rhino file, and it can be quite copious depending on the nature of the plug-in and how it was used. | ||
+ | |||
+ | * **Big data** - finally, Rhino files can simply contain **massive amounts of geometry** in the form of curves, surfaces or meshes. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===How can I see where the problem is?=== | ||
+ | |||
+ | Having read the above, you might already have some "usual suspects" | ||
+ | |||
+ | However, if you are stumped, or just want to see all of what your file contains in extreme geeky detail, you can use the **Audit3dmFile** command inside of Rhino. | ||
+ | |||
+ | * First is the **" | ||
+ | |||
+ | * Next is the **" | ||
+ | |||
+ | * Further down is the **" | ||
+ | |||
+ | * Lastly, at the bottom is the **" | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===OK, I see some possible suspects, how do I proceed now?=== | ||
+ | |||
+ | * **Display meshes**: If you suspect your display mesh settings are causing an inflated file size, there are several things to try. You can try using the command **_SaveSmall**, | ||
+ | |||
+ | * **Materials**: | ||
+ | |||
+ | * **Bitmaps (images)**: If the bitmap table contains large entries, it could be one of several things. | ||
+ | |||
+ | * **Plug-in data**: Data created by Rhino plug-ins stays in the file //even if the Rhino instance opening the file doesn' | ||
+ | |||
+ | |||
+ | * **Massive amounts of geometry in the file**: | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===What other possibilities are there?=== | ||
+ | |||
+ | Some other things that can be tried if all the above fail... | ||
+ | |||
+ | * Sometimes opening a new blank file, copying and pasting the geometry out of the old file and into the new can fix things. | ||
+ | |||
+ | * If things are really bad and absolutely nothing else works, you can try using **_SaveAs** and check " | ||
+ | |||
+ | ---- | ||
+ | ==(comments welcome...)== | ||
+ | |||