Camera: Added divide by zero check FreeCameraTouchInput #12649
Merged
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.
In the forums, there was an issue raised where movement wasn't working on Safari. After some investigation, it was found that the
touchMoveSensibility
property was being used in a denominator inside of thecheckInputs
function. Because of this, iftouchMoveSensibility
was zero, it'd create a divide by zero scenario that would effectively render the camera'scameraDirection
vector to be a vector of NaNs. The fix for this was to just add a check to see iftouchMoveSensibility
was zero and handle things accordingly.Forum link: https://forum.babylonjs.com/t/keyboard-control-not-working-for-latest-universalcamera-in-desktop-safari/31314