ZBrushCentral

Layer Problem sculpting partially baked into basemesh!?

ZBrush Usage Questions
#1

Hello Zbrushers,
ich have a wired problem on 4.7 64bit.

I have a head sculpt with polypaint.
1 Layer for sculpting Details (pores/wrinkles) no mask no Polypaint.

Now at one point i found out that when i turn that layer off - the sculpting detail of this layer remains in my basemesh with a certain value.Meaning that activating that Layer again result in a way too strong sculpt/added.

I started a second layer with some big dimples and when i reopened that scene the next day - those also were baked in with a low value into the basemesh.like if you click on bake layer,

i never projected,baked or anything else at this modell.

its completley wired and i cant reproduce the effect.It acts like the memory isnt enough and zbrush stops to sculpt on the layer fully,but partially on the basemesh.

sounds wired right?

#2

Have you deleted subdivisions?

#3

not at this point.i have 7 subdivs and about 14 mil polys.at this stage it takes too long to reproject,freeze or similar.So i just stay at highest and modell there.Sometimes i turn off the layer and move areas of the mesh a bit in lower subdiv levels.
like for example the ear or a horn.then i switch back to the highest level.turn on the layers.So i dont want the basemesh modification (moved ear a bit) on my recorded layer.

#4

Layers can be complex to predict.
In some circumstances it allows you to deform when layers are not active. Then when manipulating layers these changes could be lost (or not). For example this happen after creating new subdivisions in a subtool with inactive layers with no information stored. Using deformation in layers is specially problematic.

About your case
If you delete subdivisions when layers are visible these will be printed in the base of the object
If you create subdivisions when layers are visible these will be slightly printed in the base of the object. (This is not new in 4.7) As secondary effect the base deformation is added to the layer deformation creating an increased effect over the initial objective. But this becomes evident only when switching on off layers.
This doesn’t appear when subdividing with layers non visible.
Also for example using the morph target will modify the base layer when no layer is in recording mode. But this can be suddenly lost when creating new layers.

I guess there are some other circumstances when this should be happening, but I don’t think it is random, it is something you did. It would be interesting to know what has triggered it.

#5

3d layers have always been a little finicky. They work but you just need to know how to use them.

I haven’t had time to verify that all of these issues still exist in 4r7p3 but I have done extensive research into them in past versions.

Here is a link to a thread where I call out issues and post workarounds/fixes. Hopefully it helps you.

http://www.zbrushcentral.com/showthr…-3D-layer-bugs

#6

Thanks for your link. And that is only part of the problems of the layers.

I would love if Pixologic makes more priority fixing existing tools or finishing them, specially layer system, subtool organization (that new plugin has no icons or real time updates) and being able to use the polypaint tools in bitmap textures.

#7

Altea, this must have been the problem partially.

zbrush gives a warning,but its not fully helpfull.
if i want to subdivide the mesh while in layer record mode it pops up a warning saying i must
leave record mode or bake all layers to try again (subdivide).

BUT it should say "leave record mode + deactivate layers or bake all layers to try again (subdivide).

otherwise it will imprint the layer infos into my basemehs like you said.

so at one ppoint it seems i went from subdiv 6->7 and it imprinted the infos.

the really really strange thing is about the dimples i added very lately,the had the same imprinted effect in the basemehs- but i never ever switched another subdiv up again.iam on subdiv7 a long time now (2 weeks)!->i see my incremental safes all have the subdiv7.

#8

If you have incremental saves then you should be able to track in what point the problem appears and perhaps what operation has created it (specially if you saved the undos)