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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.