Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.53f1
Issue ID
UUM-110120
Regression
No
Standalone Build Resolution and Screen Mode settings do not match Player Settings when making new Standalone Builds
How to reproduce:
1. Open the project “IN-103109_BuildProfile”
2. Open the Player Settings, File → Build Profiles → Player Settings…
3. Set Screen Mode and Resolution, Player → Resolution and presentation → Fullscreen Mode → Set to Windowed
4. Build and Run the project, File → Build Profiles → Build and Run, close the Standalone Build
5. Set the Screen Mode (step 3) to Exclusive Fullscreen and toggle the “Default is Native Resolution” option to OFF
6. Build and Run the Project (step 4), close and repeat to Build and Run one more time, close the Standalone Build
7. Toggle the option “Default is Native Resolution” to ON (step 5) and Build and Run (step 6) one more time
8. Observe the Standalone Build
Expected result: The Standalone Build is of the same resolution as is the screen it is open on and it is Fullscreen
Actual result: The Standalone Build is of different resolution than the screen it is open and sometimes not Fullscreen
Reproducible with: 2021.3.53f1, 2022.1.0a1, 2022.3.62f1, 6000.0.48f1
Not reproducible with: 6000.0.51f1, 6000.1.8f1, 6000.2.0b6
Fixed in: 2022.3.63f1, 6000.0.49f1
Notes:
- If at any point the Standalone Build does not match the Player Build Profile settings, you can stop with the steps, the issue did reproduce. Sometimes the Exclusive Fullscreen mode will instead be Window, or Fullscreen Window
- When using multiple screens, moving the Windowed Mode to the main screen seems to help reset the position for the next Build
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:
Thank you for reporting this issue. Unfortunately, the Unity version you are using (2021 LTS) is no longer supported, and we are unable to address bugs related to this version. Please upgrade to a newer (2022 LTS+), supported version of Unity to ensure compatibility and access to the latest features and fixes.