Search Issue Tracker
Fixed in 2021.1.X
Votes
1
Found in
2018.4
2019.4
2020.1
2020.1.0f1
2020.2
Issue ID
1266308
Regression
No
Standalone player resolution is not correct when build is ran in batchmode with custom screen width and height arguments
How to reproduce:
1. Open attached project "BatchModeRes.zip"
2. Build the project
3. Open Command prompt (cmd)
4. with 'cd' navigate to the build location
5. In cmd, call "BatchModeRes.exe -batchmode -screen-fullscreen 0 -screen-width 1280 -screen-height 760"
6. Open "C:\Users\*username*\AppData\LocalLow\DefaultCompany\BatchModeRes\Player.log"
Expected result: last line is "Screen size: 1280x760"
Actual result: last line is "Screen size: 1424x720"
Reproducible with: 2018.4.26f1, 2019.4.6f1, 2020.1.0f1, 2020.2.0a18
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
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a7