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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment