Search Issue Tracker
Fixed in 2020.3.37f1
Fixed in 2020.3.X, 2021.3.X, 2021.3.6f1
Votes
0
Found in
2020.3.2f1
2021.3.0f1
Issue ID
UUM-1818
Regression
No
[Backport] [ParticleSystemForce] Errors are thrown on accessing Preset when ParticleSystemForce is deleted
When ParticleSystemForce object is deleted then on accessing its Preset when Editor is in play mode throws errors in the console. Refer attached video and stack trace
Steps to repro:
1. Create a new project.
2. Hierarchy > Effects > Particle System Force Field > Create Preset
3. Hierarchy > Particle System Force Field > Delete
4. Project > Particle System Force Field Preset > Editor > Play Mode.
Actual Result:
Errors spam the console on accessing Preset when ParticleSystemForce is deleted.
Expected Result:
No error should be thrown in the console on accessing Preset when ParticleSystemForce is deleted, Or more user-friendly warning should be thrown
Occurring on:
2021.2.0a7, 2021.2.0a1, 2021.1.0b10, 2021.1.0a1, 2020.2.6f1, 2020.1.17f1, 2019.4.21f1
Environment:
Windows 10 & macOS 10.15
Stack Trace:
SerializedObject target has been destroyed.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
ArgumentNullException: Value cannot be null.
Parameter name: source
UnityEditor.Presets.PresetEditor.DrawInternalInspector () (at /Users/bokken/buildslave/unity/build/Modules/PresetsEditor/PresetEditor.cs:311)
UnityEditor.Presets.PresetEditor.DrawPresetData () (at /Users/bokken/buildslave/unity/build/Modules/PresetsEditor/PresetEditor.cs:119)
UnityEditor.Presets.PresetEditor.OnInspectorGUI () (at /Users/bokken/buildslave/unity/build/Modules/PresetsEditor/PresetEditor.cs:107)
UnityEditor.UIElements.InspectorElement+<>c__DisplayClass59_0.<CreateIMGUIInspectorFromEditor>b__0 () (at /Users/bokken/buildslave/unity/build/External/MirroredPackageSources/com.unity.ui/Editor/Inspector/InspectorElement.cs:617)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&) (at /Users/bokken/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:189
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2021.3):
Fixed in 2021.3.6f1