Zbrush 4 loaded with one of my recent W.I.P just didnt take to kindly to my pose.
Same file, different result.
it says in the documentation that layers might not come in correctly.
go into 3.5 export out that “pose” layer as a .obj
open up your model in 4 and import that obj as a layer…you should be all set.
I was just about to post a long discussion on how the 3.5 layers aren’t coming in well, I guess I missed that in the documentation.
On one of my models a pose layer does nothing when it is turned off and on, (so it’s stuck in that pose ) one has terrible distortion, one has a layer imported as super strength (need to set it to -1 to get it back to the 3.5 ‘off’ state, and strength 1 is equivalent to about 1.5 in zb 3.5.)
Worse, going up to the highest subdivision and clicking to enable a hidden layer causes ZB to crash. (Note the layers are one level below the max subdivision)
Also, highlighted by the crash mentioned, there’s no way to tell what the subdivision a layer is currently set for, which makes it dangerous if you forget 
These problems don’t seem to occur with layers created in ZB4.
How do you import an obj to a layer? Did you mean subtool?
nope. a layer.
i.e.
go to the highest subD level. make a new layer. go to import, select the mesh that should be a “layer” the mesh will update to the new pose inside of that layer which can be toggled again like before.
no, I suppose what you have to do is exactly the following:
open you file in ZB3 wher you originally create it . enable the layer at the given subdivision level, export the tool at this stage, disable the layer, delete it and save the file. then open that file in ZB4 go up to exactly that subdivision level and import the obj which you have previously exported.
if you have created a layer before, you should then be able to adjust the imported changes just as before with this layer.
so for example: a ZB3 head with 6 subdivision levels and a huge scar and added on a separate layer to the face on subdivision level 5.
open ZB3 head > dial up to the level 5 with teh scar layer> have scar layer fully enabled and visible> export at this stage as an obj. disable the layer and delete it, so the scar is gone> save that model as usual as a ZTL file - let’s say ‘scarfaceTransitions_Zb3-zb4.ztl’ > open scarfaceTransitions_Zb3-zb4.ztl in ZB 4 > create a fresh layer ( which you now in ZB4 have to do on highest subdivision level)- name it ‘Scar’ dial down to subdivision level 5 ( where you originally had the scar), import your obj and there you have your scar and can probably turn it on and off on your new scar layer.
Hey wow I had no idea you could do that, thanks for the awesome info! That worked like a charm, and also lets me get rid of whatever was causing a crash in one of the layers.
and hey, that also lets me recover a pose that I abandoned when i accidentally deleted the tpose layer. cool!
it will also save you on file size when you get to doing a ton of poses for an art director…or if you’re just testing stuff. A great way to keep your layers without actually have to commit to them. Just make sure you don’t change the point order and you should be all set.
glad we could help you
Thanks guys, thought I mite have to end up doing that, shame I have 1000s of Ztools 
This one has several layers, some tools have tons, had better get to work I guess, but there again, I have no reason to not use ZB3 at this time so il continue to work as I was in ZB3.
Iv had to ditch some layers, I could produce a displacement map for the higher level layers, but quality is just not the same as the raw data. You cant go exporting a 15mil polycount obj and not expect poor ZB not to crash on import, if it was 64bit then maybe.
Delete.
Please try the following…
- Load the tool in 3.5, Hide all layers and save the tool.
- Load the tool in Z4, turn on layers.
That worked doing it that way, thankyou. I had already tryed everything els like importing a lower sub d of the pose which did update it fine, but after turning it off, then back on, the mesh folded up, same even if morph target was stored.
Thanks.