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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
ScriptableSingleton in this case is functioning as designed