Fix wrong camera position calculation when focusing an element#820
Merged
dmarcos merged 1 commit intoaframevr:masterfrom Sep 16, 2025
Merged
Conversation
Contributor
Author
|
@dmarcos this is ready to be merged |
Member
|
thank you! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The calculation I did in #760 was not quite right.
The center was assumed to be in local coordinates but it is actually already in world coordinates, so localToWorld increased the y value so the camera was much too high. The issue is not much visible in a scene where all models are on the ground, it's much more visible on a model in the air. Even for models on the ground, that fixes the glitch when you start rotating after focusing an element.
Before
After:
