ZBrushCentral

"Out of disk space ...." error opening one specific project (Please Help!).

PARENT-SUPPORT CHILD-Startup And Compatibility Troubleshooting
#21

I am having the same problem as everyone else.

When I try to open a File or load a ZTool (both from the same project) I receive the “Out of Disk Space” message. I also have the same mysterious .zzz file in my project folder.

Concerning the problematic file: the Polycount was quite low, at 2,358 total points. The ZTool in the File has 30 SubTools.

I tried Aurick’s suggestion which may be responsible for my limited success in recovering the ZTool. His instructions were: Preferences > Undo History > turn on Skip Loading and turn off Enable Saving.

Aurick’s suggestion allowed me to load the ZTool and re-save both the ZTool and the File with a new name. However, even the new File and the new ZTool will cause ZBrush to crash within minutes. I said that I had limited success because while I’m able to recover the ZTool and the file, ZBrush crashes when I try to export an OBJ or use GoZ. So while I am able to view my work, I’m unable to do anything useful with it because it doesn’t stay open long enough for me to get the data out of ZBrush.

My System Specs:
MacBook Pro, Early 2011
Processor: 2.3 GHz Intel Core i7
Memory: 8 GB 1333 MHz DDR3
Graphics: AMD Radeon HD 6750M 1024 MB
OS: Mac OS X Lion 10.7.5

I have almost 600 GB of free disk space.

I will still submit a Support Ticket now.

#22

While this is not a fix, I have made a couple of changes, to my daily routines, after this incident:

  1. Never overwrite an old project, but always create a new incremental save, 1, 2, 3, and so on.
  2. Significantly decrease the amount of tool undo’s. I think the default is 10k, but I have mine at 500, which is more than enough.
  3. “Compact memory” once in a while

I have never since had a corrupt file. BUT like some of you I use zbrush every day to make a living, so I hope some to see an update in the “auto updater” that will fix this for good, as it sucks to lose days work when on a tight deadline.

I have a feeling that some of these quirks that sometimes causes crashes, is somehow related to zbrush being 32-bit and pushing the memory limits, making the program unstable. Looking forward to that 64-bit update…

#23

I put in a ticket, and was told that this is a 4R4 glitch which occurs when you merge subtools without first having UV selected. You can work around it by hitting the UV button prior to merging, but any files which have been corrupted are going to be irretrievable.

In the last few days I’ve been following this protocol and haven’t come up against any new error messages.

#24

Hi.
I have the same problem with the error caused by the lack of virtual memory. I’ve been using the program for a long time and had no such problems. Yesterday at work was reported that little memory.
Need some help.

#25

This week I will have to reinstall the system. Maybe after this work. haha. I hope …

wtf.jpg

#26

Same issue here. Unfortunately I just lost a bunch of work. I sent in a support ticket and links to my ztool on drop box. The skipping undo load didn’t help.

Thanks!

#27

Same has happened to me, i am low on SSD sapce though, when i open Zbrush i have 8GB frree when using it it goes down to less than 1GB free. Is this normal??

i have 8GB of Ram and have been playing with the settings… i can only get upto 8 million polys before this kicks in system says it can run 18 million +. Im running a i7 aswell.

Any fix?
to the point ZB4R4 wont even open :-/

EDIT***

the undo history solution worked for me!

#28

Hey. I solved the problem. In the general I have no way in which it was impossible to solve the problem. But there is one proven way. Reinstall the operating system.
www.jpg

What caused the error, I do not know. I think programmers will find out Pixologic.

#29

reinstalling OS is the only way to fix this? that seems silly. there is no other solution?

#30

The only thing that helped me is to reinstall the system. I do not think it’s silly.
Over time, as the system it is advisable to reinstall. If you use it a year or two it will work because after the first installation.
If you dearly when this is the fastest way to solve the problem. You decide. If I could find another way to solve this problem, we would have written.

#31

I have the same problem as above. I tried to save, and it gave me the can’t unload memory error as described above. That file, after the crash, refuses to load properly and also crashes ZBrush. Interestingly, I wasn’t too far into the project, just setting up my sub-tools for only 1 minute, and I tried from the beginning and decided to save quickly, no problem. Next I went to do a merge down on two subtools and bam, same problem. So as long as I don’t want to merge my characters eyeball into one subtool then it seems I won’t have an issue, but if I even attempt to do that it will destroy the file and not allow me to save or load it… Hope that provides some info on this.

#32

Do you have ZB4R4 R2?

#33

After I preustanovil system. I opened the file highlighted that preserved in memory errors.
The lists had one broken object. Ie it does not show and the choice was not. I just deleted it and re-save the project.

If someone is to reinstall the system, it is best after opening your project, remove the object that is not visible. Of course you will lose it, but restore it will not work. Because when you had a memory error are full of these objects in your project will be lost.

I apologize for my English. Used a translator.

#34

Yeah. ZB4 R4 P2 running on a fresh install of Windows 8 Pro

Fresh install of R4 -activate- and then straight to zupdater/re-activation for the update. Again, for me, problem started with trying to merge two separate eyeball spheres into one sub-object. That damages the scene and corrupts any attempt to save said scene. Simply leaving the eyeballs separate doesn’t cause me any issue, working fine like that, quite happy. admin can email me via my acct. for a sample .obj file and step by step if needed (I may not check back on this thread). best of luck

#35

If the subtools did NOT have UV’s assigned, it could cause an error like this.

#36

Same error here.
I could reproduce it the following way:

Make a model and some subtools.
Polypoint on the model.
qRemesh the model.
Delete the eyes subtool.
Redo the eyes by:
Make a sphere and append it to the model.
Duplicate the sphere.
Merge the 2 spheres down.
Save the tool.
BAMM.

The “crash” occurs only when I delete the eye sub tool and create this subtool anew.

#37

Did the spheres have uv’s assigned before the merge?

#38

Nope, they did not have UVs assigned.

I have uploaded my tool here so that the bug can be tracked:

http://www.file-upload.net/download-6904934/Skin_mann3_4_mithose3_bodyremeshed6_painting10.7z.html
(The download button is a small white button with a small green cap next to it).

The uploaded tool does NOT crash.

To reproduce the bug, please do the following:

Add the tool to a new/empty project
Click the “SubTools” menu
Click the existing “PM3D_Sphere3D4”
Click “Delete”
Click “Append”->Sphere3D
Click the Sphere3D in the SubTools menu
Scale the sphere down to the size of an eye ball
Move it to one eye cavity in the face
In the SubTools menu click “Duplicate”
Move the second sphere to the other eye cavity
In the SubTools menu, click “Merge”, then “MergeDown”
Save the Tool (“Tool”->“Save As”).
You will see the error “Unable to Offline a memory which is already Offline”.

This occurs everytime, so I guess it might be good for bug tracking.

Hope it helps.