Does This Look Familiar?

[user_deleted]

Problem... help..

When I bake simulation on a constraint-driven object in this one scene I'm working on, I get bizarre results:

The keys get shifted + or - 360.... it doesn't matter almost, since the rotation is a full circle everything LOOKS normal int he scene, but... it's a mess if you try to resample the curve or work with it in any way.

I can't figure out what I'm doign wrong.... I can clean this up by hand in 2 seconds, but I'm writing some automation tools and they should not spawn this kind of mess....

Has anyone ever seen this?

[joojaa]

Well thats because thats exactly what the constraint sees in the world. You can easily put a step limiting expression in play or do a full ierarchy traversal like the one constraint download on high end does.

[user_deleted]

hm - is this what you're talking about?

QUOTE
This script is a good demsontartion of what mel can do but SHOULDNT. Also incidentaly its in pure contradiction to the spirit of DG. However in this case its justified because of the horrible problems in doing it right!

what do you mean by "step limiting expression"? Are you talking about re-coding the bakeresults proc with some kind of max/min delta test?

Which is better? That or realOri?

[joojaa]

Well real ori is a bit heavy but its definitively better, anyway since you bake its a no issue later.

Anyway you can make a simple caching expression that looks something like this. (writing from top of my head)

CODE
global $previous;
if (frame==0)
  $previous=yourConstOut.Attrib;
$value=yourConstOut.Attrib;
while ($value-$previous>180)
  $value=$value-360;
while ($value-$previous<-180)
  $value=$value+360;
$value=$previous;
attrib.toBake=$value