Search Issue Tracker
Fixed in 2022.2.X
Votes
6
Found in
2020.3
2020.3.2f1
2021.1
2021.2
Issue ID
1335385
Regression
No
Path is impassible for the Agent when multiple lines connecting obstacle gaps are together
How to reproduce:
1. Open the user's attached "NavMeshComponents-master" project
2. Open the "3_free_orientation" Scene
3. Enter the Play Mode
4. Press at the top of the green area (straight above the yellow cylinder Agent)
Expected results: The Agent walks straight up
Actual results: The Agent takes a long walk around
Reproducible with: 2020.3.9f1, 2021.1.8f1, 2021.2.0a17
Could not test with: 2018.4.35f1, 2019.4.27f1 because of the errors "File may be corrupted or was serialized with a newer version of Unity"
Note:
- Moving one of the objects that the connecting line belongs to will fix the impassible line
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
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
Resolution Note (fix version 2022.2):
Fixed in Unity 2022.2.0a2