Search Issue Tracker
Fixed in N/A
Votes
0
Found in [Package]
1.1.0-preview.3
Issue ID
1318271
Regression
No
[Linux] [Input System] Editor does not return correct mouse position values when using position.ReadValue()
Reproduction steps:
1. Download the attached project: "InputSystemMousePositionBug.zip"
2. Open the SampleScene
3. Enter the Play Mode
4. Select the "NewBehaviourScript" GameObject in the Hierarchy
5. Move the mouse cursor outside the left side of the Game view
6. Observe the X value in the Inspector
Expected result: The X value of the mouse cursor goes into negative values
Actual result: The X value does not go into negative values
Reproducible with: Input System 1.0.2 - 1.1.0-preview.3 (2019.4.22f1, 2020.2.7f1, 2020.3.0f1, 2021.1.0b11, 2021.2.0a8)
Could not test with: 2018.4.33f1 (Newest versions of Input System are not available)
Notes:
- Tested on Ubuntu 18.04
- Not reproducible on Windows and macOS
- Mouse.WarpCursorPosition may also be affected by this. The user reported that in their tests it seemed to randomly pick a Unity panel and warp accordingly to it.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version N/A):
Fixed in version 2021.2.0a12
Resolution Note (fix version N/A):
Fixed in version 2020.3.16f1
Resolution Note (fix version N/A):
Fixed in version 2021.1.19f1