Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.27f1
2022.3.1f1
2023.1.0b20
2023.2.0a18
Issue ID
UUM-37700
Regression
No
VFX Blackboard: Duplicated items numbers misses brackets
How to reproduce:
# Open HUB;
# Create 3D(HDRP) project;
# Create a visual effect graph in the "Project" window (Create->Visual Effects-> Visual Effect Graph);
# Double-click on it;
# Click the "Blackboard" button and verify, that it becomes visible;
# Click "+" in it and select "Category";
# Select a newly created category, make a right click and select "Duplicate";
# Verify that the category item becomes duplicated and next to it user sees added 1;
# Make duplication one more time and observe the result.
Expected result: Duplicated items should have numbers displayed in brackets.
Actual result: Duplicated items are displayed with numbers but without brackets.
Reproducible with: 12.1.12 (2021.3.27f1), 14.0.8 (2022.3.1f1), 15.0.5 (2023.1.0b20), 16.0.2 (2023.2.0a18).
Additional info: [Use of brackets|https://unityeditordesignsystem.unity.com/components/label#Content-Best-Practices:~:text=Unity%20Style%20Guide%20%2D%3E-,Use%20of%20brackets%20(%23),-When%20displaying%20labels] documentation in "Editor Fundations Internal".
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
Resolution Note:
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.