Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.0.65f1

6000.3.4f1

6000.4.0b3

6000.5.0a4

Issue ID

UUM-131872

Regression

No

Terrain’s “Add Tree” window does not disable the “Add” button when the Tree Prefab is deleted and missing, allowing a “Missing” Tree to be added

Terrain

-

Steps to reproduce:

  1. Create a new Unity project using the Universal 3D template
  2. Create a new Terrain GameObject (GameObject > 3D Object > Terrain)
  3. Create a new Tree GameObject (GameObject > 3D Object > Tree)
  4. Select the Terrain GameObject in the Hierarchy window
  5. Open the "Paint Trees" tab in the Terrain component
  6. Click the "Edit Trees" button and select "Add Tree" option
  7. Select the created Tree as the Tree Prefab in the "Add Tree" window
  8. Delete the "Assets/Tree.prefab" prefab
  9. Observe the "Add Tree" window
  10. Click the "Add" button in the "Add Tree" window
  11. Observe the Terrain component

Actual results: The "Add" button is not disabled when a Tree with a missing Prefab is selected

Expected results: The "Add" button is disabled or the Tree with a missing Prefab is not added

Reproducible with versions: 6000.0.65f1, 6000.3.4f1, 6000.4.0b3, 6000.5.0a4

Tested on (OS): MacOS Silicon Tahoe 26.1

  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.