Search Issue Tracker
Fixed
Fixed in 6000.2.0b7
Votes
0
Found in
6000.2.0b7
Issue ID
UUM-109880
Regression
No
Platform settings count as default Build Settings when creating Build Profiles from Platform Build Settings
How to reproduce:
1. Open any Project
2. Navigate to “Project Settings > Services > Diagnostics” and observe the default Build Setting
3. Navigate to “File > Build Profiles” and change “Diagnostic Data” to the opposite option of the default option
4. Add your platform’s Build Profile
5. Observe the “Diagnostic Data” dropdown
Expected result: Shows either “Enabled or Disabled (Project Default)” directly corresponding what is chosen in Project Settings as the default
Actual result: Shows either “Enabled or Disabled (ProjectDefault)” directly corresponding to what was chosen in your Platform’s Build Profile Settings before creating the Build Profile
Reproducible with versions: 6000.2.0b7
Tested on (OS): macOS Sequoia 15.4 (M4)
Note: Platform Build Profile options for the default (enabled/disabled) Diagnostics Data dropdown option does not update visually if the default option has been switched in Project Settings and Platform settings were not set to default settings
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
Add comment