I use it all the time, it does not crash for me.
Hi,
I am using xp 64, amd athlon 64 X2 dual core 4400+, 4 gig ram, geforce 7800 GT + Wacom Cintiq 21" (newest driver)
Zbrush 3.1 is constantly crashing on my system - not only when using the save tool
i am working on a simple model which might not overstress Zbrush (about 4 million polys) - I am using no subtools, the mesh is clean, I am not using the ctrl + s hotkey … …
when I installed the newest geforce-driver, ZBrush stopped working at all
so I reinstalled the previous version - see above…
I am really sad about this, because I used to LOVE Zbrush and more and more I am loosing my enthusiasm about this tool.
please provide us a stable update - after all we have paid for this tool
kind regards,
michael
just adding to the statistics.
replacing existing ztl through tool panel save tool button or bound hotkey, causing crash.
thanks for the incremental saving plugin, hasn’t caused a crash yet. (might be simply b/c it doesn’t overwrite though?)
hi aurick , i think this is not bcoz of low system mem , i got this bug first time.
i had saved my same polycount mesh many times but when i saved it with my kmplayer running it didn’t save the file but returned me to zbrush. and in second attempt it made my mesh wierd and then crashes.
i hav amd phenom2.2 , 4 gb mem , 250 gb hdd. ati 3200 onboard gfx
or
it maybe bcoz i saved the tool after lot of work done.
ive lost countless amounts of time and effort trying to deal with this lame crash. a coworker and i finally figured it had to do something w/ the ctrl + S by the exact same method as you posted above.
seriously pixologic NEEDS to fix this - very unacceptable.
:mad:
seems there’s a lot of users wanting this bug fixed… yet there’s a lot of random little plugins made that are cool… yet don’t really make up for the work lost when you try to save.
the other issue that crashes my zbrush is going to the menu via space bar, or click on my stylus.
i know we’re supposed to check our computer specs etc. my machine is an intel core 2 Quad CPU, running 8 GB of RAM. so i know there’s no issue there, as do most of the people writing on this thread.
perhaps there should be a petition to fix some existing bugs that as quoted in this thread, cost a lot of time on production… like the crash i just experienced. as a user…and someone who promotes the software… all the fancy alpha menu’s could not replace being able to work at the speed of thought without sweating that the next time i enter a menu too quickly or save my work, im going to lose it all.
i love this program… but im eagerly awaiting THE fix. cheers!
this is an annoying bug for sure… but until it’s fixed I would recommend everybody rebind ctrl+s to “save tool as”. Just hold control and click on the “save tool as” button, and when prompted to enter a new hotkey combination press ctrl+s. this will overwrite the existing one and if you’re like me you’ll never see this crash again.
Stumbled uppon this thread while googling the same problem. Just want to add the the list of users and refresh this a bit so hopefully it gets taken care of. I enjoy Z brush a lot but this needs to be addressed.
Same problem here! My “workaround” is, to export the model first as an OBJ. This works every time and so you can save you last step. Sure, the lower meshes are gone (if you not export them as OBJ too) but so you can hold your last step.
iLegacy, to help you a great deal try this out.
Use the mouse or your tablet to go to the save button in the tools menu, do NOT use the hotkey. The hotkey was my problem and it crashed every time. Clicking the button seems to work. Also if you want to reduce the time it takes to save, put all sub objects on their lowest sub d level before saving. This works like a charm for me. Hope it helps you too.
Aberrant
Thank you :), i tried this and it seems to work.
Yeah, googled zbrush crash on save and found this. Surprised the issue has been going on for so long. I’m running Zbrush on 2 machines. One is an 8 core 64 bit Dell workstation with 8 gigs of ram and the other is a home built Quad Core i7 cpu with 3 gigs of Ram (currently 32 bit). Both can handle very high poly counts, and lots of stress in general but I lost the same thing 3 times last night because of this save issue. Looks like I will stop overwriting and using ctrl+s but still, how is this still a problem almost 2 years after this thread started. Hoping maybe 3.5 will put this to rest. I’m loving Zbrush so far and would still recommend it to anyone, great community of users, very generous developers, etc. but I would really hope that this issue doesn’t continue. It’s about the worst/most inconvenient possible crash/bug I can really imagine.
I would have to agree completely. I am almost positive this will be fixed in the next version of Zbrush. For now try to make it a habit to use the save button instead of the Ctrl+S hotkey. I always save incrementally to avoid corrupting past work. I end up with a ton of files but its better than not having my work save at all, or get corrupted.
Also if you prefer a hotkey, theres a link in this thread on a previous page, to a plugin that auto drops sub d levels and goes to the first sub-tool in the stack and saves incrimentaly for you.