Search Issue Tracker
Fixed in 2018.1.X
Won't Fix in 2017.1.X, 2017.2.X, 2017.3.X
Votes
0
Found in
2017.1.0f3
Issue ID
944112
Regression
Yes
NavMesh.CalculatePath.corners return 0 when outside of the NavMesh area near to a wall or an edge
Reproduction steps:
1. Download project "PathApagar.zip" and open in Unity
2. Enter Play mode
3. Select Navigation
4. Chose object "dest" in scene "apagar"
5. Move "dest" to the edge of white platform until console shows "PathComplete, 0"
Expected: NavMesh.CalculatePath property corners should return corner points of the path even if destination is outside of NavMesh area
Actual: NavMesh.CalculatePath property corners returns 0 if outside of NavMesh area near to the edge or wall
Reproduced on: 2017.1.0b8; 2017.1.0p5; 2017.2.0b8; 2017.3.0a5
Not reproduced on: 5.6.3p1; 2017.1.0b7
Regression introduced: 2017.1.0b8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Masks affect Sprite Renderers outside their range when a Light2D is present with specific Target Sorting Layers selected
- URP Lens Flare is rendered in the wrong position when Render Graph Compatibility Mode is enabled and Render Scaling is not 0
- Editor crashes on DrvPresentBuffers when loading RenderDoc while using OpenGLES 3.0 or OpenGLES 2.0 Graphics API
- [Test Runner] Incorrect name under Window > Panel after project restart
- [iOS] Crash when using fallback fonts created at runtime
Add comment