VRMLLoader: Make sure rotation axis is normalized. #28162
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
VRML files can contain non-normalized rotation vectors, whether correctly or incorrectly. This change loads such files safely, and has no impact if the vector is already normalized.
Mugen87
approved these changes
Apr 19, 2024
Mugen87
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Three.js AxisAngle apparently requires a normalized axis vector. VRML may also, but I had many files (converted from VRML 1.0) that contained un-normalized axis vectors.
Whether there is a defect in my VRML data or not, normalization is idempotent and can only help.