Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.3.0a7
Issue ID
UUM-52278
Regression
No
Blackboard: Attributes or properties list isn't displayed
How to reproduce:
# Open HUB;
# Create 3D(HDRP) project;
# Create a visual effect graph in the "Project" window (Create->Visual Effects-> Visual Effect Graph);
# Select "Minimal System" in "Create New VFX Asset" and click "Create";
# Double-click on the graph to open it;
# Go to the Blackboard and select the Properties or Attributes tab;
# Click "+";
# Enter "AAA" in the search field, presented in the menu;
# Delete all three entered symbols;
# Move the mouse to the "Attribute" menu or "Properties" menu displayed below the search;
# Observe the result.
Actual Result: Sub-menu list isn't displayed. Video added in the attachments section.
Expected Result: Sub-menu always should be displayed.
Reproducible with: 2023.3.0a7, 2023.3.0a9.
Not Reproducible with: 2022.3.10f1, 2023.1.16f1, 2023.2.0b13, 2023.3.0a6. As all, they do not have search functionality.
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
- “GetAllOverlapping failed…” error when clicking a GameObject during a custom picking pass in the Scene view for the second time
- “NullReferenceException” thrown when moving control points on a tree branch in Scene view
- [Linux] Player window unexpectedly resizes to monitor dimensions when calling "Screen.SetResolution" function with hardcoded resolution matching current display's width or height
- Color picker does not show the correct color when selecting color on the moving object
- “Asset X has no meta file, but it's in an immutable folder. The asset will be ignored.” errors are thrown when importing package with files not listed in package.json's "files" property
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.