Search Issue Tracker
Fixed
Fixed in 6000.0.3f1
Votes
0
Found in
6000.0.0b16
Issue ID
UUM-70176
Regression
No
[Player Settings] [Common] [Scripting Compilation] - Update scripting defines when player settings is removed
Steps to reproduce:
1. Open Files > Build Profiles
2. Create a build profile, make it active (press Switch Profile)
3. Add player settings to it (press Customize Player Settings)
4. Add a symbol to the Scripting Define Symbols under Other Settings > Scripting Compilation and press Apply
5. Notice how a warning will show up above the scripting define section under Build Data > Scripting Defines
6. Remove the player settings (kebab menu > Remove Overrides).
Actual results: Notice how the warning above the scripting defines are still there because the added scripting defines didn't get applied.
Expected results: When removing the player settings, the warning should disappear
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