Re: Caching Angular Velocity

2012-11-14 Thread Xavier Lapointe
Looks like your vector has flipped? Could you just calculate the shortest path and compare the values? I had some trouble as well at some point with this.

Re: Caching Angular Velocity

2012-11-14 Thread Jonathan Laborde
The shortest path from what to what? Keep in mind that this is from a loaded pointcache, I don't have access to the previous frame, and I don't to load it twice. On Wed, Nov 14, 2012 at 3:27 PM, Xavier Lapointe xl.mailingl...@gmail.comwrote: Looks like your vector has flipped? Could you just

Re: Caching Angular Velocity

2012-11-14 Thread Ahmidou Lyazidi
Current frame -1 should normally give you the previous frame. 2012/11/15 Jonathan Laborde labordeor...@gmail.com The shortest path from what to what? Keep in mind that this is from a loaded pointcache, I don't have access to the previous frame, and I don't to load it twice. On Wed, Nov

Re: Caching Angular Velocity

2012-11-14 Thread Jonathan Laborde
Well yes, of course. What I meant is that I don't want to recalculate on a loaded cache something that has been already calculated in simulation, and load the same cache file twice for every frame. On Wed, Nov 14, 2012 at 4:14 PM, Ahmidou Lyazidi ahmidou@gmail.comwrote: Current frame -1

Re: Caching Angular Velocity

2012-11-14 Thread Xavier Lapointe
What I meant is: Python 2.6.6 (r266:84292, Jun 18 2012, 14:18:47) [GCC 4.4.6 20110731 (Red Hat 4.4.6-3)] on linux2 Type help, copyright, credits or license for more information. 1224.001 % 360.0 144.000998 360 - 144.000998 215.999002

Re: Caching Angular Velocity

2012-11-14 Thread Jonathan Laborde
Apparently Xaview knows something that I don't! So it seems there's a way to revert it back to the original value, that's pretty cool! How about the axis that changes? Sometimes it's 0,0,1, sometimes 1,0,0, 0,0,-1, etc... On Wed, Nov 14, 2012 at 4:37 PM, Xavier Lapointe

Re: Caching Angular Velocity

2012-11-14 Thread Xavier Lapointe
I think you could just apply this logic when you output, unless when you use the cache again it starts flipping again, which would be utterly odd. Unless you deal with a specific case of super high revolution, from one frame to the other it shouldn't spin more than 360 ... I guess. As for the

Re: Caching Angular Velocity

2012-11-14 Thread Jonathan Laborde
I tried to cache the same original value in a custom attribute, Alan was suggesting that maybe AngularVelocity was a Softimage dedicated attribute that had to follow certain rules or something. Alas, with a custom rotation attribute the restult is the same. Softimage is messing with my values!

Re: Caching Angular Velocity

2012-11-14 Thread Alan Fregtman
I suspect it might be converting those values to quaternions internally, and well, you can't have revolutions in quaternions. I don't know off the top of my head what to do, but if I have an eureka moment I'll let you know. On Wed, Nov 14, 2012 at 5:05 PM, Jonathan Laborde