Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.3.0a1
2018.3.0a1
2018.3.0f1
2019.1.0a1
Issue ID
1108264
Regression
No
agent.path.corners.Length does not always match agent.path.GetCornersNonAlloc() when path is broken from carving
Steps to reproduce:
1. Download and open the attached project
2. Open Scene "test1.unity"
3. Enter Playmode
Expected result: CornersCountAlloc would always match path.corners.Length
Actual result: sometimes it does not match and reports the value of the initial given array(e.g. CornersCount (0) != CornersCountNonAlloc (3))
Reproduced on 2017.3.0a1, 2017.4.16f1, 2018.3.0f1, 2019.1.0a11
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
Will be fixed as part of substantial refactoring work planned for the NavMeshAgent.
More information will be communicated on the Navigation forum. https://forum.unity.com/forums/navigation.79/