Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
0
Found in
2021.1.0b9
2021.2.0a5
Issue ID
1314460
Regression
Yes
Black screen after switching from Fullscreen to Windowed on a Linux build
How to reproduce:
1. Open the user attached project (Resolution.zip)
2. Open the "SampleScene"
3. Press "Ctrl+B" to build and run the project
4. In the player press "1" to change the player's resolution to 1280x720
5. Press "F" to go fullscreen followed by "W" to go back to windowed mode
Expected result: The player continues to render normally, showing the default skybox
Actual result: The player stops rendering only showing a black screen
Reproducible with: 2021.1.0b9, 2021.2.0a5, 2021.2.0a7
Not reproducible with: 2018.4.32f1, 2019.4.21f1, 2020.2.6f1, 2021.2.0a4
Notes:Graphics
1. Reproducible on Ubuntu 18.04 and CentOS 7
2. Not reproducible on Windows 10
3. Could also be reproduced after switching to 1920x1080 resolution on a 4K monitor
Comments (2)
-
Armithaig
Oct 23, 2021 00:52
Confirming still occurring in 2020.3.19f1.
Additionally you need not change from windowed to fullscreen, it is enough to go from a non-native resolution to a native one without altering the FullScreenMode.
-
VoodooDetective
Sep 01, 2021 17:05
This is happening 2020.3.17f1
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a10
Resolution Note (fix version 2020.3):
Fixed in 2020.3.22f1