In a blank scene:
[ol]
[li]Create a joint
[/li][li]Create a nurbs curve
[/li][li]Add an attribute to the curve: float, 0 min, 1 max, 1 default
[/li][li]Set Driven Key … driver: curve.new_attr, driven: joint1.scaleX (0,0) (1,1)
[/li][li]parent constrain the joint (constrainee) to the curve (constrainer)
[/li][li]Export joint as an animated fbx.
[/li][li]
[/li][/ol]
In the fbx text file, the set driven key’s second key time will be 8200761993330688 , which is over 100,000 frames. (Unity says a time range of 176160, then barfs)
Why? Only happens when:
joint has a parent constraint AND
there’s a set driven key on the joint scale AND
there’s no keys on the driving attribute
A fix is to put a key on the driving attribute. Looks like the fbx exporter will pay attention to this key, instead of the set driven keys, luckily.
Anyone seen anything like this?