Search Issue Tracker
By Design
By Design in 6000.6.X
Votes
0
Found in
6000.5.0a8
6000.6.0a1
Issue ID
UUM-136426
Regression
No
VFX Template search partial name matching does not work when Template name differs from the Asset name
Steps to reproduce:
- Open the attached project
- In the Project window, observe the existing "Test" VFX asset with a Template name of "Graph"
- Right-click in the project window and select the option to create a new VFX asset
- In the Template window, enter "raph" into the search field that should partially match the template name
- Observe the Search results
Actual results: No template is found by the search query
Expected results: Template from Step 2 is found by the search query
Reproducible with versions: 6000.5.0a8
Can’t test with versions: 6000.0.70f1, 6000.3.10f1, 6000.4.0b12, 6000.5.0a4 (No search field in the Templates window)
Tested on (OS): Windows 11, macOS 26.3.1
Notes:
- Partial name matching works when entering the asset name, in this case, "est"
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:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.