Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.9.7
Issue ID
UVSB-2602
Regression
No
Type Description Box in Backboard Persists When Hovering Over Types Without Descriptions
Steps to reproduce:
- Create a new Unity project
- Open the Visual Scripting Graph via Window > Visual Scripting > Visual Scripting Graph
- Create and open a State Graph asset
- In the Backboard section, add a new variable
- Hover over a type without a description (e.g., string, float, bool) in the type selection dropdown
- Observe that no description is shown
- Now hover over a type with a description (e.g., Vector3)
- Observe the description box appears with contents
- Finally, hover again over a type without a description (e.g., bool)
- Observe that the description box
\\
Actual results: The type description box remains visible
Expected results: The type description box should disappear when hovering over types that do not have descriptions
\\
Reproducible with versions: 1.9.4 (2022.3.62f1) , 1.9.8 (2022.3.62f1, 6000.0.52f1, 6000.1.12f1, 6000.2.0b9, 6000.3.0a2)
\\
Tested on (OS): Ubuntu 22.04, macOS 15.6
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
This issue has been closed because we know with certainty that we will not be able to address it in the coming year.
We understand that it is personally important enough for you to have filed a bug report, and we are sorry that we will not be able to address it in a timely fashion, but we have to address bugs in order of impact, and unfortunately this one is minor compared to the other issues listed in our backlog.