I think the problem that Carolly points out isn't quite as bad as you might think. Yeah, we are talking about lots of 3d details, but they currently only support the change of a single dial. So, it would just be a matter of retaining N dial changes....which is N x 16 bytes (or whatever a floating point value is) It's not that bad. You would have to recalculate the position after the undo....but you are doing that with dial changes. At worse, it would be like having 30 automatic pose dots in queue. I doubt that is why they never implimented it. It's probably just a can of worms with lower shiny factor than the other options that fall ahead of it on the list of upcoming features. eric