Open GoogleCodeExporter opened 8 years ago
OgreMeshy uses Ogre1.8, so this should be added.
Original comment by goatman.py@gmail.com
on 18 Jul 2011 at 3:55
I'm working through getting normals exported in one of my projects, and it
seems that the pose indices written by the exporter are off-by-one. i.e. in
the xml output, the poses are tagged with indices 0 and 1, but the keyframed
poserefs indicate index 1 and 2.
It is possible this is because of some wierdness in the way my shape animations
are keyed (2.5 support for this seems a little undercooked).
Once i have normal-enabled animations correctly playing back in my code i will
submit a patch.
Original comment by pete.mar...@gmail.com
on 19 Jul 2011 at 2:07
Small update - Apparently updated normals are not made available through python
for animated meshes - apparently normal calculation is deferred until
display-time, so the normals will have to be recalculated for each frame by the
exporter.
It would probably be possible to create a temporary proxy object with the
displaced vertices, get blender to update it and then read back the normals but
this is likely to be slower than just manually calculating face and vertex
normals directly.
Original comment by pete.mar...@gmail.com
on 22 Jul 2011 at 11:54
Original comment by goatman.py@gmail.com
on 18 Aug 2011 at 1:25
Original issue reported on code.google.com by
pete.mar...@gmail.com
on 18 Jul 2011 at 1:02