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
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
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.