Non normalized quaternions
Posted: Thu Jun 07, 2012 1:43 am
Hello, I'm developping a middleware app with NatNet and the V120:Trio.
It seems with the 2.5 beta 2 of tracking tools, that sometimes, Trio sends non-normalized quats. This is my guess because when my end application convert it to Euler Angles, it sometimes goes NaN (undefined) causing the app to send the 3D entity "into space".
This is just for info. I solved the problem by normalizing the quat sent by the Trio. Then my app was functionning normally, without the above bug. I'm not a math expert but as far as I know, for 3D displacement one should only use normalized quats.
Can you take a look at this? Thanks
Can
It seems with the 2.5 beta 2 of tracking tools, that sometimes, Trio sends non-normalized quats. This is my guess because when my end application convert it to Euler Angles, it sometimes goes NaN (undefined) causing the app to send the 3D entity "into space".
This is just for info. I solved the problem by normalizing the quat sent by the Trio. Then my app was functionning normally, without the above bug. I'm not a math expert but as far as I know, for 3D displacement one should only use normalized quats.
Can you take a look at this? Thanks
Can