Search Issue Tracker
Fixed
Fixed in 6000.0.59f1, 6000.2.6f1, 6000.3.0a4
Votes
0
Found in
6000.0.51f1
6000.1.7f1
6000.2.0b6
Issue ID
UUM-109475
Regression
Yes
Errors are thrown when a GameObject with Trail Renderer is selected in the Hierarchy, moved and destroyed
How to reproduce:
1. Open the attached “Trail errors” project
2. Open the “SampleScene”
3. Enter Play mode
4. Switch to the Scene view
5. In the Hierarchy, select the “GameObject”
6. In the Inspector, Transform component, change any of the “Position” properties to “2”
7. Observe the Console
Expected result: No errors are thrown in the Console
Actual result: Multiple errors are thrown in the Console
Reproducible with: 2022.2.0a6, 2022.3.63f1, 6000.0.51f1, 6000.1.7f1, 6000.2.0b6
Not reproducible with: 2022.2.0a5
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Errors thrown: “MissingReferenceException” and “GUI Error”
- Also reproducible by moving the GameObject via move tool or a script
- Reproduces when the GameObject is destroyed via “Autodestruct” setting or “Destroy” method
- Does not reproduce in Game view or when the GameObject is not selected
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
Add comment