I've been writing some code that makes some objects fly around and Ken's interpolation code makes it look nice and smooth. However, in doing so I experimented a bit with position update frequency, wondering what the slowest rate I could use is, especially when the velocity I was trying to show was constant. There's effectively a maximum speed that the interpolation achieves, so that if you update less than several times a second (e.g. once or twice a second), the object has a really jerky start-stop motion.
Is there a quick fix for this? Or should we just let that issue be, and later add concepts of velocity and acceleration to A3DL? Would it be possible to add position-interpolation-speed and orientation-interpolation-speed properties to Object3D? Or position-update-freq-hint and orientation-update-freq-hint? These would be advisory parameters for the interpolation code, that would let it choose object velocity in the interpolation. I like the idea of update-freq-hint, because it's not implying anything other than what the server side is doing (updating the property periodically). However, the client side would always be one step behind, so it might make things look pretty glitchy. Thoughts? Reed _______________________________________________ vos-d mailing list [email protected] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
