Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.
Resolution Note (2023.3.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.