ZBrushCentral

Broken Mesh

I saved my ztl and it said it was out of memory in the process. I tried saving again and it worked. I soon found out it did NOT work and corrupted my ztl. Now each time I load it and draw it out, it is exploded. I also noticed that in the preview window it looks fine, but as soon as I draw it out it is exploded, and on the lowest sub d it is missing polygons on only one side.

Long story short, somehow zbrush saved a corrupted z tool and it is now exploded. If I had wrote over the old file or did not save incrimentally I would be lost. Just wanted to report this rather than find a fix since I have a prior version. Anyone else encountered this?

Odds are good that you’re trying to make ZBrush do more than your system can handle.

What are your syestem specs, and what are your settings in the Preferences>Mem menu? How many polygons does your model have at the highest level?

Also, have you defragmented your drive lately? Does it have a good amount of free space on it?

Thanks for the speedy reply Aurick. I am running a P4 dual core at 3.2 Ghz with 4GB DDR2 ram. I have defragmented after the problem, with very little fragmentation (I doubt thats it but you never know). I do not have access to my mesh at the moment so I cant specify poly count.

The reason I believe it is something other than pushing my PC is because it has only happened once. It is not something that is frequent or that I can re-create (a good thing). I am willing to bet my machine just needded to be re-booted or something.

The one thing I dont understand is why it let me save the second time but got the error the first time (not enough memory to perform task) and the second time it wrote over it with a corrupt file. I would have thought it was the error that created the corrupt file, and the save after should have over-written that and been ok. Anyway, thanks again for the quick response and I mainly wanted to inform you, incase it happens to other users or has happened in the past. I love zbrush and found many “problems” are workflow related or have good explanations to their cause.