Search Issue Tracker
Fixed in 2021.3.9f1
Fixed in 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X, 2023.1.0a5
Votes
0
Found in
2021.3.5f1
2022.1.7f1
2022.2.0a18
2023.1.0a2
Issue ID
UUM-7552
Regression
Yes
The player does not refresh window display properties when opening the Player on another display
Reproduction steps:
- Create an empty project
- Build the project
- Set Windows Project setting to “PC screen only” (Win + P shortcut)
- Run the Player
- Observe the Player’s resolution
- Exit the Player and set Windows Project setting to “Second screen only” (Win + P shortcut)
- Run the Player again
- Observe the Player’s resolution
Expected result: no black bars should be seen
Actual result: black bars are present
Reproducible with: 2021.2.0a16, 2021.2.19f1, 2021.3.5f1, 2022.1.7f1, 2022.2.0a18, 2023.1.0a2
Not reproducible with: 2019.4.39f1, 2020.3.36f1, 2021.2.0a15
Reproducible on: Windows 10 (21H2)
Notes:
- One of the two monitors has to be set as a vertical display
- Deleting the HKEY_CURRENT_USER\\SOFTWARE<company_name><product_name> registry values before opening the Player on another display fixes the issue
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2023.1):
Fixed in 2023.1.0a5
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0b5
Resolution Note (fix version 2022.1):
Fixed in 2022.1.13f1
Resolution Note (fix version 2021.3):
Fixed in 2021.3.9f1