Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0b10
Issue ID
922847
Regression
Yes
CalculatePath() fails to find a path between two valid connected locations
Steps to reproduce:
1. Open the attached project(PathBug.zip)
2. Open the Assets/BadPath.unity scene
3. Play the scene (Ensure the Navigation Window is selected in the Editor)
4. Observe the Console Window and the Navigation Window:
A valid NavMesh is produced which covers and links both red points
No path is found between the two red points
The logging shows the NavMesh is valid, the two red points are valid, but the is no path found
Expected result: CalculatePath() should find a path between two valid connected locations
Actual result: CalculatePath() fails to find a path between two valid connected locations
Reproduced with: 2017.1.0b9, 2017.1.0b10, 2017.2.0a4
Not reproduced with: 5.5.4p1, 5.6.2f1, 2017.1.0b8
Regression introduced in: 2017.1.0b9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment