I’m currently working on a model of approximately 200 subtools, the file is currently 2.87GB in file size. Which is a lot larger than I’m normally used to work with. So I started to investigate the issue and found out that a single subtool of 2,149 Active points adds 41.27MB to the file size.
Does anyone know the reason why this happends and how to fix or prevent this from happening in the future?
After exporting the model to an OBJ file and reimporting it to zbrush and saving it as a single ztl.file gives me a file size of only 92kB which it is supposed to be… So the zbrush file size is actually 450 times to big…
Are you saving all the undo history for every subtool along with the model when it’s exported maybe?
There is no undo history in the file, I made sure to delete this just in case. Also I think a .ztl never saves the undo history.
Hello @Dubla
Point count is not the sole determining factor of file size. The state of the mesh in the file can play a role. Certain features in use may affect this.
If you’d like us to take a look at the file to see if there’s anything unusual going on, please just stop over at Pixologic Support and start a conversation.
Thank you!
Hi DUBLA
correct, a .ztl don’t saves the undo history.
Regarding your problem, I think we can compare this with a photoshop file (please correct me if I’m totally wrong with this).
In PS you can have multiple layers with all the fancy things that you can do in this program (I don’t have PS, I use Affinity Photo but it’s in general the same behavior).
The corresponding PSD file is normally much bigger as an exported e.g. PNG file.
During the export all the layers will be combined to one layer (or 2 if you use alpha).
This (and also the PNG loos-less compression) reduce the file size.
In short words, al the tools, subtools etc. in ZBrush request extra memory.
If you export this into a generic 3D format like OBJ then all this different ‘layers’ will combined to ‘one’ object with pure information about the points and polygons.
CU
Thanks, Yes I’ll make a ticket and send over the model.
Yeah I do figure it must be some underlaying data, however it’s a 2K poly model wooden plank which I’ve worked on for like 2 minutes. So there shouldn’t be too much data involved with that.