ZBrushCentral

Zbrush 4: Adaptive skin problem

Hello everybody.

I have a problem with generating an Adaptive skin from a Zsphere 2 tool using the new skinning method. I used to turn on the Classic Skinning mode just to explore the difference. And now it’s turned off but it seems that its’ setting still affect the Adaptive skin generation (if I turn the Classic mode on again and make some changes, they affect the skin generation after I turn it off). Even more, none of the settings on a new tab applied after that do not work.

Reloading the tool or the application did not improve the situation. I do not use Zsketch, only basic Zsphere 2 tool. In fact, I have no control over the Adaptive skin generation, except of the Density modifier.

Please help me, I spent a lot of time modelling and now I’m afraid to lose all the work. Thanks in advance.

Could you please provide step-by-step instructions to duplicate what’s happening? Your description is unclear. Thanks.

i have a similar problem but slightly different…I have Zbrush 4 on WinXP x32 SP3, 2gb ram, P4 w/HT 2.8Ghz, Nvidia MX400, the new adaptive skin feature for Zspheres does not work on this machine instead it automatically models in Classic mode, i can turn classic mode off or on but it still models in classic mode even though its set to off. I have a newer machine. Win7 x64, quadcore, 6gb ram, nvidia geforce 9100, and adaptive skin works fine. My guess is that the older machine needs a dependent file/driver. I have the latest updates of nvidia for this but no go. any ideas?:rolleyes:

I have the exact same problem at home and at work. Both times I was on a tool that have multiple zspheres in Subtools. One zshere would adaptive skin correctly, they other would bug out. I just started working on something at home that had 2 zsphere subtools in it, my zsphere tree had the problem but my zsphere scale human did not.

I seemed to solve it my closing the program, opening it back up, cloning the problem zshpere subtool and going to the clone and seeing it it worked there. It did fix it this time, but I remember doing the same troubleshoot at work without it fixing it.

I tried to re-pro it but I couldn’t.