• Editor
  • Request: Make graph view values match selected axis mode

I'm noticing that the graph view always shows values relative to the "parent" axis, for example in the next screenshot "parent" is selected and values match:

But if I switch to either "local" or "world" then the graph view keeps showing values relative to the "parent" axis:

My guess is that keys are always stored relative to parent axis but, while editing animations sometimes I prefer to switch to the other axis modes so I wonder if it would be possible for the graph view do a conversion to match the selected axis mode.

Related Discussions
...

We did consider it, but it's a bit tricky. For example, consider if you increase translate X when the graph is showing world axis values, then likely both the local X and Y would change (which are the values actually being keyed). This may not be clear to the user. It also creates a bit of a disconnect for when you have translate X and Y separated: when you choose to show the curve for translate X, it's a little surprising if adjusting the key values changes both X and Y.

We may still do it in the future, but it's a complex enough change that I don't think we'll have it done for v4.0.

I see, also it could be a bit confusing to the user if not aware of what is going on. No worries, I can just switch to "parent" mode when needed.

Thanks for the reply!

Sure, it's always interesting to think how things can be improved.

There's an even bigger issue with the idea: the world values between keys cannot be described with a Bezier curve. For example, translation between keys on the world axes can be affected by parent bones, which can adjust the value any which way. We could compute the value at some number of points between the keys to give an idea of how the value changes over time, but it wouldn't be a Bezier curve and couldn't have handles for adjusting it.

Yes, the transparency and openness to suggestions is very appreciated.

Mmm I think I see what you mean, if I move the parent bone it will change the keyed world values for the child bone, and Bezier curves don't work there for that same reason (world values could change mid-animation if parent bone is moved).

Since this seems to be complex enough and may or not be implemented in the future, I wonder if it would be a good idea to add a small note in the documentation mentioning that the graph always works with parent values, just to avoid users getting confused about why the graph is showing different values than the toolbox.

Agreed, we'll definitely mention it in the documentation. We should certainly write some documentation! :scared: