Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X
Votes
1
Found in
2019.3
2019.3.2f1
2020.1
Issue ID
1221634
Regression
No
[Input System] Mouse.current.position value is offset by 1 pixel compared to old system's Input.mousePosition
Steps to reproduce:
1. Open the attached project (case_1221634.zip)
2. Enter Play Mode
3. Move your mouse around
Expected result: Mouse coordinates of the new Input system match the old system
Actual result: Mouse coordinates of the new Input system are always offset by 1 pixel in either Dimension
Reproduced in: preview-0.2.6 (2019.3.3f1), 1.0.0-preview.5 (2020.1.0a25)
Cannot test with: preview-0.2.1 and earlier (Assertion failures)
Notes:
- The issue is reproducible in both the Editor and Player
- If the mouse cursor is placed in any corner of the window, the positions reported match
- If the left mouse button is clicked, the coordinates reported by the new Input system are "snapped" and match the old system's
- If the mouse is "flicked" and quickly lifted, the new InputSystem will incorrectly report its position
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a16
Resolution Note (fix version 2020.3):
Fixed in 2020.3.31f1