Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.5f1
6000.4.0b4
6000.5.0a5
Issue ID
UUM-132454
Regression
No
Inconsistent capitalization and usage of “Template” in the VFX window
Steps to reproduce:
- Create a project
- Install the "Visual Effect Graph" package
- Create a new Visual Effect Graph (Project window > Create > Visual Effects > Visual Effect Graph > select any template > click "Create")
- Select the newly created VFX Asset
- Press the “+” icon, which is displayed in the VFX Graph window
- Observe the displayed items
Actual results: “Template” word is not capitalised in both listed items
Expected results: The word “Template” should be capitalized as it is in other sections
Reproducible with versions: 17.0.4(6000.0.65f1), 17.3.0(6000.3.5f1), 17.4.0(6000.4.0b4), 17.5.0(6000.5.0a5)
Tested on (OS): macOS - Tahoe 26.2
h3.
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
- 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
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.