Print at Dec 20, 2025, 7:06:33 PM

Posted by YGYL at Feb 18, 2025, 5:00:21 PM
Re: Meet MarioSambol, our new support team member
No, you're not understanding what I'm saying. What I said is much more advanced. You can think of it as a data structure that uses many low-level parts to form a complex high-level object. For example, it turns out that a tree takes 20MB of OBJ storage, and in this way you can compress it down to 0.5MB.
I would really like to know what the trick behind that is. Schrinking to 1/40 of the original size is huge. Sweet Home 3D is not the very best considering OBJ size. Take for example the Sycamore tree from the Scopia library. It is created in Blender and is around 7.6MB. Export it from Sweet Home 3D and the resulting OBJ file is 18.8MB. Efficient? Not really and that is putting it mild. Import that export in Blender and export it again and the size shrinks back to 7.6MB. But what you mention is something entirely different.
You may have read in one of my other posts that, besides developing 3D models, I work mainly with very large projects. And those are causing problems in Sweet Home 3D because of their size. Having the tools to considerably shrink objects is very welcome.


You can understand it like this:
This is an example of separating an object, I'm going to draw a luxury table from the French court, consisting of a large table board and 6 table legs, the large table board is 1MB, each table leg is 1MB. if you export the OBJ directly, then naturally it's 7MB. or you split it up and lay it out in a SH3D file 1 large table board plus 6 table legs. You save the file and see it's 2MB because those 6 table legs are the same and add up to a 1MB.
The same big tree why take up a lot of file space, because he has thousands of leaves, each leaf is very large, let's break it down, a trunk plus thousands of the same leaves. 0.5MB (this is a bit exaggerated)