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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.