New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve transform display in SceneInspector #896
Comments
What does everyone think about this one? We're now showing the world matrix and local matrix, but not any decompositions into translate/rotate/scale. While I think they would be handy, I think they'll also lead to bug reports like "scene inspector rotate doesn't match node editor rotate", where the decomposition of the matrix doesn't give the same result as the rotation that went in to it. Do we omit them on those grounds, or can we do something in the UI to make it clear that this is a decomposition, and the original values are not always to be expected? Any thoughts/ideas? |
@carstenkolve @edmondeng @japmohican @thiasbxl @bentoogood Are any of you really keen on the decompositions? I think it's fine as is, but maybe I'm too used to looking at matrices... |
I don't think you'll find many lighters or td's who are so comfortable With regard to john's point - I'm not totally sure I follow. is the concern On Wed, Jul 23, 2014 at 5:05 PM, Andrew Kaufman notifications@github.com
ben tooogood |
I think his concern is that you might set one rotate value on the plugs, and see a different rotate value in the diff, because matrix decomposition is non-deterministic. |
The simplest example is when a rotation in a single axis goes past 360 - there's no representation for that in the matrix, so 361 degrees would decompose the same as 1 degree. So what you see in your scene inspector is unlikely to be what you typed in to your node editor. I do think having translate/rotate/scale would be handy, I'd just like to find a way of presenting it that doesn't lead to unfulfillable expectations. |
got you. i'd say given that people should understand that the contents of the scene and maybe the labels to the values could be something like 'resultant ? On Wed, Jul 23, 2014 at 5:22 PM, John Haddon notifications@github.com
ben tooogood |
Cool - I'll stick it in then. Any other thoughts on naming? "Resultant rotation", "Rotation component", "Extracted rotation", "Rotation from matrix"? |
For what it's worth, I think my vote would be for "Rotation component"... |
Maybe improve this WHEN Ben is back at IE? thanks! |
'Rotation from matrix' stood out to me too actually. if you call it that, I will come back to IE for sure! On Wed, Jul 23, 2014 at 5:41 PM, yuta shimizu notifications@github.com
ben tooogood |
The various transform components are now extracted out and displayed separately to the matrix as well. Fixes GafferHQ#896.
Display the world matrix and the local matrix. Possibly also show decompositions into translate/rotate/scale?
The text was updated successfully, but these errors were encountered: