Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1112168
Regression
No
[MacOS] Input.mousePosition returns incorrect results when mouse cursor is not moving and using dual monitors
[MacOS] Input.mousePosition returns incorrect results when
- The mouse cursor is not moving
- Using dual monitors (Game Window on Mac monitor, Unity Editor on the second monitor)
- Game Window -> "Free Aspect" -> "Low Resolution Aspect Ratios" is disabled
How to reproduce:
1. Open attached project "Sweet Breakout.zip" and scene "SampleScene"
2. Have Game Window on your Mac monitor and your Unity Editor on you second monitor
3. Make sure that Game Window -> "Free Aspect" -> "Low Resolution Aspect Ratios" is disabled (choosing a fixed aspect ratio fixes the issue)
4. Enter Play mode
5. Move the mouse cursor on Game Window (the pad/board is following the cursor on x Axis)
6. Stop moving the mouse
Expected result: the pad/board stops
Actual result: the pad/board snaps to a different location
Reproducible with: 2018.2.20f1, 2018.3.7f1, 2019.1.0b5, 2019.2.0a7
Could not test with: 2018.1 and earlier due to the project crashing
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
With the deprecation of the old input system, we are moving users to the new input system package at https://github.com/Unity-Technologies/InputSystem and can also be found in the package manager window of Unity.