Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.3.0a5
6000.4.0a1
Issue ID
UUM-114264
Regression
No
No default category name in the VFX template window for the templates without configured Category name
How to reproduce:
1. Create a new project and install the Visual Effects package
2. Create any VFX Graph and select it
3. In the Inspector, under the "Template" section, check the "Use as Template"
4. Enter anything into the "Name" field and leave the "Category" empty
5. In the Project window, open the VFX template window
6. Scroll to the bottom, and observe the category header of a custom template
Expected result: There is a placeholder name and the category header is not empty
Actual results: The category header is empty
Reproducible with: 6000.3.0a5
Can't test with: 6000.0.55f1, 6000.1.15f1, 6000.2.0f1 (no such functionality)
Reproducible on: macOS Sequoia 15.5 (M1)
Not reproducible on: No other environment tested
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 warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
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.