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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
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.