Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.2.X, 2022.1.X
Votes
0
Found in
2020.3.19f1
2021.2.0b8
2021.2.0f1
2022.1.0a3
Issue ID
1379541
Regression
Yes
[Particles] Inspector breaks and errors are thrown when the Material field is deleted from the Particle System
How to reproduce:
1. Open the user's attached "ParticleMaterials" project
2. Open the "SampleScene" Scene
3. Select the "Particle System" GameObject
4. Enable the "Trails" module in the Inspector
5. Select "Renderer -> Material" in the Inspector
6. Click Ctrl + Delete (Cmd + Delete on MacOS) on keyboard device
7. Repeat the 5th and 6th steps
8. Observe the Editor
Expected result: The Material field doesn't get deleted after the 7th step
Actual result: The Inspector breaks and "InvalidOperationException: The operation is not possible when moved past all properties (Next returned false)" error is thrown
Reproducible with: 2020.3.19f1, 2020.3.23f1, 2021.2.0b9, 2021.2.3f1, 2022.1.0a4, 2022.1.0a15
Not reproducible with: 2019.4.32f1, 2020.3.0f1, 2020.3.18f1, 2021.2.0a1, 2021.2.0b8, 2022.1.0a1, 2022.1.0a3
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
- 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
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a1
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b5
Resolution Note (fix version 2021.2):
Fixed in 2021.2.8f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.27f1