Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
1
Found in
2019.4
2019.4.7f1
2021.1
Issue ID
1278638
Regression
No
Mouse Position on Y-axis on UWP is broken when display scaling is set to non-100% scaling
How to reproduce:
1. Open the attached "repro.zip" project
2. Build and run on UWP platform
3. Make sure that at least one of your monitors uses non-100% DPI scaling
4. Move the build Window to a monitor with non-100% DPI scaling
5. Observe the difference between the old Input System and Input System Package readings
Expected result: Old Input System and Input System Package readings are the same
Actual result: Old Input System and Input System Package readings are different
Reproducible with: 2019.4.12f1, 2020.2.0b6, 2021.1.0a1 (Input System 1.0.0, 1.1.0-preview.1)
Notes:
- Could not test on 2018.4, because the Input System Package was not yet available in that stream
- The bug only appears on UWP
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0a2, backported to 2020.2.0b9, 2020.1.12f1, 2019.4.14f1
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b9
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.12f1