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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 1.1-pre.5):
Fixed with: Input System 1.1.0-pre.5