Search Issue Tracker
Fixed in 2020.3.X
Votes
2
Found in
2020.3.31f1
2020.3.32f1
Issue ID
1411755
Regression
Yes
Inspector gets garbled after assigning 0 to Materials list in Mesh Renderer and undoing it
Steps to reproduce:
1. Create a new project or open an existing one
2. Create a new Cube GameObject in Hierarchy
3. Select the Cube
4. Click on the Materials dropdown count in the Mesh Renderer component
5. Enter 0 and click Enter key
6. Undo it with Cmd+Z or Ctrl+Z
Expected results: Inspector component don't get garbled
Actual results: Inspector components get garbled (see attached pic in edits)
Reproducible with: 2020.3.31f1, 2020.3.32f1
Not reproducible with: 2019.4.37f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b12, 2022.2.0a8 (likely fixed with the dropdown change)
Notes:
- Alternate steps to reproduce the issue would be to add Mesh Renderer component and then Mesh Filter component to an empty GameObject
- Issue goes away after a proper repaint, for example picking any other GameObject and then picking the affected one
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2020.3):
Fixed in 2020.3.34f1