Search Issue Tracker
Fixed
Fixed in 6000.5.0a9, 6000.6.0a1
Won't Fix in 6000.3.X, 6000.4.X
Votes
0
Found in
6000.3.0b8
6000.4.0a3
6000.5.0a7
6000.6.0a1
Issue ID
UUM-123212
Regression
No
HierarchyNode not found errors are logged when Selecting Items in Hierarchy v2 while Scene is loading
Steps to reproduce:
- Open the attached Project
- Enable Hierarchy v2 (Preferences > General > Use New Hierarchy Window)
- Enter Scene "MainGameScene"
- Enter Play Mode and immediately start clicking in the Hierarchy before the Scene fully loads
- Exit Play Mode and immediately start selecting items in the Hierarchy
- Observe the Console
Actual results: Errors "InvalidOperationException: HierarchyNode(2:1) not found
Unity.Hierarchy.Hierarchy.GetNodeTypeHandlerFromNode (Unity.Hierarchy.HierarchyNode& node) (at <b2914ef2e9724533bd7b796b18734a85>:0)
Unity.Hierarchy.Hierarchy.GetNodeTypeHandlerBase (Unity.Hierarchy.HierarchyNode& node) (at <b2914ef2e9724533bd7b796b18734a85>:0)" are logged
Expected results: No Errors are logged
Reproducible with versions: 6000.3.0b8, 6000.4.0a3
Can’t test with versions: 6000.0.60f1, 6000.2.10f1 (No Hierarchy v2)
Tested on (OS): Windows 11
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.5.0a9):
Fixed in 6000.5.0a9
Resolution Note (6000.4.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. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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 (6000.3.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. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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.