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
- 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
This is a duplicate of issue #556409