Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0a1
2018.2.0f2
Issue ID
1066340
Regression
Yes
[OSX] Going into fullscreen with either hotkey or Screen.SetResolution uses wrong fullscreen mode
How to reproduce:
1. Open attached project
2. See in Player Settings that it has FullScreen Mode set to 'MaximizedWindow'
3. Build & run for OS X
4. Enter fullscreen with the Screen.SetResolution button and exit fullscreen with CMD+F hotkey
5. Enter fullscreen with the CMD+F hotkey
Expected result: in both cases, the fullscreen mode is Maximized Window
Actual result: in both cases, the fullscreen mode is Full-Screen Window
Reproducible with: 2018.2.2f1, 2018.3.0a7
Not reproducible with: 2018.1.9f1
Notes:
Screen.fullScreen does not have this issue
Although in 2018.1.9f1 this issue is not present, the label still incorrectly displays full-screen mode after using Screen.SetResolution and CMD+F
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment