Search Issue Tracker
Fixed
Fixed in 6000.5.0a5
Won't Fix in 6000.4.X
Votes
0
Found in
6000.4.0a2
6000.5.0a2
Issue ID
UUM-126767
Regression
Yes
Template fields' information is not preserved or is reverted to previous value upon asset duplication
Steps to reproduce:
- Create a new project and install the Visual Effect Graph package
- Create a new VFX
- Select the VFX in the Project Browser
- In the Inspector, tick the Use as Template box and set the name to A
- Duplicate the VFX
- Observe that the Use as Template flag is now set to {}false{}, and the VFX name has reverted to its previous value (likely empty)
Actual results:
- The Use as Template flag is set to false
- The name field is empty
Expected results:
- The Use as Template flag should remain set to true
- The name field should either:
** Receive a suffix upon duplication if a unique name is required, or
* Retain the asset’s original name.
Reproducible with versions:* 6000.4.0a2, 6000.5.0a2
Not reproducible with versions: 6000.4.0a1
Tested on (OS): macOS
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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Resolution Note (6000.4.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.