Closed GoogleCodeExporter closed 9 years ago
Original comment by ble...@gmail.com
on 25 Aug 2011 at 10:50
We are double checking to make sure this is the best workflow to use.
In the meantime one way to force the normals to write out is to create a
noNormals boolean attribute and make sure it is set to false. The double
negative will always generate normals.
The reason we try to avoid writing out normals when it appears that they are
default is because of a bug in some versions of Maya where loading them back in
is waaaay too slow.
Original comment by miller.lucas
on 25 Aug 2011 at 11:28
Fix implemented here:
http://code.google.com/r/millerlucas-dev/source/detail?r=cf06a89fbeda595effb7c75
dc484b357d743f822
I moved the hard edge loop check inside the check for !userSetNormals so cases
where at least one of them was changed by the user, we won't need to do a
redundant edge check. (since the normals will get written anyway)
Original comment by miller.lucas
on 26 Aug 2011 at 1:19
Original comment by miller.lucas
on 29 Aug 2011 at 5:03
Original comment by miller.lucas
on 19 Sep 2011 at 9:32
Original issue reported on code.google.com by
shinc...@gmail.com
on 18 Aug 2011 at 3:44