Search Issue Tracker
Fixed in 1.1-pre.5
Votes
1
Found in [Package]
1.1.0-preview.2
Issue ID
1304974
Regression
No
Input System returning mouse position (0, 0) when clicking on Editor and then clicking the Game View
How to reproduce:
1. Open the attached project
2. Click Play
3. Click somewhere on the editor
4. Click somewhere in the Game View
Expected result: The mouse position is the same in all Input Action Phases.
Actual result: The mouse position is (0,0) for Started and Performed phases and correct for the Cancelled phase.
Reproducible with: 0.9.0-preview, 1.0.0-preview.3, 1.1.0-preview.2 (2019.4.18f1, 2020.1.17f1, 2020.2.2f1, 2021.1.0b2, 2021.2.0a1)
Could not test with: 0.2.10 (console errors after importing package)
Workaround: Use Mouse.current.position.ReadValue() to get the mouse position
Notes:
1. Input System version 1.0.0-preview.3 all phases return (0, 0)
2. Input System version 1.0.0-preview.2 and below Started and Performed phases return correct values and Cancelled returns (0, 0)
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note (fix version 1.1-pre.5):
Fixed with: Input System 1.1.0-pre.5