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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
This is a duplicate of issue #556409