Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
22
Found in
5.5.0a1
2019.4
2020.3
2021.2
2022.1
2022.2
Issue ID
805160
Regression
No
[NavMeshSurface] Trees placed on Terrain are not taken into account when baking NavMesh
How to reproduce:
1. Open the attached project (TreeTest.zip)
2. Open scene Scenes/SampleScene
3. In the Hierarchy window, double-click on the GameObject "TreeLocation" to observe the Trees in the Scene view
4. In the Hierarchy window, select "NavMesh Surface"
5. In the Inspector window, under the NavMeshSurface component, select Bake
6. Observe the NavMesh in the Scene view
Expected result: the Terrain Trees are taken into account in the NavMesh
Actual result: the Terrain Trees are not taken into account in the NavMesh
Reproducible with: 2019.4.36f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a5
Comments (8)
-
SexyNoodleMan
Jul 24, 2025 22:11
Please fix the issue. I know making two separate Unity features (Terrains and NavMesh) work together is difficult, but I believe it is a very common scenario in which a developer will want to make a large open-world terrain navigable by the AI. To have Terrain Trees not included correctly in the bake for NavMesh Surfaces is a glaring oversight in my opinion.
-
Crzed
May 15, 2025 18:59
This would be funny if it wasn't so egregious.
-
DatmosPro
Sep 09, 2024 05:40
Is this bug real ? i can not understand how we can do big "nature maps" with thousands of trees, rocks,... were its imposible to put every single tree or rock manually.
How are we supposed to do this?
I'm freaking out that this bug exists and that it's been around for so long!!
-
crdgre
Apr 01, 2024 14:20
I do not understand why it's not fixed yet.
-
hublard
Feb 05, 2024 15:38
lol this is a joke, that that is still a bug? it force u to use the new navmesh surface but u cant bake terrain tree navmesh? wtf unity fix it. using unity 2022
-
Maelstrom_Ben
Jan 27, 2024 02:08
I would like to +1 getting this prioritized. It's crazy that the new version of navmeshes has a regression as big as this.
-
leondino0309
Aug 22, 2023 11:39
Also leaving this here for everyone with this issue (which are gonna be a lot of people now that it is forced with the newer versions of Unity).
This guy made a really good fix:
https://github.com/Malikir324/Unity-NavMesh-adding-Obstacles-To-Terrain-Trees -
leondino0309
Aug 22, 2023 11:12
Please fix this issue.
From Unity 2023 forward, the new AI naviagtion systems forces you to use NavMesh Surfaces, instead of baking it through the navigation window. (Unless you use the obsolute version, which shouldn't be neccesary.)
This means that in the newest versions of Unity it has become IMPOSSIBLE to bake terrain trees, without using outdated feautures with a warning that they will get deleted...
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
- Baked Lightmap ”View” button text is aligned incorrectly
- Lightmap Asset icon changes colours after Baked Lightmap Viewer window is opened
- VideoClipImporter preset not applied when applying Preset Selector on already imported video clips
- Frame Debugger gets disabled when any Editor window is maximised and minimised
- TextMeshPro InputField view is not updated when OnEndEdit is triggered
Resolution Note:
This feature request has been added in NavMeshComponent backlog