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 <[email protected]>wrote: > 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! > > > On Wed, Nov 14, 2012 at 4:58 PM, Xavier Lapointe <[email protected] > > wrote: > >> 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 flipping, I can't really tell, could be many things. >> >> Maybe other guys will have some points to add as well. >> >> Cheers! >> > >
