Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.32f1
2022.3.14f1
2023.2.2f1
2023.3.0a16
6000.0.0b11
Issue ID
UUM-57123
Regression
No
ScriptableSingleton value change isn't detected in Unity when it's modified via text editor
How to reproduce:
1. Open the attached “TempTest.zip“ project
2. Open the “ExampleScriptableSingleton.dat“ file with a text editor (TempTest/ProjectSettings)
3. Change the “currentNumber“ value from 0 to 1
4. Save made changes
5. In the Unity Editor, log the “Current Number“ (BugReport > Log & Save Current Number)
Expected result: Logged “Current Number” is 1
Actual result: Logged “Current Number” is 0
Reproducible with: 2021.3.32f1, 2022.3.14f1, 2023.2.2f1, 2023.3.0a16
Reproducible on: macOS 14.0 Sonoma (Intel)
Not reproducible on: No other environment tested
Note: ScriptableSingleton changes are detected if the Editor is restarted or if everything is reimported (by right-clicking in the Assets folder and selecting “Reimport All“)
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
- "GetPreferedValue" returns max value when using auto-sizing
- UI Builder doesn't update the style sheet when using "Extract inline style" right-click option
- “Assertion failed on expression” errors thrown when undoing Nodes creation with keyboard shortcut
- Crash on various stack traces when using Texture2D.CreateExternalTexture() while rendering
- Clicking on section text in Node Library > Context folder throws NullReferenceException errors
Resolution Note:
ScriptableSingleton in this case is functioning as designed