Extracting normal maps from very high poly models in ZBRUSH?
polycounter lvl 10
Been using ZBrush for a while now for high poly models with no uvs.So since ZB can handle very high polys compared to other apps I was wondering if there is a way u can select the high poly model,the low poly uvied one and extrct the normal and AO maps for the low poly.I can't find it even in Multimap extractor.I am guessing the only way is to project the details of the high poly mesh to the lowpoly after subdividing it to a level that it can take the details of the high poly and then go to the lowest level and extract from highest subdivision level of the reprojected low poly.I hope this isn't the only way as Mudbox even has this feature I speak of.
I don't want to use decimation master as I might lose some details.I tried exporting it without decimating into xnormal and it said out of memory or something like that.Maybe I would try it again.
I don't want to use decimation master as I might lose some details.I tried exporting it without decimating into xnormal and it said out of memory or something like that.Maybe I would try it again.
Replies
You then bake from there.
Mudbox is a different beast since it was designed from the get-go as a full traditional workflow concept (unlike ZB which started like a 2D app), so take it for what you will.
Also, decimation master shouldn't be killing ANY of your details? Could you post an image of what you mean?
Try aiming for around 500K, also, remember that ZB doesn't smooth out the your details, it never did, if you zoom in, even at 4 million you will see the unsmoothed details. So yeah, what make look as a 'loss of detail' is actually ZB showing it's true colors, in any other app, it should look fine.
For xNormal, 64 bit is recommended, but even in 32 bit, it shouldn't run out of memory for baking. Try increasing/decreasing the bucket size, and don't use any AA.
You´ve got to be kidding right?
You are kidding right?With all the powerful capabilities of the great ZB,it lacks one of the most important yet simple feature for sculpting apps?Why do they do that?Is it that the devs of ZBrush can't add this feature or what?I am beginning to get fed up with apps that are really cool but lack some simple things they should have had from the first release,so one has to look for another app to carry out such tasks.I guess I will use the decimation master and xnormal then.Thanks .
@SpeCter
I can't beliveth it either.
@cryrid
I am hoping at some point they add it but maybe they feel they shouldn't be bothered since xnormal does the job of baking for its users pretty well.
All it takes is importing a clean uv´ed lowpoly recreating higher subdivisions and bake then
.
Personally, I don't mind. If I have a sculpt obj and I have a low poly mesh obj, loading them in xnormal isn't going to take any additional effort. It's also going to give me a lot more options for baking maps, and more control when it comes to things such as setting up a projection cage or choosing the tangent basis I want to work with.
A) You need to re-project the high detail as MESH to the new MESH since ZB is not traditional and doesn't bake High to Low separate mesh, need new mesh to replace old mesh.
I didn't any of the extra info for my own health you know *coughcough*.
I understood what u wrote.I am just a little surprised that it does not have that workflow like in Mudbox or other sculpting apps and its very powerful.I was guessing it was hidden somewhere in ZB's complex and infamous UI.Thanks for replying,Ace.
@cryrid
I agree.Its not really much work to use xnormal.I will just study on how to use the decimation master to get the best out of my highres model.
Thanks for the replies,everyone.Now,gat to go back to ZBrushing.
I have been getting very bad normal and ao maps.Then I had to import the very heavy high poly model into Maya(assuming u can't scale meshes in ZBrush using numbers as it lacks a real 3d world) and increased the scale to 4 and did the same for the lowpoly model.Imported back to xnormal and the normal map came out looking okay,the ao map had some black patches.Any way to get very clean,more precise maps and also is there a way I can increase the scale in xnormal without importing meashes into 3d app for scaling?
The model looks very good with the hardware renderers but sucks with the Maya software and mental ray renderers.Why is that?
i recommend setting up the cage in an external software, like max or maya, for full controll.
if you want cleaner maps increase the ray-count for AO´s and the mapsize for normals. then scale the normal down to the desired resolution.
i do all the baking in max cause it shows you very clearly were your maps dont project properly, so you can adjust the cage perfectly.
also get used to switching applications frequently, cause there is always one, that does a certain task way better then all the other ones.
having a good folderstructure minimizes the caused delay.
You can change the scale in zbrush. There's an Export tab at the bottom of the Tool menu where you can increase the scale. You want to make sure the number stays consistent between your high and low poly.
Thanks a lot,..I increased the scale of both the low and high poly mesh to like 100 in xnormal and the error window did not come up.Rendered out my normal and ao maps.
@EarthQuake
No worries.The renderers work well with the maps now.I just had to reverse the normals on the model.Mental ray does seem to be displaying some wierd stuffs though while the hardware renderers displays everything correctly.
@Goeddy
I am not gonna lie here.I hate the 3d viewer of xnormal,the view sorts of lags,camera navigation wierd,the UI thingy is confusing and I can't even comprehend moving vertices of a cage in it.I know of someone who uses Maya for baking normal maps,says mental ray baking gives way better results and u can manipulate the cage.The only thing that might be a problem is viewport lag as a result of the high poly mesh.I remember using Mudbox for my 3d works then.I used it for extracting normal and ao maps and they turned out awesome.What I love about MB maps is how well they render with mental ray and I never had to modify a cage to get good results.The only problem is the huge file size MB becomes when moderate work is saved in comparison to ZB.Xnormal seems to work more for hardware renderers or viewport renders.
I am one of those people who don't enjoy moving for one app to another as it encourages creating files all over the place to export stuff.I also like orderliness and a straight forward workflow.Too many apps,kinda create confusion and disorder especially when with files saved all over the place and in specific formats.I kinda miss Mudbox though.All I used before were:
Maya-base modeling,uvmapping;Mudbox-detailing,baking,reimporting uvied low res model,load in baked normal and ao maps and painting all textures I need.Topogun-retopology/creating mesh like cloths,hair e.t.c.
-The only backdrop to this workflow is speed.Maya modeling tools isn't built for speed modeling.
Now I use or trying to get used to this:
ZBrush-freeform modeling/sculpting,retopology;Maya-uvmapping & baking cage modifications;Xnormal-baking normal and ao maps;Zbrush-polypaint diffuse map on high poly;Xnormal-bake diffuse map;Photoshop-paint more details and make other maps.
-with zbrush,one can create models fast,but the movement from one app to the other is frustrating.
@Popeye9 & Pivot
Thanks for the heads up,did not know there was some options lurking behind the Import and export pallete in Tools.Thats what happens when u have a UI like that in ZBrush.