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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment