Search Issue Tracker
Duplicate
Votes
0
Found in
4.3.4f1
Issue ID
597963
Regression
No
Changing Player Settings doesn't affect consequent builds
Duplicate of case 556409
Steps to repro:
- open attached project and load "ResolutionFail" testscene (empty scene with GUIText info)
- open build settings
- open player settings
- make sure "Display Resolution Dialog" is disabled
- enable "Default is Full Screen" and "Default is Native Resolution"
- create build
- execute build
- notice displayed resolution and quality settings
- in player settings, change any of the fields Full Screen, Native Resolution, Default Screen Size, and/or in the Quality Settings choose a different setting.
- create build
- execute build
- notice behaviour and displayed resolution and quality settings are FROM PREVIOUS BUILD, not this one
- the initial settings can only be overridden if you execute a build with resolution dialog enabled
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
This is a duplicate of issue #556409