Search Issue Tracker
By Design
Votes
1
Found in
2021.3.34f1
2022.3.17f1
2023.2.4f1
2023.3.0b1
6000.0.0b11
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-59747
Regression
No
NavMesh Agents struggle to make sharp turns when the application's framerate is limited
How to reproduce:
1. Open the attached “navmesh_fps_issue” project
2. Open the “TestScene” (Assets > AITest > TestScene)
3. Enter Play Mode and observe the result
Expected result: All NavMesh Agents move to the red sphere
Actual result: Two Agents get stuck when trying to take a sharp turn, then proceed to ping-pong back and forth
Reproducible in: 2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0b1
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Note: Also reproducible in Player
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
This is working by design, there are ways to handle this using our APIs,
we have added a Sample to the package demonstrating how to handle this case, it will be available in the next Package release 2.0.9