-
-
Notifications
You must be signed in to change notification settings - Fork 4k
Rebrand glTF coordinate conversion to an alternative strategy that is biased towards glTF models #20131
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
base: main
Are you sure you want to change the base?
Conversation
…version (bevyengine#19816)" This reverts commit fb2bbb0.
Co-authored-by: Robert Swain <[email protected]>
Co-authored-by: Robert Swain <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm clicking the approve button as I think backing away from "we will change the default in 0.18" is the right choice given the ongoing discussion.
I have some doubts about the use_model_forward_direction
behaviour (see alternative proposal), but I feel this PR is still a step in the right direction.
Objective
Per long discussion with @superdump (see #19686 (comment)), the new coordinate loading system is still wrong, just now biased in favor of having correct forward semantics for models instead of cameras.
Which is still what I need, but it should not be the new default, as we may well change
Transform::forward
instead.Solution
Since changing forward semantics is a bigger change, let's rebrand the coordinate conversion code and keep it opt-in so that users that don't use glTF cameras get correct semantics in the meantime.
Testing