Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.4.0f3
Issue ID
836113
Regression
No
[NavMesh] [Carving] NavMeshObstacle doesn't carve on the first Update frame
A navmesh obstacle that's set to carve (regardless of "Carve Only Stationary") will not carve just as the game starts. This means that if a component does a NavMesh.Raycast in Start or in the first Update, the raycast will go through the obstacle.
To reproduce
1. Open attached project
2. Run scene
3. Notice that one of the sphere gets through obstacle
Reproducible: 5.5.0b6, 5.4.1p3, 5.3.6p6, 5.2.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment