Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
2022.3.61f1
6000.0.46f1
6000.1.0b14
6000.2.0a8
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-102821
Regression
No
NavMeshQuery.BeginFindPath returns success status when searching short paths
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play mode
Expected result: No Errors exist
Actual result: Error “BeginFindPath is not documented to return Success“ is present
Reproducible with: 2022.3.61f1, 2.0.7 (6000.0.46f1, 6000.1.0b14, 6000.2.0a8)
Reproducible on:
Play mode
Not reproducible on:
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Changing Target Xform to “works” does not reproduce the issue
- Success status is not included in the documentation https://docs.unity3d.com/6000.0/Documentation/ScriptReference/Experimental.AI.NavMeshQuery.BeginFindPath.html
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
Add comment