<div dir="ltr"><div>The mockup looks good to me -- the only thing I would add is that sometimes you want multiple high-poly meshes, although usually that can be sorted out (merged to a single object) before the bake, so it's not critical. I noticed that there are no ray settings like in xNormal. I don't usually mess with the raycast settings, especially if I'm using a cage, and a lot of other software seems to have default settings that basically "just work" -- so hopefully that is what blender will have :)<br>
<br></div><div>wrt Dalai's comment about previewing -- for game assets I preview/check in the target engine<br><br></div>-Aubrey<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 31, 2013 at 11:01 AM, Dalai Felinto <span dir="ltr"><<a href="mailto:dfelinto@gmail.com" target="_blank">dfelinto@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Andy,<div><br></div><div>Keep in mind that the proposal was drafted to make it simple to re-bake the same maps for the same (or different) object(s). So before getting to the specifics it would be nice to see a 'show of hands' on whether this would bring benefits.</div>
<div><br></div><div>Now for the specifics:</div><div class="im"><div><br></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">> Having the per object presets for baking isnt really needed as you would generally want all the maps to have exactly the same settings for margin, AA and use the same cages etc.</span><br>
</div><div><font face="arial, sans-serif"><br></font></div></div><div><font face="arial, sans-serif">If people don't need that control per-object, then sure. It would make things simpler. The advantage of having this per-map is that you can easily create multiple maps for the same type (e.g., Normal) and compare<br>
</font><div class="im"><br style="font-family:arial,sans-serif;font-size:12.727272033691406px"><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">> The workflow I would expect is that the user selects objects as they do now (HP then LP), select the maps they want to bake, the size of the maps etc. and then hit bake with the only difference to now is that they have multiple maps selected which Blender would automatically create with the appropriate suffixes.</span><br>
</div></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">* Do you always use the same UV Map for all the maps you are baking?</span></div>
<div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">* Your propose implies that all the maps are exported externally, which may not fit so well in Blender design in my opinion. Ideally you want to bake the maps and preview if they look good in Blender. That's why we propose to select an Image Datablock for each map.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></span></div><div>Cheers,<br></div><div class="gmail_extra">Dalai</div></div>
<br>_______________________________________________<br>
Bf-gamedev mailing list<br>
<a href="mailto:Bf-gamedev@blender.org">Bf-gamedev@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-gamedev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-gamedev</a><br>
<br></blockquote></div><br></div>