Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
1.0.0-exp.4
Issue ID
NAVB-6
Regression
No
NavMeshSurface area is cut off when baked at a specific position on Terrain
Reproduction steps:
1. Open the attached "SurfaceBake.zip" project
2. Open the "Scenes/SampleScene" Scene
3. Select the "Terrain > IncorrectBaking" GameObject in the Hierarchy
4. Ensure that the GameObject's Transform's Z position is at 140
5. Click "Bake" in the Inspector
Expected result: baked area fully covers the area
Actual result: baked area does not fully cover the surface
Reproducible with: 1.0.0-exp.2, 1.0.0-exp.3, 1.0.0-exp.4 (2019.4.30f1, 2020.3.18f1, 2021.1.16f1, 2021.2.0b12, 2022.1.0a8)
Note: if the NavMeshSurface has a different Z axis position (such as 139.9), the bug is not reproducible.
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
This is a known limitation. After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
We are closing this issue as Won’t Fix.
Resolution Note (1.0.X):
This is a known limitation. After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
We are closing this issue as Won’t Fix.