Search Issue Tracker

Fixed

Fixed in 6000.5.0b7, 6000.6.0a5

Won't Fix in 6000.0.X, 6000.3.X

Votes

0

Found in

6000.0.70f1

6000.3.11f1

6000.4.0b12

6000.5.0a8

6000.6.0a1

Issue ID

UUM-136458

Regression

Yes

VFX Marquee selection does not match the visual indicator

Visual Effects

-

Steps to reproduce:

  1. Open the attached project
  2. Open the Test vfx asset
  3. In the Graph Editor, hold shift to create a selection marquee
  4. Observe the visual indicator that is left by the selection

Actual results: The visual indicator is connected to the bottom of the mouse cursor. This can lead to situations where the indicator crosses the node, but it isn't selected or vice versa

Expected results: The visual indicator is connected to the top of the mouse cursor. Only objects crossed by the visual indicator are selected

Reproducible with versions: 2023.2.0b15, 6000.0.70f1, 6000.3.11f1, 6000.4.0b12, 6000.5.0a8

Not reproducible with versions: 2022.3.74f1, 2023.2.0b14

Tested on (OS): Windows 11, macOS 26.3.1

  1. Resolution Note:

    Fixed in 6000.6.0a5

  2. Resolution Note (fix version 6000.6.0a5):

    Fixed in 6000.6.0a5

  3. Resolution Note (fix version 6000.5.0b7):

    Fixed in 6000.5.0b7

  4. Resolution Note (6000.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.

  5. Resolution Note (6000.0.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