Search Issue Tracker
Won't Fix
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
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.