Search Issue Tracker
Fix In Review for 6000.4.1f1
Fix In Review for 6000.5.0b2, 6000.6.X, 6000.6.0a2
Under Consideration for 6000.4.X
Votes
0
Found in
6000.4.1f1
6000.5.0a9
6000.6.0a2
Issue ID
UUM-137711
Regression
Yes
A "NullReferenceException" error is thrown when the left mouse button is pressed in the new Hierarchy while a GameObject is selected
How to reproduce:
1. Create a new project using the “Universal 3D” template
2. In the menu bar, select “Edit → Preferences → General → New Hierarchy” and ensure that the “Use new Hierarchy window” option is enabled
3. In the new Hierarchy window, select a GameObject
4. While the GameObject is selected, hold the left mouse button down for a second on an open space in the new Hierarchy window
5. Observe the Console
Actual result: “NullReferenceException: Object reference not set to an instance of an object” error is thrown in the Console
Expected result: No errors are thrown in the Console
Reproducible with: 6000.4.0a2 (417aa67423b3), 6000.4.1f1
Not reproducible with: 6000.3.12f1, 6000.4.0a1, 6000.5.0b1, 6000.6.0a1
Could not test with: 6000.0.71f1 (New Hierarchy window is not available)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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 6000.4.1f1):
Fixed in 6000.4.1f1
Resolution Note (fix version 6000.6.0a2):
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.6):
Fixed in 6000.4.1f1
Resolution Note (fix version 6000.5.0b2):
Fixed in 6000.5.0b2