fr-coder
(fr-coder)
January 13, 2025, 10:10pm
1
The nav link proxy is broken when using packaged build in windows. Trying to enable it during cause game crash. Anyone know a fix for that?
Here the steps to reproduce:
Create any project
Add a Nav Link Proxy.
Enable Nav Link Proxy Relevancy
Disable the Nav Link Proxy. Go to Smart Link → Link Enabled and uncheck
Remove any Simple Links → Point Links
Go to Project Settings → Navigation Mesh → Runtime Generation and select “Dynamic Modifier Only”
Open the level blueprint. In the Begin play, add a 5-second delay and enable the Nav Link Proxy using the function SetSmartLinkEnabled.
Package the game for windows
Run the game. it will crash
Logs:
[2025.02.01-08.59.04:654][622]Message dialog closed, result: Ok, title: The UE-MyProject6 Game has crashed and will close, text: Fatal error!
[2025.02.01-08.59.04:654][622]LogWindows: Error: === Critical error: ===
[2025.02.01-08.59.04:654][622]LogWindows: Error:
[2025.02.01-08.59.04:654][622]LogWindows: Error: Fatal error!
[2025.02.01-08.59.04:654][622]LogWindows: Error:
[2025.02.01-08.59.04:654][622]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffffffffffff
[2025.02.01-08.59.04:654][622]LogWindows: Error:
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf66f36f UnrealGame.exe!FNavigationDataHandler::RegisterElementWithNavOctree() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf687ffa UnrealGame.exe!FNavigationDataHandler::UpdateNavOctreeParentChain() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf683625 UnrealGame.exe!FNavigationDataHandler::UnregisterElementWithNavOctree() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf686fba UnrealGame.exe!FNavigationDataHandler::UpdateNavOctreeElement() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf646dab UnrealGame.exe!UNavigationSystemV1::CalcTimeSlicedUpdateData() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf6884f7 UnrealGame.exe!UNavigationSystemV1::UpdateNavRelevantObjectInNavOctreeStatic() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf685250 UnrealGame.exe!UNavigationSystemV1::UpdateComponentInNavOctree() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cfd28bf3 UnrealGame.exe!FNavigationSystem::UpdateComponentData() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf6f28b7 UnrealGame.exe!UNavLinkCustomComponent::SetEnabled() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf8d9ccb UnrealGame.exe!ANavLinkProxy::execSetSmartLinkEnabled() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6ca718fe9 UnrealGame.exe!UFunction::Invoke() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6caa325a9 UnrealGame.exe!UObject::CallFunction() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6caa5834d UnrealGame.exe!UObject::ProcessContextOpcode() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6caa5a188 UnrealGame.exe!ProcessLocalScriptFunction() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6caa59b43 UnrealGame.exe!UObject::ProcessInternal() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6ca718fe9 UnrealGame.exe!UFunction::Invoke() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6caa59675 UnrealGame.exe!UObject::ProcessEvent() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cfc8e034 UnrealGame.exe!AActor::ProcessEvent() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d07f2e5f UnrealGame.exe!FLatentActionManager::TickLatentActionForObject() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d07de5d0 UnrealGame.exe!FLatentActionManager::ProcessLatentActions() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d084bd63 UnrealGame.exe!UWorld::Tick() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d055d6cf UnrealGame.exe!UGameEngine::Tick() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d177ad25 UnrealGame.exe!FEngineLoop::Tick() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d178b60c UnrealGame.exe!GuardedMain() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d178b6da UnrealGame.exe!GuardedMainWrapper() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d178e3d2 UnrealGame.exe!LaunchWindowsStartup() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d179b2e4 UnrealGame.exe!WinMain() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d605753a UnrealGame.exe!__scrt_common_main_seh() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff8241be8d7 KERNEL32.DLL!UnknownFunction []
[2025.02.01-08.59.04:654][622]LogWindows: Error:
[2025.02.01-08.59.04:658][622]LogExit: Executing StaticShutdownAfterError
[2025.02.01-08.59.04:658][622]LogWindows: FPlatformMisc::RequestExit(1, LaunchWindowsStartup.ExceptionHandler)
[2025.02.01-08.59.04:658][622]LogWindows: FPlatformMisc::RequestExitWithStatus(1, 3, LaunchWindowsStartup.ExceptionHandler)
[2025.02.01-08.59.04:658][622]LogCore: Engine exit requested (reason: Win RequestExit)
EDIT:
This issue is a regression related to UE 5.5.1.
UE 5.4 is ok
3dRaven
(3dRaven)
January 13, 2025, 10:56pm
2
Tried to reproduce. Not getting any errors
Point
Relevancy
Link Enabled set to false
Point links cleared
Project settings
Level BP
After 5 seconds in packaged game
No crashes in shipping either
UE version 5.4
Operating system win 11
fr-coder
(fr-coder)
January 14, 2025, 12:04am
3
Thanks for trying to reproduce it. I am using using 5.5.1. I will try 5.4 as well and let you know if this is a regression
fr-coder
(fr-coder)
January 14, 2025, 7:19pm
4
Hello everyone,
I tested 5.4.4 as well and it doesn’t crash. So this is probably a regression related to 5.5.1.
I have reported an issue for that
1 Like
3dRaven
(3dRaven)
January 14, 2025, 9:05pm
5
Glad you were able to narrow it down in that case.
1 Like
Hey,
thanks for reporting the issue! We’re having the same problem after updating to 5.5.1. I worked with 5.4 and is still working when im downgrading back to 5.4.
Unfortunately I can’t find your report, could you please share it so I can upvote it?
fr-coder
(fr-coder)
January 24, 2025, 11:43pm
7
I have no notice about the bug report that I submitted here
https://www.unrealengine.com/en-US/support/report-a-bug
Is there anything that we can do to speed up that critical fix?
vtranPM
(vtranPM)
January 31, 2025, 7:21pm
8
could you paste your callstack and issue link? I wonder if it is what I am seeing
Im also having this issue, not in packaged game but in editor, using new 5.5.2 generated nav links, I get a crash and no log about it, just unexpected error and exit.
only happens when i turn generate nav links in nav mesh settings, and mess with the jump down settings a bit, everything works in editor fine, but when restarting, it will no longer open. Removing this change from config file allows project to open again, repeating it again does the same thing.
After some testing i found it only crashes when a bp_NavLink is set in the project settings. Which is the intended way of having logic in a nav link dictate how ai uses nav links when they reach them. Even while its blank, it causes a crash on reopening editor once the main function is overridden.
Haven’t checked with a fresh project, but wanted to know if someone else experienced this with their project in 5.5…
just an update;
I was able to workaround this by not including any casts in the override of the nav link proxy bp. Just relying on interface call to the executing actor/vector, it is able to subvert the crash. This is a cleaner approach anyways, so just wanting to leave it out there for everyone else who might run into this.
fr-coder
(fr-coder)
February 1, 2025, 8:44am
10
I have submitted it, but I don’t think the ticket has been created yet. I should receive an email once it’s processed. As a workaround, I’ve used a NavModifier for the doors, but this solution isn’t applicable in all cases. Here you can find the logs:
[2025.02.01-08.59.04:654][622]Message dialog closed, result: Ok, title: The UE-MyProject6 Game has crashed and will close, text: Fatal error!
[2025.02.01-08.59.04:654][622]LogWindows: Error: === Critical error: ===
[2025.02.01-08.59.04:654][622]LogWindows: Error:
[2025.02.01-08.59.04:654][622]LogWindows: Error: Fatal error!
[2025.02.01-08.59.04:654][622]LogWindows: Error:
[2025.02.01-08.59.04:654][622]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffffffffffff
[2025.02.01-08.59.04:654][622]LogWindows: Error:
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf66f36f UnrealGame.exe!FNavigationDataHandler::RegisterElementWithNavOctree() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf687ffa UnrealGame.exe!FNavigationDataHandler::UpdateNavOctreeParentChain() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf683625 UnrealGame.exe!FNavigationDataHandler::UnregisterElementWithNavOctree() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf686fba UnrealGame.exe!FNavigationDataHandler::UpdateNavOctreeElement() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf646dab UnrealGame.exe!UNavigationSystemV1::CalcTimeSlicedUpdateData() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf6884f7 UnrealGame.exe!UNavigationSystemV1::UpdateNavRelevantObjectInNavOctreeStatic() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf685250 UnrealGame.exe!UNavigationSystemV1::UpdateComponentInNavOctree() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cfd28bf3 UnrealGame.exe!FNavigationSystem::UpdateComponentData() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf6f28b7 UnrealGame.exe!UNavLinkCustomComponent::SetEnabled() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cf8d9ccb UnrealGame.exe!ANavLinkProxy::execSetSmartLinkEnabled() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6ca718fe9 UnrealGame.exe!UFunction::Invoke() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6caa325a9 UnrealGame.exe!UObject::CallFunction() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6caa5834d UnrealGame.exe!UObject::ProcessContextOpcode() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6caa5a188 UnrealGame.exe!ProcessLocalScriptFunction() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6caa59b43 UnrealGame.exe!UObject::ProcessInternal() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6ca718fe9 UnrealGame.exe!UFunction::Invoke() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6caa59675 UnrealGame.exe!UObject::ProcessEvent() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6cfc8e034 UnrealGame.exe!AActor::ProcessEvent() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d07f2e5f UnrealGame.exe!FLatentActionManager::TickLatentActionForObject() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d07de5d0 UnrealGame.exe!FLatentActionManager::ProcessLatentActions() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d084bd63 UnrealGame.exe!UWorld::Tick() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d055d6cf UnrealGame.exe!UGameEngine::Tick() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d177ad25 UnrealGame.exe!FEngineLoop::Tick() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d178b60c UnrealGame.exe!GuardedMain() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d178b6da UnrealGame.exe!GuardedMainWrapper() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d178e3d2 UnrealGame.exe!LaunchWindowsStartup() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d179b2e4 UnrealGame.exe!WinMain() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff6d605753a UnrealGame.exe!__scrt_common_main_seh() []
[2025.02.01-08.59.04:654][622]LogWindows: Error: [Callstack] 0x00007ff8241be8d7 KERNEL32.DLL!UnknownFunction []
[2025.02.01-08.59.04:654][622]LogWindows: Error:
[2025.02.01-08.59.04:658][622]LogExit: Executing StaticShutdownAfterError
[2025.02.01-08.59.04:658][622]LogWindows: FPlatformMisc::RequestExit(1, LaunchWindowsStartup.ExceptionHandler)
[2025.02.01-08.59.04:658][622]LogWindows: FPlatformMisc::RequestExitWithStatus(1, 3, LaunchWindowsStartup.ExceptionHandler)
[2025.02.01-08.59.04:658][622]LogCore: Engine exit requested (reason: Win RequestExit)
vtranPM
(vtranPM)
February 4, 2025, 10:54pm
11
that callstack is very close to what I see as well. Although in my case World Partition is removing an ANavLinkProxy which uses a Smart Link (UNavLinkCustomComponent) from the world. Thanks! I think this confirms we have basically the same issue but different repros.
tenpindan
(tenpindan)
February 19, 2025, 9:53am
12
Also getting the crash here after upgrading to 5.5.3
Navlinks cause a crash in a world partitioned world in a packaged game, when they are unloaded.
Things I’ve tried to no success:
The above fix by thelazylion didn’t work for me. I’m using interfaces already in the nav links
Turning off async nav generation
Saragan
(Saragan)
February 19, 2025, 10:17am
13
Hi, i put a work around for this here
Ok I have a temp fix
[image]
Created a new grid that is as big as the map and marked as always loaded, then set the actors with nav links to that grid, seems to have solved it temporarily
[image]
effectively just make stuff with nav links always load and no despawn, its hacky, obviously i would rather have the issue fixed but for now at least my game build and doesnt crash
The fix is targeted to 5.6, but if you have compiled engine, you can merge it from here:
https://github.com/EpicGames/UnrealEngine/commit/e6e021562c545a301f7ea58b2d03c7fe70ddbd8b