Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.5.0a5
Issue ID
UUM-132704
Regression
No
VFX Graph Template Name is empty and not auto-populated when enabling "Use as Template" on a VFX asset
Steps to reproduce:
- Create a new Unity project using a High Definition 3D Template
- Go to Assets > Create > Visual Effects > Visual Effects Graph
- Select and create any VFX Graph
- Select the created graph in the Project window
- In the Inspector, enable the "Use as Template" property
- Observe the "Name" property
Actual results: The property is empty
Expected results: The property auto-populates with the VFX Asset name
Reproducible with versions: 6000.5.0a5
Not reproducible with versions: 6000.0.66f1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a4
Tested on (OS): macOS 26.2 (M1)
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
- 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”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
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.