Search Issue Tracker

Won't Fix

Under Consideration for 2022.3.X, 6000.0.X

Won't Fix in 6000.5.X

Votes

0

Found in

2022.3.58f1

6000.0.38f1

6000.1.0b5

6000.2.0a3

6000.3.0a1

6000.4.0a1

6000.5.0a1

Issue ID

UUM-97272

Regression

No

[Overlays] Visual Effect Model overlays tooltip is left in Scene when unfocusing VFX Node and the overlay dropdown menu is opened

UI Toolkit Framework

-

Steps to reproduce:

  1. Open the attached Project
  2. Open Scene "SampleScene" and VFX Graph "FlyDeathVFX"
  3. Have Scene View opened and in the VFX Graph select node "Multiply (Vector - Local)"
  4. In Scene View have the "Visual Effect Model" Overlay docked to the left edge
  5. Open that Overlays dropdown menu and in the VFX Graph select the "Update Particle" Context
  6. Observe Scene View

Actual results: The "Visual Effect Model" tooltip is left in Scene View when unfocusing a node that has a VFX Property Overlay, if the Block is selected again, the Overlay opens with skewed elements

Expected results: No tooltip or other artifact is left in Scene View when unfocusing nodes

Reproducible with versions: 2022.3.58f1, 6000.0.38f1, 6000.1.0b5, 6000.2.0a3

Tested on (OS): Windows 11

Notes:

  • On 2022.3 instead of the Tooltip name, a black dot is left in Scene View
  1. 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.

  2. Resolution Note (6000.5.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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.