Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.2.0b11
Issue ID
951986
Regression
No
NavMeshAgent.FindClosestEdge does not position object on the closest edge if NavMesh is made of separate surfaces
Steps to reproduce:
1. Open "NavMeshBugs.zip"
2. Load Scene TestScenes/NavmeshExample
3. Enter Play mode
4. Press the 'G' key to generate the NavMesh and position the EnemySpawner and PlayerBase objects at the closest edge of the navmesh
Note: the NavMesh has to consist of multiple separate meshes for the problem to occur
Expected result: the objects are placed on the closest edge
Actual result: the objects are placed at the edge of the same surface despite which one is the closest
Reproducible with: Unity 5.6.3f1, 2017.1.0b1, 2017.1.1f1, 2017.2.0b11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Double separation lines are present in a kebab dropdown menu
- [URP] CommandBuffer: built-in render texture type 3 not found while executing warning is thrown when Game view is open and OpenGL is used
- User gets "Sorry...that page seems to be missing" when click a help icon
- Horizontal Scrollbar appears in the Inspector Window when the Volume Component is added
- Build Profiles - Feature Request: Editor restart button would improve the user experience
Add comment