Cannot compile UNavigationSystem in 4.20.1

Re4gNarsil · August 27, 2018, 4:41pm

Hey guys, I’ve tried searching all morning but can’t find a way to find the navigation system after going to 4.20 and get it to compile; I used to use

UNavigationSystem * NavigationArea = UNavigationSystem::GetCurrent(GetWorld()),
and have since tried the same thing but specifying UNavigationSystemV1, as well as

UNavigationSystemV1 * NavigationArea = FNavigationSystem::GetCurrent(this).
Neither compiles, giving me a LNK2019 error. Btw, I am using

#include “Runtime/NavigationSystem/Public/AbstractNavData.h”
#include “Runtime/NavigationSystem/Public/NavigationSystem.h”

And yes, I tried using the NavSysPathsUpdate.py just to see if that’d help; it runs for a split second, showed a few changes to make which I followed, and then closed automatically without doing anything. Any ideas?

Superwig · August 28, 2018, 1:55pm

You need to add the “NavigationSystem” module to your Build.cs
And to use FNavigationSystem::GetCurrent you need to specify the type

#include "NavigationSystem.h"
UNavigationSystemV1* NavigationArea = FNavigationSystem::GetCurrent<UNavigationSystemV1>(this).

Superwig · August 31, 2018, 12:37pm

And you’re sure you added “NavigationSystem” to your Build.cs modules? Because that’s the exact linker error you would get if you didn’t.

Re4gNarsil · August 31, 2018, 1:39pm

Okay, there we go. That’s what I missed; thanks.

Re4gNarsil · August 31, 2018, 12:21pm

Trying this, it still gives me the same error. I’ve attached a picture that shows the exact error message

Imagine-Games · January 5, 2019, 11:44pm

how do you add the navigation system module to the build.cs … what would be the lines to type?

bernhardrieder91 · February 17, 2019, 9:20pm

PublicDependencyModuleNames.AddRange(new string[] { “Core”, “CoreUObject”, “Engine”, “InputCore”, “NavigationSystem” });

Imagine-Games · February 18, 2019, 2:20am

Thanks bernhard, i actually figured it out eventually and also found another thing in my .ini file i had to change the paths as well, which i had but there was 1 elusive path i hadnt seen that was still there referencing the old system…

Ares9323 · September 17, 2021, 9:56pm

My problem was the missing “NavigationSystem” in the build.cs file, the same thing happened to me several times and I’d really like to understand HOW do you know what kind of name you have to add in that list and WHEN…
Is there a list of modules anywhere? Why is this not written in the documentation?
By the way thank you so much!

Superwig · September 18, 2021, 6:39am

It is in the documentation.
[Docs for UNavigationSystemV1][1]