ZBrushCentral

Urgent help needed - Error has been encountered while trying to load the file.

Hi guys! I’ve been working on a big project since January. At first I was saying incrementally at the end of each day.
After a while the file became 4gb in size and I started saving over the same file. Today I saved the file. Then ran morph target>create diff mesh. ZBrush ran out of memory and said that will save it to a disk (I assume into a Recovered Files folder.) I quit zbrush and tried to open the project file i saved before. I got

“Error has been encountered while trying to load the file. Loading has been aborted.”

Last save is 3 weeks old. My deadline is in 2. I know it’s all bad and I’ve lost all hope by now.
Anyone? Does Pixologic have an emergency recovery service?

Attachments

VRprFoL6.jpg

Okay. I love Windows! I right clicked the .zpr file and clicked Restore Previous Versions. Now I only lost 2 days of work.
Don’t need an urgent help. But if you at least know WHY it would happen, please let me know!.

Who knows what evil lies in the heart of Zbrush? Umm… Nobody as far as I know. I’m lucky if I don’t crash when I’m just turning a model to a side view. Yes, that’s happened to me several times lol.

Man, that’s nuts!

Does anyone know anything about Zbrush Autobackup script for 4r3?
I know it existed for older zbrush. Can’t find it for 4r3 tho.

The Auto Recover feature is not compatible with 64-bit versions of Windows 7.

As for what happened with your file: ZBrush is still a 32-bit application (until ZBrush 5 comes out). As such, Windows imposes a 4 GB maximum for the size of files that it can load. If you ever start pushing close to that, it’s time to rethink things a bit!

One thing that will help you a lot is to not use the ZPR format (via File>Save As) unless you specifically need to. For example, if you have render settings that you need to keep and don’t want to redo or if you have a need to have your work as multiple Tools rather than SubTools. The ZPR format saves just about EVERYTHING - including any incidental Tools that you might have created during your work, materials that have been loaded, render settings… you name it. As a result, your file sizes can easily bloat if you’re not being careful.

Instead, use the ZTL format (via Tool>Save As). This saves the current Tool and its SubTools, applied textures, etc. In almost all cases, this is all you need for saving your models. You’ll have smaller files which not only helps avoid exceeding the Windows limitations, it also helps ZBrush work more efficiently so you can avoid those out of memory situations.

By the way, it’s bad practice to save over your most recent save. To stay on the safe side, it’s a good idea to save two or three incremental versions, overwriting the oldest with each save. That way, if you do hit a situation like this or a file corruption you should be able to revert to the last version or the one before that. You’ll lose less work if the unthinkable happens.

Yep. I do feel stupid about saving over. Good thing, the story has a happy ending. I resculpted everything in one night and it looks twice better.

My other project files were 2gb max. I think what made this one huge is that all my subtools were visible. (Some of them possibly at the highest subdivision level.)

Also found this handy little incremental save script. Haven’t tested it yet, but a friend of mine claims that it works with 4r3 even better than it worked with 3.5

http://www.maphart.com/2010/freebies/zbrush-3-5-ztool-autosave

Thanks for support! Now I’ve got some sculpting to do! :slight_smile:

Actually, a file isn’t going to be any smaller by hiding SubTools. The points are still there.

Also, while it’s okay to hide SubTools when you save, please do not save with hidden points. It complicates the save and a lot of the corrupted files that I’ve seen have wound up having hidden points. Just a word of caution. :)

I accidentally made a jump from 1.5 gig to 4.7 and did not noticed and zbrush crashed during saving.
Now it wont open and crashes with multiple out of virtual memory errors.
I lost 2 hard days of work, is there any way to recover a corrupted tool file like that? Maybe through debugging the file?