Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
2022.3.61f1
6000.0.47f1
6000.1.0f1
6000.2.0a9
6000.3.0a1
6000.4.0a1
Issue ID
UUM-103973
Regression
No
NavMesh is not usable when using empty Bounds in BuildNavMeshData
How to reproduce:
1. Open the “IN-97204_TestNavMesh“ project
2. Open the “SampleScene”
3. In the Hierarchy select the Cube GameObject
4. In the Inspector window, for the Script Component, ensure that “Use Empty Bounds” is enabled
5. Enter Play mode
6. Observe Scene view
Expected result: Gizmo is visible and Agent moves to the Target
Actual result: Gizmo is not visible and error is present “"SetDestination" can only be called on an active agent that has been placed on a NavMesh.”
Reproducible with: 2022.1.0a1, 2022.3.61f1, 6000.0.47f1, 6000.1.0f1, 6000.2.0a9
Reproducible on: macOS 15.4.1 (M1 Max), Windows 10 (by user)
Not reproducible on: no other environments tested
Note: In the documentation it is mentioned that Empty bounds is treated as no bounds, i.e. the NavMesh will cover all the inputs
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
Add comment