Discovered Some errors with Unity 6

Unity Engine
, , ,
1

Hi everyone I have some error with new unity version (I mean unity 6) I think the errors related to Navmesh here is errors:

  1. NullReferenceException: Object reference not set to an instance of an object Unity.AI.Navigation.Editor.NavigationOverlay.DisplayAgentPendingRequestWarningBox () (at ./Library/PackageCache/com.unity.ai.navigation@3f89ad87253d/Editor/NavigationOverlay.cs:297) UnityEditor.AI.NavMeshEditorHelpers.OnAgentDebugInfoRequestsPending () (at <82d5427af9d84542ac1bab8e50c139c7>:0)

  2. NullReferenceException: Object reference not set to an instance of an object Unity.AI.Navigation.Editor.NavigationOverlay.HideAgentPendingRequestWarningBox () (at ./Library/PackageCache/com.unity.ai.navigation@3f89ad87253d/Editor/NavigationOverlay.cs:306) UnityEditor.AI.NavMeshEditorHelpers.OnAgentDebugInfoRequestsProcessed () (at <82d5427af9d84542ac1bab8e50c139c7>:0)

noticed that

  1. both error popup when I ran game but also I get first error when I pause my game
  2. this errors does not effect on my game

hope you fixed on next version

2

You should file a bug report with the menu inside of Unity.

4

Hi Bella964 thanks for Answer when I Update Ai Navigation Package both error gone thanks again for you help

5

It’s gone how?
When ?
Which version of Unity and AI.Navigation did you used ?
SHARE INFOS :angry:

Anyway we’ve worked around the bug on Unty 6000.0.42F1 by disabling the NavMeshAgent from Gizmos menu.

6

FWIW, I’ve also been seeing this in 6000.0.43f1 and AI.Navigation 2.0.6. I had noticed it only happened when my NavMeshAgent was selected, but it hadn’t occurred to me that disabling gizmos might help - and that did the trick indeed for me, so thanks for that tip @MaxKillstudios!

I’m guessing the OP hadn’t noticed that this was only happening when their NavMesh was selected, and upgrading the package only seemed to help because they didn’t have theirs selected when they tested next time?

Then I noticed that AI.Navigation 2.0.7 was now available (though only since 2025-04-09, so can’t be the version upgraded to by OP), so I tried upgrading to that… and so far I’m not seeing the same problem, even with my NavMeshAgent selected and with NavMeshAgent gizmos on… so unless there is some additional criterion for this hapening, perhaps 2.0.7 included a fix? There’s no mention of it in the change log though.

Anyway, hope this helps someone. Kind regards,

Andy