Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.5.0a5
Issue ID
UUM-132481
Regression
No
Instead of "Category" user gets "vfxgraph.category" string during search criteria change in the "Create new VFX Asset" window
Steps to reproduce:
- Create a project
- Install the "Visual Effect Graph" package
- Open the "Create new VFX Asset" window (Project window > Create > Visual Effects > Visual Effect Graph)
- Go to the “Search” field and click “+”
- Select the “Category” item from the list
- Select “Built-In”
- Click the drop-down next “Built-In”
- Observe the result
Actual results: User gets "vfxgraph.category" code string
Expected results: User should get "Category"
Reproducible with versions: 6000.5.0a5
Can’t test with versions: 6000.4.0b4 as search functionality is available only in U6.5
Tested on (OS): macOS - Tahoe 26.2
Notes: The same issue exists in the "Create new Shader Graph" Asset 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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
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.5.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.