Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0f3
Issue ID
932069
Regression
No
NavMeshAgent sometimes ignores NavMeshObstacle above the NavMeshLink
Steps to reproduce:
1) Download attached project 'NavMeshComponents-master copy.zip' and open in Unity
2) Open 'Test' scene
3) Press Play
4) Click on the floor around the corners of the box blocking the NavMeshLink(check attached video 'repro.mp4')
Note that sometimes NavMeshAgent goes through the collider which is above the NavMeshLink
Expected result: NavMeshAgent should avoid box cillider
Actual result: Sometimes NavMeshAgent goes through the collider(or even teleports)
Reproduced with: 5.6.0f1, 5.6.2p4, 2017.1.0f3, 2017.2.0b3
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
- 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
Resolution Note:
The NavMesh obstacles do not block the NavMeshLinks.