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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a7