Search Issue Tracker
Fixed in 2021.3.9f1
Fixed in 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X, 2023.1.0a3
Votes
0
Found in
2021.3.2f1
2022.1.0f1
2022.2.0a12
2023.1.0a1
Issue ID
UUM-4178
Regression
Yes
[Backport] Build is launched in the wrong Display when Main Display is changed
Reproduction steps:
1. Open the attached project "Display test"
2. Check your Display settings
3. Build and Run project
4. Notice that the Build was launched on your Main Display
5. Change your Main Display to another Display
6. Run the build
Expected result: Build runs on current Main Display after it is changed
Actual result: Build doesn't run on current Main Display after it is changed
Reproducible with: 2021.2.0a16, 2021.2.19f1, 2021.3.2f1, 2022.1.0f1, 2022.2.0a12
Not reproducible with: 2019.4.38f1, 2020.3.34f1, 2021.2.0a15
Notes: If Player Settings in Registry are deleted after changing the Main Display, expected behavior is reached.
This also affects in which Display the Editor is opened.
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
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0b5
Resolution Note (fix version 2022.1):
Verified fixed in 2022.1.13f1
Resolution Note (fix version 2021.3):
Verified fixed in 2021.3.9f1
Rev: ad3870b89536