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
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
Add comment