Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4.6f1
2020.2
Issue ID
1273706
Regression
No
[ScriptableObject] Script loses reference to ScriptableObject after compilation error is encountered and then fixed
Reproduction steps:
1. Open attached project "Scriptable.zip" and scene "ScriptableObjectIssue"
2. In Project window, open "MyBuggyScript.cs"
3. In "MyBuggyScript.cs", uncomment line 7
4. Restart Unity Editor
5. In "MyBuggyScript.cs", comment out line 7
6. In Hierarchy window, select "My SO Container" GameObject
7. Observe "My Scriptable Object" field
Expected result: There is a reference to the scriptable object
Actual result: There is no reference to a scriptable object
Reproducible with: 2018.4.27f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0b1
-
ChrisIceBox
Sep 01, 2020 08:01
The object is not unsaved - the data is lost. Please re-open this issue. Data that was part of the scene file being is lost.
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:
The behavior for unsaved assets is undeterministic in this scenario, in order to address this you should save the asset in the asset database at creation time: AssetDatabase.CreateAsset(myScriptableObject, "Assets/MyScriptableObject");