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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 1.1-pre.5):
Fixed with: Input System 1.1.0-pre.5