We're starting to do some per-node keyframe compression here to reduce
our data size and improve our data quality. For one reason or another we
haven't needed to do it until now.

Our initial tests were a bit naïve and we ended up with a) jitter and b)
not much reduction in size. We're improving our error metrics so that
endpoint information is going to be used but I suspect this won't help
the size at all. 

I've heard people mention adaptive and optimization methods in relation
to this problem. Can anyone point me in the direction of some decent
reference material for this? 

Are their any relaxation metrics that people have found safe to use? 

On this first pass we're stuck with linear keyframing, because we just
don't have the cycles in game to go to splines. I know this would help a
lot, but it isn't an option. 

Thanks in advance,

Ian

-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
GDAlgorithms-list mailing list
GDAlgorithms-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gdalgorithms-list
Archives:
http://sourceforge.net/mailarchive/forum.php?forum_ida88