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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment