Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.34f1
6000.0.0b11
Issue ID
UUM-59482
Regression
No
Screen.fullScreen is set to "False" when Display.Activate is used
How to reproduce:
1. Open the attached project "FullScreenFalseRepro.zip"
2. Build And Run the project
3. Exit the Player
4. Open the Player log (%USERPROFILE%\AppData\LocalLow\DefaultCompany\FullScreenFalseRepro\Player.log)
Expected results: "Fullscreen State" is True
Actual results: "Fullscreen State" is False
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0b1
Reproducible on: Windows 11 22H2
Not reproducible on: No other environment tested
-
ionutparvu
Apr 10, 2024 09:01
In the current implementation of the Multi Display in Windows Standalone, when a secondary display is created the main window will be changed with a Resolution change request, with the resolution depending on what mode the game is FullScreen(display resolution) or Windowed(maintains the resolution), this request will make the main window windowed, and create a windowed window for the second display.
The resolution change will take effect the next frame therefore the reason why it takes two frames for Screen.fullscreen to be false. Due to the fragility of the Multi Display implementation, we consider it to be dangerous to fix this issue and I think a workaround for this issue is to make a difference between single Display and Multi Display. When the game is on multi-display (this can be done by checking if there is more than one display active Display.displays[k].active ) and see if the PlayerSettings.fullScreenMode, as this will dictate the resolutions of the windows that are handled by Unity.
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Our ISS customers’ bug reports have a higher weight than normal, and this is accounted for in the decision. We hope to be able to work with you on finding a suitable workaround in the short term. Today, however, we will be closing this case.
Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.