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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
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/