Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2020.3.45f1
2021.3.19f1
2022.2.0a1
Issue ID
UUM-30772
Regression
No
"NullReferenceException" errors in the Console when opening the Particle System Editor
How to reproduce:
1. Open the attached project “ZombieToys-15.zip“
2. Open Scene “construction“ (Assets/Scenes)
3. Select the “SlimeHit“ GameObject
4. Press “Open Editor…“ in the Inspector
Expected result: The Particle System Editor is opened
Actual result: "NullReferenceException" errors in the Console
Reproducible with: 2020.3.45f1, 2021.3.19f1, 2022.2.0a1
Not reproducible with: 2022.2.0a3, 2022.2.8f1, 2023.1.0b5, 2023.2.0a3
Fixed in: 2022.2.0a2
Reproducible on: macOS 13.0.1 (Intel), Windows 10 (by reporter)
Note:
- When pressing the small plus symbol bellow the “Open Editor…“ button and selecting “Show All Modules“ after following the reproduction steps, the Editor can’t be opened and there are no Errors in the Console
- Issue is not reproducible in a new empty project
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
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. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.
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.
Resolution Note (2022.2.X):
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. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.
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.