Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.44f1
2022.3.48f1
6000.0.21f1
Issue ID
UUM-82978
Regression
No
Adding and editing trees in Terrain doesn't add to Undo History
*Steps to reproduce:*
# Open a Unity project
# Download and Import this asset to your project: [Free Trees | 3D Trees | Unity Asset Store|https://assetstore.unity.com/packages/3d/vegetation/trees/free-trees-103208]
# Open the Undo History via Ctrl + U or Edit > Undo History
# Add a Terrain to your scene via GameObject > 3D Object > Terrain
# Select the new Terrain GameObject
# In the Inspector, under the Terrain component, navigate to the 'Paint Trees' tab
# Click on Edit Trees > Add Tree
# Select one of the imported tree assets next to the Tree Prefab option
# Click Add
# Observe the Undo History
# With the tree selected, click Edit Trees > Edit Tree
# Next to Tree Prefab, select a different tree asset
# Click Apply
# Observe the Undo History
# With the tree selected, click Edit Trees > Remove Tree
# Observe the Undo History
*Actual results:* Removing a tree adds to the Undo History as expected, however Adding and Editing a tree do not
*Expected results:* Adding, Editing, and Removing a tree all add to the Undo History
*Reproducible with versions:* 6000.0.21f1, 2022.3.48f1, 2021.3.44f1
*Not reproducible with versions:* -
*Can’t test with versions:* 7000.0.0a3 (terrain system no longer available)
*Tested on (OS):* Ubuntu 24.04, Windows 11
*Notes:*
* Depending on the order that you Add/Remove/Undo trees, this issue can have some extra weird behaviour. For example, if you
1. add a tree to the Trees list
2. remove that tree
3. add that same tree again
4. undo the removal of that tree
5. redo the removal of that tree
then the tree will be gone, even though the previous step had the tree still there. This is because of adding trees not being added to the Undo History.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues.
We acknowledge that the current Terrain system has a number of limitations, so we are currently investing in a large amount of discovery work to determine exactly what is needed most and how we can bring it to you at the quality level you have come to expect and address the most pervasive pain points in the most effective and efficient manner. However, we know each case is different, so please do continue to log any issues you find, and provide general feedback on our roadmap page to help us prioritize.
Forum to discuss feature requests: https://forum.unity.com/threads/world-building-public-roadmap-and-feature-requests.1437163/
Roadmap: https://unity.com/roadmap/unity-platform/3d-world-building