The FlyingNavigation plugin does not function properly when running on a dedicated server mode.

[xuxu2]

Describe the bug
I am experiencing an issue with the FlyingNavigation plugin when running on a dedicated server. The navigation system does not function properly.

To Reproduce
Steps to reproduce the behavior:

1. I followed the QuickStart guide to set up the sample project, and it works correctly when running in the editor.
2. However, when I run the project on a dedicated server, the FlyingNavigation agents do not properly follow the navigation path.
3. The issue is that the UNavigationSystemV1::SupportedAgents does not include the "fly" and "default" agents as set up in the QuickStart guide.
4. Debugging shows that the 0th index of SupportedAgents is set to the "recast" agent.
5. In the editor, the SupportedAgents has "fly" at index 0 and "default" at index 1.
6. The reason the dedicated server sets the 0th index to "default" (recast) is due to the following:
7. The UNavigationSystemV1::ApplySupportedAgentsFilter() function resets the SupportedAgents to the default object's SupportedAgents.
8. The GetDefaultObject() returns an object with "default" (recast) as the 0th agent in SupportedAgents.
9. This overwrites the previous correct SupportedAgents configuration.
10. I am using Unreal Engine 5.3, and the mentioned code is pure engine code without any customization.

Expected behavior
The navigation system should function correctly on the dedicated server, with the "fly" and "default" agents properly configured in the SupportedAgents.

Desktop (please complete the following information):

• OS: Windows 11
• Version [Microsoft Windows [Version 10.0.22631.4317] / Plugin Ver : Lastest

Additional context

[BlenderSleuth]

Thanks for leaving this bug report - I'll be able to take a look next week.

[BlenderSleuth]

Ok, I've had some time to try to figure out what the problem is. I've set up the navigation agents as you describe (note: I've changed the Nav Agent Height values to be different between agents, because otherwise the registration can have issues):

And I've created an AI pawn that attempts to follow the player using a FindPathToActorAsynchronously and a RequestMove in the AI controller:

It will also wait for the player to be spawned on the server first. With this setup, specifically with the controlled pawn being plugged into the pathfinding context, the dedicated server config worked perfectly (both simulated in the editor and in a packaged game).
Sometimes the supported agents have problems when the Default Agent Name is not valid, the agent radius and height are the same between agents and sometimes the level needs to be reloaded and rebuilt when navigation agents are updated in project settings.
Is there some other set up step that might be the issue?

[BlenderSleuth]

Hi there,

I'll be around in Jan to help fix your issue, but I'm afraid I will be away from Febuary 2025 until the end of the year, and won't be able to help from then.

[xuxu2]

Sorry for the late reply, I checked as you told me and tried again and it started to move. Our difference from you is that we use aimovetto to move our pawns. But this doesn't seem to be the problem. Now that I've re-configured it, it's working. But the problem is that sometimes pawns can't move. What should I do?

[BlenderSleuth]

AI Move To should do a very similar thing to my setup, so that shouldn't make a difference. The two main troubleshooting things for transient pawn movement problems are drawing the path (the Draw Debug Paths option on the flying navigation data actor) and checking the logs to see if any warnings are emitted.