Search Issue Tracker
Active
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux Hub] A new instance of the Hub does not have a Taskbar icon
- Mesh Inspector becomes slow to use when inspecting a large Mesh with Blend Shapes
- [Metal] GfxDeviceMetal::CreateComputeProgram does not check inputs
- The Modes button of the the SerializedField MinMaxGradient is not clickable in the Inspector when indentLevel is more than 0
- Input.GetKey for Left Shift returns true when Right Shift is held down and Left Shift is pressed (and vice versa)
Add comment