Search Issue Tracker
By Design
By Design in 2023.2.X
Votes
1
Found in
2022.2.11f1
2023.1.0b8
2023.2.0a7
Issue ID
UUM-31091
Regression
No
Search filter doesn't show GameObjects in the Hierarchy when specifying which Property it contains
How to reproduce:
1. Open the attached project “Search”
2. Press Ctrl+K to open the Search in a standalone tab
3. Look for a GameObject containing a Property “Mesh” with the mesh “Cylinder” assigned to it
4. Observe the Search results
Expected result: The Search shows the two GameObjects, one in the Hierarchy and one in the Project
Actual result: The Search shows the GameObject only in the Project
Reproducible with: 2022.2.11f1, 2023.1.0b8, 2023.2.0a7
Couldn’t test with: 2020.3.45f1 (The extended Search doesn’t exist), 2021.3.20f1 (The Search is different from the newer versions)
Reproducible on: Windows 11 Pro
Note: Also reproducible with the other Components
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:
For the time being there are some variation between queries on asset and scene object.
The way the query is written looks for the mesh indexed property of prefab and yields a prefab asset result.
t:MeshFilter mesh="GlobalObjectId_V1-4-0000000000000000e000000000000000-10206-0"
The way to write this query for a scene object would be:
h: t:MeshFilter #m_Mesh="GlobalObjectId_V1-4-0000000000000000e000000000000000-10206-0"
We might work on a way to unify these search. But for the time being this is not a bug but more of a feature.
Resolution Note (2023.2.X):
For the time being there are some variation between queries on asset and scene object.
The way the query is written looks for the mesh indexed property of prefab and yields a prefab asset result.
t:MeshFilter mesh="GlobalObjectId_V1-4-0000000000000000e000000000000000-10206-0"
The way to write this query for a scene object would be:
h: t:MeshFilter #m_Mesh="GlobalObjectId_V1-4-0000000000000000e000000000000000-10206-0"
We might work on a way to unify these search. But for the time being this is not a bug but more of a feature.