Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2022.3.4f1
2023.1.2f1
2023.2.0a21
2023.3.0a3
Issue ID
UUM-40972
Regression
Yes
Assets are not found when searching by path in the Search window
How to reproduce:
1. Open the user’s attached “bug-asset-search.zip” project
2. In the Search window, insert “p: Assets/Scenes”
3. Observe the results
Expected result: “SampleScene” is found
Actual result: 0 results
Reproducible with: 2022.2.12f1, 2022.2.21f1, 2022.3.4f1, 2023.1.2f1, 2023.2.0a21
Not reproducible with: 2021.3.27f1, 2022.2.11f1
Reproduced on: macOS 13.2.1 (Intel)
Notes:
Searching by filename works
"p: Asset" will show the result, but "p: Assets" will not
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:
In order to harminize with how PRoject browser searches, we chose that free searm term would be match against asset names and not full path (this limit noise in filter results).
the dir filter can be used if you would like to filter according to folders.
Resolution Note (2023.3.X):
In order to harminize with how PRoject browser searches, we chose that free searm term would be match against asset names and not full path (this limit noise in filter results).
the dir filter can be used if you would like to filter according to folders.