Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
10
Found in
2018.1.0a1
2018.1.0f2
Issue ID
1047005
Regression
Yes
Cursor.lockState is ignored after Alt+Tab
Reproduction steps:
1. Open the attached project "CursorSample_Project";
2. Build the project for MacOS or Windows;
3. Open the built project;
4. Alt+Tab (Command + Alt) to another window and then Alt+Tab back to the build.
Expected results: the cursor is still locked in the point it was locked before losing focus on the built project window.
Actual results: the cursor acts just as Cursor.lockState would be set to None.
Reproduced on: 2018.1.0a1, 2018.1.5f1, 2018.2.0b9, 2018.3.0a2.
Not reproduced on: 2017.3.2f1, 2017.4.5f1.
Reproduced both on MacOS and Windows
Workaround: check the "Run in background" option in the Player settings.
Fixed in 2018.3
Comments (2)
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
- Render Graph Execution errors when using GPU occlusion culling with 'Opaque Objects' frame setting disabled on a Camera
- Animator window: “Delete” menu item not greyed out for Base Layer context menu
- Resetting “PC_RP Asset (Universal Render Pipeline Asset)” causes Game view to become black and throws Renderer and NullReference errors in the Console window
- [Mobile] Player Crash on scripting_invoke_profiler_begin when the built Player Scene has an empty UIDocument and is built on IL2CPP
- Unnecessary Warnings are logged when running Player with -batchmode -nographics
martin-sustek
Jul 23, 2018 17:50
Even with the “Run in background” enabled, the behavior is different than before - after switching back, the cursor is on different monitor (multi-monitor setup) and you need to click back into the window.