Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
0
Found in
2020.3.45f1
Issue ID
UUM-26576
Regression
No
Script compilation is not triggered when modifying Scripting Define Symbols outside the Editor
Reproduction steps:
1. Open the “TestScriptingDefine“ project
2. Open “Project Settings” and make sure “Scripting Define Symbols” contains “MY_FEATURE_ENABLED”
3. Close the project
4. Open “ProjectSettings/ProjectSettings.asset” and change “scriptingDefineSymbols:” from “1: MY_FEATURE_ENABLED” to “1:”
5. Open the project
6. Click the “Tools/Run Test” menu item
7. Observe the Console
Expected result: “Feature enabled: False” is logged
Actual result: “Feature enabled: True” is logged
Reproduced in: 2020.3.45f1, 2021.1.0a5
Not reproduced in: 2021.1.0a6, 2021.3.18f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1
Reproduced using: macOS 13.0.1 (Intel), Windows 10 (by the reporter)
Note: “Feature enabled: False” is logged when clicking “Tools/Recompile Scripts” and then “Tools/Run Test“
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
Resolution Note:
Unfortunately, this wont be fixed as only 2020.3 is impacted and there is a workaround: please refrain to edit the project settings asset file manually, or make sure to manual trigger script compilation if you do so.
Resolution Note (2020.3.X):
Unfortunately, this wont be fixed as only 2020.3 is impacted and there is a workaround: please refrain to edit the project settings asset file manually, or make sure to manual trigger script compilation if you do so.