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
- Unity Editor process remains running after closing Editor
- OnApplicationPause pauseStatus is incorrect after losing focus on macOS
- [Mono Upgrade]FileSystemWatcher FileSystemWatcherArgs.Name variable returning the full path instead of the relative file name
- Animator Blend Tree weight defaults to 0 for a frame when AnimationClipPlayable is created with script in Play Mode
- Overridden method is called when calling the base class method using a derived class delegate
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a7