alexander.zubov Posted February 2, 2012 Share Posted February 2, 2012 No matter what I do, I get this: http://i.imgur.com/b5LP8.png Normal map bakes fine in Blender. Link to comment
manguste Posted February 2, 2012 Share Posted February 2, 2012 Hm, that's strange. Can't reproduce it. Maybe the polygons are too small? Try increasing the mesh scale when exporting. Link to comment
alexander.zubov Posted February 2, 2012 Author Share Posted February 2, 2012 Apparently it's the model scale :/ I had to scale it up on export 20x and I still have some small artifacts. Thanks. P.S. Why when I load model to NormalMapper, it's not being passed onto the Ambient Mapper? I had to load it again. Link to comment
manguste Posted February 14, 2012 Share Posted February 14, 2012 Because these are basically different standalone tools under one hood and they manipulate on different set of entities. Link to comment
alexander.zubov Posted February 15, 2012 Author Share Posted February 15, 2012 It's a bad design :/ Ambient mapper and Normal Mapper need model at the different scale (ambient mapper is super slow on the huge model that works fine for normal mapper). Twice the work. Link to comment
ulf.schroeter Posted February 15, 2012 Share Posted February 15, 2012 It's not bad design, the speed difference is related to the much higher calculation complexity for AO... Link to comment
alexander.zubov Posted February 16, 2012 Author Share Posted February 16, 2012 Heh, tell that to xNormal or even Blender :) Link to comment
manguste Posted March 1, 2012 Share Posted March 1, 2012 Use whatever tool is more convenient to you, no one is holding a knife to your throat :) Our artists use different tools as well depending on the result they want to achieve (or their mood, or what else is in the air). The more rays are traced, the longer it'll take for AmbientMapper to create a map. And NormalMapper and AmbientMapper cannot be compared as they perform different calculations. Link to comment
Recommended Posts