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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
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.