You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is due to the previous refactoring for rendering optimization. There is no more requestAnimationFrame called for the mouseMove event. That behavior is far from perfect but approximates the classic FPS head movement better than the former behavior (in my opinion). This is easy to change, but the question is: which solution is more ergonomic (given that pointerlock is not available)?
Previously, just having the pointer in either direction was enough for the view to move. Now, the mouse needs to be moved for the camera to turn.
The text was updated successfully, but these errors were encountered: