Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2018.4
2019.4.9f1
2021.1
Issue ID
1282412
Regression
No
Cursor.LockState locking out of the screen when using two monitors with different scales
How to reproduce:
1. Set one of your monitor's scale to the highest scale (170% or 200%) in Windows Display settings
2. Open the user's attached "LD47" project
3. Drag the Editor's window to your other monitor
4. Enter Play Mode
5. Press the Esc key to make the cursor visible
Expected result: The cursor is in the center of the Game View window
Actual result: The cursor is below or above the center of the Game View window or even outside the Game View window
Reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.6f1, 2020.2.0b7, 2021.1.0a1
Tested with:
- 2560x1440, 225% (Main monitor) and 1920x1080, 100% (second monitor)
Note:
- Two monitors are needed to reproduce the issue
- Setting the main display's scale, and testing on the second display, the cursor appears below the center. Setting the second monitor's scale and testing on the main monitor makes the cursor appear above the center
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2021.1):
Fixed in 2021.2.0a6