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
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
Add comment