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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment