0
$\begingroup$

i have created tire treads for my car.added bevel,subsurf,array and simple deform modifiers to it and saved it.file size shows 1286 kb. but when i applied all the modifiers to make it a single mesh and saved it, the filesize goes to 140,541 kb.my unit setting was inches and scaling was 1.0 . the size of the tire was 20.4 X 20.4 X 6.37 (in inches ). my question is why filesize goes this high after applying those modifiers ?? will it make any difference if i change the unit settings like inches to cm or scaling to .01 or change both, and then recreate the mesh ?? i am working on 2.8 beta.

$\endgroup$
  • 4
    $\begingroup$ The file size is the same for a cube that is 2cm x 2cm x 2cm than if the cube is 20000 x200000 x 20000 km, the number of vertices is the same. The key to your question is in this sentence: "when I applied all the modifiers". Modifiers will calculate new "virtual" geometry on the fly from the original mesh, by applying the modifiers you are making that geometry real, therefore increasing the number of vertices among other things. $\endgroup$ – cegaton Mar 10 at 19:28
3
$\begingroup$

It comes down to the information needed to describe the scene.

When you have modifiers, you only store the input mesh and the settings of modifiers. So in the case of subdivision modifier (for example) you save only the low-polygon mesh and a number indicating how many subdivisions there are. When you open the file, Blender generates all the subdivided vertices and displays them - they are kept in system RAM when the file is open, but not saved when you save the file.

When you apply the modifier(s) all that generated geometry becomes real - you can change each vertex individually. The information how to generate all that is lost because the modifier is gone. So when you save the file, Blender needs to save all the geometry.


Unit settings have no effect for file size, you are saving the same amount of values. The values themselves are just different (instead of saving the number 1.5 you save 3.81 - inch vs cm). Blender stores all these numbers as 32bit floats so no matter the value they occupy the same space in memory: 32bits = 4 bytes for each.

$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.