Search Issue Tracker
Won't Fix
Won't Fix in 6000.4.X
Votes
0
Found in
6000.3.5f1
6000.4.0b5
Issue ID
UUM-132726
Regression
No
[Hierarchy V2] Pinging Target in Hierarchy from Tile Palette dropdown doesn’t highlight or select the Tilemap GameObject in Hierarchy window
Steps to reproduce:
1. Create new Unity project using Universal 2D Template
2. Make sure New Hierarchy window is enabled (In Preferences window > General)
3. Create a new Tile Palette (open the Tile Palette window, go to Window > 2D > Tile Palette)
4. Select the New Palette drop-down menu
5. Select the Create New Palette option to create a new Palette
6. Once created, click on the same drop-down menu
7. Click on the nipple button to ping Target in Hierarchy
8. Observe Hierarchy window
Actual results: “Tilemap” GO is not pinged in Hierarchy window
Expected results: “Tilemap” GO is pinged in Hierarchy window
Reproducible with versions: 6000.3.5f1, 6000.4.0b5, 6000.5.0a4
Not reproducible with versions: 6000.5.0a5
Can’t test with versions: 6000.0.66f1 (New Hierarchy not available)
Tested on (OS): Windows 11, macOS Silicon Tahoe 26.2 (M1)
Notes:
- Not reproducible with old Hierarchy window
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
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. 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.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.