Search Issue Tracker

Won't Fix

Won't Fix in 6000.6.X

Votes

0

Found in

6000.3.10f1

6000.4.0b10

6000.5.0a7

6000.6.0a1

Issue ID

UUM-135411

Regression

No

“+” button remains active in the "Active Targets" section when no additional items are available for selection

ShaderGraph

-

Steps to reproduce:

  1. Create a new Unity project
  2. Open the "Create new Shader Graph Asset" window (Project window > right click > Create > Shader Graph > From Template...)
  3. Select any template and click the "Create" button
  4. Select a newly created shader graph item in the "Project" window
  5. In the shader graph window, find "Graph Inspector"
  6. Find the "Active Targets" section in the "Graph Inspector" section
  7. Click "" and select "Custom Render Texture"
  8. Click "" and select "Built-In"
  9. Click "" one more time and observe the result

Actual results: The “” button is displayed as active and clickable even when there are no additional items available to select

Expected results: The “+” button is disabled when no additional items are available for selection, preventing further interaction

Reproducible with versions: 6000.3.10f1, 6000.4.0b10, 6000.5.0a7

Tested on (OS):  macOS - Tahoe 26.2

  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.6.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.