Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
12.1.0
Issue ID
1375181
Regression
Yes
Exceptions/errors are thrown while undo/redo-ing changes made to VFX graph blackboard category
How to reproduce:
1. Open attached project
2. Add Vector 2 to blackboard
3. Add Vector 3 to blackboard
4. Hold Undo/Redo these changes
5. Observe console
Expected result: change are undo/redo-ed and not errors appear in console
Errors:
Exception while setting value for slot o of type UnityEditor.VFX.VFXSlot: UnityEngine.MissingReferenceException: The object of type 'VFXSlot' has been destroyed but you are still trying to access it.
Your script should either check if it is null or you should not destroy the object.
at (wrapper managed-to-native) UnityEngine.Object.get_hideFlags(UnityEngine.Object)
at UnityEditor.VFX.VFXGraph.OnInvalidate (UnityEditor.VFX.VFXModel model, UnityEditor.VFX.VFXModel+InvalidationCause cause) [0x00082] in /Users/justasz/Documents/test/New Unity Project (11)hd/Library/PackageCache/com.unity.visualeffectgraph@13.1.0/Editor/Models/VFXGraph.cs:654
at UnityEditor.VFX.VFXModel.Invalidate (UnityEditor.VFX.VFXModel model, UnityEditor.VFX.VFXModel+InvalidationCause cause) [0x00000] in /Users/justasz/Documents/test/New Unity Project (11)hd/Library/PackageCache/com.unity.visualeffectgraph@13.1.0/Editor/Models/VFXModel.cs:403
Also error thrown 2022.1:
Assertion failed on expression: '!AssetDatabase::IsAssetDatabaseInitialized() || !AssetDatabase::IsAssetImporting()'
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()
Reproduced with: 2022.1.0a13 (13.1.0), 2021.2.0b17 (12.1.0)
Does not reproduce with: 2022.1.0a12 (13.0.0), 2021.2.b15 (12.0.0)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment