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
Describe the bug
Having Space Navigator in project breaks middle click to focus in SceneView.
Usually middle click will move the view and re-center on the clicked point.
With this active, middle click does something but doesn't recenter the view.
To Reproduce
Steps to reproduce the behavior:
Create a scene
Make two cubes with a bit of distance
Middle-click one cube, note camera doesn't recenter
Middle-click the other cube, note camera doesn't recenter
Open ViewportController.cs
in the static ViewportController() constructor, add return; as first line
Repeat the test above
Note that the camera properly recenters
Expected behavior
Scene View behaviour is unaffected by package
Details (please complete the following information):
Issue occurred while navigating editor viewports
Device type [All]
Connection [wired]
OS: [e.g. Windows]
SpaceNavigator Driver version [e.g. 2.0.0-beta.7]
Edit: Might have the same reason as the drift seen (#29), since it seems that the comparison for == Vector3.zero fails since the inputs are actually never fully zero (this is in idle state):
A better way to react to input would be to actually listen for the InputAction.performed event instead of polling every frame and not knowing if data has actually changed.
The text was updated successfully, but these errors were encountered:
Describe the bug
Having Space Navigator in project breaks middle click to focus in SceneView.
Usually middle click will move the view and re-center on the clicked point.
With this active, middle click does something but doesn't recenter the view.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Scene View behaviour is unaffected by package
Details (please complete the following information):
Edit: Might have the same reason as the drift seen (#29), since it seems that the comparison for == Vector3.zero fails since the inputs are actually never fully zero (this is in idle state):
A better way to react to input would be to actually listen for the InputAction.performed event instead of polling every frame and not knowing if data has actually changed.
The text was updated successfully, but these errors were encountered: