Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
5
Found in
2019.3.0b7
2019.3.0f3
2020.1
Issue ID
1213982
Regression
Yes
Mouse coordinates are not relative to the game window when getting them from EventType.ScrollWheel's mousePosition
How to reproduce:
1. Open the attached project
2. Build the project
3. Open the built project in a Windowed mode
4. Use the Scroll-Wheel in the top-left corner
5. Inspect the "Last mouse position"
Expected result: Mouse coordinates are relative to the game window
Actual result: Mouse coordinates are relative to the monitor's screen
Reproducible with: 2019.3.0b7, 2019.3.0f6, 2020.1.0a21
Not reproducible with: 2017.4.36f1, 2018.4.16f1, 2019.2.19f1, 2019.3.0b6
NOTE: Issue doesn't reproduce on Mac
Links to docs:
1. https://docs.unity3d.com/ScriptReference/Event-mousePosition.html
2. https://docs.unity3d.com/ScriptReference/Screen-width.html
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2020.1):
Fixed in Unity 2020.2.0a15
Resolution Note (fix version 2020.1):
Fixed in Unity 2020.1.0b14
Resolution Note (fix version 2019.4):
Fixed in Unity 2019.4.3f1