Skip to content
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

Fixing Nan errors in Camera Frustum Mesh #1397

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

emily-howell
Copy link
Member

Issue was that when normalized, the look vector had a slight floating point imprecision that caused this to try and calculate a new up vector. Because the up vector was being rotated based on that floating point imprecision, it was trying to rotate around a (0,0,0) axis which caused nan values

… point imprecision that caused this to try and calculate a new up vector. Because the up vector was being rotated based on that floating point imprecision, it was trying to rotate around a (0,0,0) axis which caused nan values
@emily-howell emily-howell linked an issue Oct 10, 2024 that may be closed by this pull request
@emily-howell emily-howell self-assigned this Oct 22, 2024
@cyrush
Copy link
Member

cyrush commented Oct 22, 2024

@emily-howell can we add a test that exercises one of these cases?

Worried about the divide + mult impact on other cases.

Is it a case where the look at and position are very clost?

Is it possible to fix this before the normalize?

@emily-howell
Copy link
Member Author

For sure. Let me put together some test cases for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

investigate nans in camera frustrum mesh
2 participants