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
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
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/