ZBrushCentral

ZB3 !Great but I need more umph I guess...

Model being worked on inzb3 but 30 minutes in a Crash…oh pooh!
I think my system is not sexy enough for zb3 so will switch licence’s to my mumma board.:sunglasses: Only thing is im scared I wont get reactivated and be un zb3’d for the weekend(trembles lol)!:confused:

Oh I cant wait to get into the programme properly.The details on this were my efforts after 30 mins of looking around .:smiley:
Imagine what can be done with real knowledge.Scary!Brilliant!:bulb:

Anyways,goodluck everyone and I hope others waitng for the link get sorted soon.What a downer seeing everyone working instead of your link.But be nice gutys,its frustrating but its a free kind gift remember !Oh and I was aying that before my link came through by the way!!:wink:
cal

Attachments

crash1.jpg

yeah same goes for me, i need more power too =(, i get errors like that too, cool sculpt btw. now to figure out subtools. good luck on not crashing!

It depends on how much ram you have, and whether youre working on a 64 bit OS, I guess. But Z3 does seem to actually get unstable and crash with higher raw polygon counts, long before actual sculpting perfrmance becomes unacceptable.

For me, on this ancient single core AMD 64 3500+ with 4 GB of reasonable speedy ram…I get up to just about 10 GB of raw polygons before it becomes unstable and crashtastic. Im told this number increases significantly with 64 bit OS.

What you want to do is find out where the practical raw poly limit is for you machine, and not exceed that…use the HD poly function to go beyond that point.

I seriously doubt that crashes are solely linked to poly count. I regularly crash while working out some simple zsphere characters i.e. less than 100 spheres. Adaptive skin preview at density 2, nothing that is taxing on my system, and yet it crashes about every 20 minutes. This is a stability issue in the program which I hope is fixed soon. I understand that bugs are a reality, but I can’t help but feel that I’m in a public beta of Z3 as there is ZERO chance that I will use this version in a production environment. The features are AMAZING. But I need some stability.

I’m sure they are not solely linked to poly count. The Op framed his issue with hardware though, so thats how I commented.

If you cant use z3 in a production environment, then you couldnt use z2 either, or MB for that matter. These are just wildly complex programs on the cutting edge of technology, and they have crashy quirks. Some very specific issues and occasional failed startups aside, Z3 has proven much more stable for me than z2 ever did, unless Im pushing more poly than my system can handle with stability. Ive even grown so bold as to go as long as 5 minutes without saving in z3, which is something Id never do in z2.

But with more Windows entities and hardware configurations out there than Z2 ever had to deal with, experiences can certainly vary, and we can all hope for continued attention and patching.