Scale component file size question
-
I am creating a drywall and exterior plywood plan. So I have a rectangle component that represents a full sheet of drywall. To represent a 1/2 sheet would I save file size by scaling that component to 2' wide instead of making it unique and then pushing in the edge?
-
You can scale a component tio your needs (if it does not have any fancy geometry in it which then could be distorted). Note however that the original instance will still be the original size so when applying more of this scaled components, you should copy/move them from within the model instead of inserting itt from the component browser (or else you need to keep scaling them one by one).
When I modeled our office (just a quick model to see how we can rearrange the furniture) I used the same one component to build the desks and the cases only by scaling it (from outside of their context).
-
Thanks Gai, I'm pretty familiar with how the scaling works. What I was trying to determine is how to save a little file size. Here it is broken down a little more:
A model with 5 identical boxes would be larger than a model with one component repeated 5 times.
What about a model with 5 different size boxes? Would you save file size by making a box component then scaling 4 copies to different sizes? Or would this be the same as making 5 unique components and changing their size with push/pull?
Well after spelling it out like that, I figured I should just do it. The answer to my own question:
-5 identical box components = 10k
-Above boxes scaled to different sizes = 10k
-5 box components made unique then push/pulled to different sizes = 16kSo on simple shapes (without textures) scaling is the better option for anyone keeping track.
-
Thanks for cattying out the experiment sketchy, that's useful to know.
-
You would think the file size on your last one would be 50 kb - 5x10kb - since each component is 10 kb and you made them unique. mmmmmm...interesting (thanks to Artie Johnson).
A good experiment yielding useful information.
-
Just a minor clarification bellwells, the model that was 10K had 5 identical components not just one. But your observation is right, the file size does not increase in a linear mannor.
-
Obviously the file itself needs some bytes (save an emty one to see how much) and additionally, the info about where, what size, how rotated etc. of the individual instances are also takes up some space.
Obviously, with more complex components, the "profit" is bigger.
Advertisement