ZBrushCentral

4,194,305 kbps file write limit/error

ZBrush Usage Questions
#1

I am having an error in ZB4. I hit save and watch the intermediate *.ZZZ file start to build. It’s a large file, it tops out at 6,236,569 kbps, but then it is rewritten to a file of the same name with an extension of .ZPR with a file size of 4,194,305 Kbps. Last week this happened to me the same way it was suppose to be a 5.5GB file but came out 4,194,305 kbps (4.19GB). The resulting file will not open, I get an error when I try to open.

What could be happening? I can’t shut off my computer till this is saved, the project is still open and if I turn it off I loose 7 hours of work.

Why is ZBrush 4 limited to writing file sizes of only 4,194,305 kbps? I need to write a 6.2GB file not a 4.19GB file.

What should I do? Don't want to loose any of the sculpt or poly paint information.

Can someone test this on their rig? I can’t be the only person writing files over 4GB.

#2

I had the same problems a few weeks ago. The IT dudes at work told me it’s because zbrush is 32-bits and cant handle a 4 gb file…try to save the file with the lowest Sdiv on all subtools or delete any Subtool that you dont need. (if you have any.) I managed to get the size down to 2 gb but I’m nervous everytime I save a file in ZB

#3

if you have layers, delete them all but one, and save that out as it’s own file. Layers are typically where major file sizes come from. I’m guessing you have a few polypaint layers, and probably a couple of sculpting layers. At some point you have to commit to the work you’ve done.

#4

Originally posted by goast666,

At some point you have to commit to the work you’ve done.
Words of wisdom. :+1:

#5

Are you sure you aren’t trying to save to a FAT32 formatted drive? They have at best a 4GB file size limit. Have a drive formatted in whatever newer filesystem your OS supports for huge files.

32 bit apps can only address 4GB of RAM but that’s why we have page files. I imagine zBrush would start complaining about lack of memory before you even started saving if you were out of both RAM and page file space.

#6

I’m on 64bit windows and NTFS drive. I made this set up when I was exparimenting with Mudbox 64bit. I would save giant 10GB files in that package… It was beautiful!!!

I got the file to save after I deleted some of my geometry. I deleted about 1/3rd of my total poly count (all the garbage) and then it wrote out a file that was only 1.2GB… It’s strange only 1/3 of my polys gone but then it writes a file that is only 1.2GB, before that 1/3 was removed it wanted to write a file that was over 6GB… This may be some kind of weird programming bug… 4,194,305 kbps may be the magic number, check your file sizes before shut down the program. If you see this number the file has not been saved correctly and you will not get any errors. You won’t know it until you try to open the file again, and it does not open.

The 4GB limmit makes sense on a 32bit app, but this is on an NTFS file system… What would be the overriding limmit?

I do commit to my changes but only in the last step… Sometimes, for technical issues, you need to keep stuff around.