Search Issue Tracker
Fixed
Fixed in 2022.3.45f1, 6000.0.10f1
Votes
0
Found in
2021.3.29f1
2022.3.7f1
2023.1.9f1
2023.2.0b6
2023.3.0a7
6000.0.0b11
6000.1.0a7
Issue ID
UUM-49446
Regression
No
Nav Mesh Agent is unable to move on the Y axis when the NavMeshSurface GameObject is rotated 90 degrees
Reproduction steps:
1. Open the attached project “NavMeshIssue”
2. Open the “Assets/Scenes/SampleScene” Scene
3. Enter the Play mode
4. Move the character using the “W” and “S” keys
Expected result: The character is moving up or down
Actual result: The character stays in place
Reproducible with: 1.0.0-exp.1 (2021.3.29f1), 1.1.4 (2022.3.7f1, 2023.1.9f1), 2.0.0-pre.3 (2023.2.0b6)
Reproducible on: macOS 13.4.1 (c)
Not reproducible on: No other environments tested
Comments (1)
-
adriant
Aug 30, 2024 08:57
Unity 2021.3 LTS does not receive the fix for this issue due to a possibly rare side-effect to the behavior of the NavMesh Agent in that version.
In the case of using the `NavMesh.Move()` function a workaround to this issue is to pass in as a parameter a Vector3 that does not have both the X and the Z coordinates equal to zero. Even a small value for either X or Z can help avoid the issue.
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Resolution Note:
Unity 2021.3 LTS does not receive the fix for this issue due to a possibly rare side-effect to the behavior of the NavMesh Agent.
In the case of using the `NavMesh.Move()` function a workaround to this issue is to pass in as a parameter a Vector3 that does not have both the X and the Z coordinates equal to zero. Even a small value for either X or Z can help avoid the issue.