Search Issue Tracker
Won't Fix
Votes
0
Found in
1.0.15
Issue ID
UUM-135947
Regression
No
“Send” and “Wait” informational boxes are not fully visible and get pushed out of the view when creating an Event in the Blackboard with a long description
Steps to reproduce:
- Create a new project using the Universal 3D template
- Install the Behavior package (com.unity.behavior)
- Create a new Blackboard asset (Assets > Create > Behavior > Blackboard)
- Open the Blackboard
- Click the "+" button and select Event
- Click the "Create new event channel type..."
- Enter any name
- Click the "Next" button
- Enter something long into the description field
- Observe the "Send" and "Wait" informational boxes in the Blackboard window
Actual results: “Send” and “Wait” informational boxes are not fully visible and get pushed out of the view
Expected results: The name is truncated so that the informational boxes are fully visible at all times
Reproducible with versions: 1.0.15 (6000.0.69f1, 6000.3.10f1, 6000.4.0b11, 6000.5.0a8)
Tested on (OS): MacOS Silicon Tahoe 26.2, Ubuntu 24.04
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
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:
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.