Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.44f1
2022.3.52f1
6000.0.27f1
6000.1.0a4
6000.2.0a1
6000.3.0a1
Issue ID
UUM-87119
Regression
No
ScriptableObject in EditorWindow becomes Null when switching Scene
Reproduction steps:
1. Open the attached “BugRepro” project
2. From the menu navigate to Test > SO Test
3. Notice the "My SO" property is “(My So)” in the SoTest window
4. Reopen the “Assets/Scenes/SampleScene.unity” Scene (double-click on Scene in the Project window)
5. Observe the "My SO" property in the SoTestWindow
Expected result: The "My SO" property should display as “(My SO)”
Actual result: The "My SO" property shows “Missing (Object)”
Reproducible with: 2021.3.44f1, 2022.3.52f1, 6000.0.27f1, 6000.1.0a4
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Comments (1)
-
SolarianZ
Nov 20, 2024 02:24
Supplementary Note: Editing a non-persistent ScriptableObject instance (i.e., a ScriptableObject instance created with CreateInstance but not saved to the AssetDatabase, as mentioned in the report) will cause all loaded Scenes in the Hierarchy to be marked as dirty (indicated by an asterisk symbol).
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
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
- Character animation freezes when toggling animator on/off in a coroutine
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.