Constant Fatal Error crashes when traveling to new regions...

[Flam3]

Until a couple or so patches ago my game ran completely fine, no crashes, just the expected performance issues that got slightly better as the patches rolled out. Now this was the case for over 100 hours of playtime...

But after whatever patch came out, I now get a Fatal Error crash each and everytime I travel to a new region. At first it seemed like running in low memory mode might have been a temporary fix, but nope, started right back up as I was going back through the first region that got the crashes started and then it just got worse as time went on to the point that it now crashes with the same fatal error no matter which region I travel into. I will say the game runs fine when I am actually loaded into the region and I am playing on an Unofficial server and apparently no one else is having this issue.

Here is the log file -

Fatal error!



VERSION: 10.42 
AtlasGame.exe!AShooterHUD::UpdateMapMaterial() (0x00007ff7a07365dd) + 7 bytes [h:\yarkupdate\projects\shootergame\source\shootergame\private\shooterhud.cpp:3562]
AtlasGame.exe!AShooterPlayerController::TickActor() (0x00007ff7a0767d0a) + 0 bytes [h:\yarkupdate\projects\shootergame\source\shootergame\private\shooterplayercontroller.cpp:2562]
AtlasGame.exe!TGraphTask<FTickTaskSequencer::FTickFunctionTask>::ExecuteTask() (0x00007ff7a1cf8b76) + 31 bytes [h:\yarkupdate\engine\source\runtime\core\public\async\taskgraphinterfaces.h:871]
AtlasGame.exe!FNamedTaskThread::ProcessTasksNamedThread() (0x00007ff7a12076f8) + 0 bytes [h:\yarkupdate\engine\source\runtime\core\private\async\taskgraph.cpp:939]
AtlasGame.exe!FNamedTaskThread::ProcessTasksUntilQuit() (0x00007ff7a12068ad) + 0 bytes [h:\yarkupdate\engine\source\runtime\core\private\async\taskgraph.cpp:680]
AtlasGame.exe!FTaskGraphImplementation::WaitUntilTasksComplete() (0x00007ff7a1209670) + 0 bytes [h:\yarkupdate\engine\source\runtime\core\private\async\taskgraph.cpp:1777]
AtlasGame.exe!FTaskGraphInterface::WaitUntilTaskCompletes() (0x00007ff7a12af1f9) + 17 bytes [h:\yarkupdate\engine\source\runtime\core\public\async\taskgraphinterfaces.h:319]
AtlasGame.exe!FTickTaskSequencer::ReleaseTickGroup() (0x00007ff7a1cbfaa9) + 85 bytes [h:\yarkupdate\engine\source\runtime\engine\private\ticktaskmanager.cpp:188]
AtlasGame.exe!FTickTaskManager::RunTickGroup() (0x00007ff7a1cc5a9c) + 0 bytes [h:\yarkupdate\engine\source\runtime\engine\private\ticktaskmanager.cpp:999]
AtlasGame.exe!UWorld::RunTickGroup() (0x00007ff7a1af88e6) + 0 bytes [h:\yarkupdate\engine\source\runtime\engine\private\leveltick.cpp:701]
AtlasGame.exe!UWorld::Tick() (0x00007ff7a1af9d41) + 0 bytes [h:\yarkupdate\engine\source\runtime\engine\private\leveltick.cpp:1227]
AtlasGame.exe!UGameEngine::Tick() (0x00007ff7a1a2b9c4) + 0 bytes [h:\yarkupdate\engine\source\runtime\engine\private\gameengine.cpp:1181]
AtlasGame.exe!FEngineLoop::Tick() (0x00007ff79ffd8a9a) + 0 bytes [h:\yarkupdate\engine\source\runtime\launch\private\launchengineloop.cpp:2449]
AtlasGame.exe!GuardedMain() (0x00007ff79ffd354c) + 0 bytes [h:\yarkupdate\engine\source\runtime\launch\private\launch.cpp:140]
AtlasGame.exe!GuardedMainWrapper() (0x00007ff79ffdb47a) + 5 bytes [h:\yarkupdate\engine\source\runtime\launch\private\windows\launchwindows.cpp:125]
AtlasGame.exe!WinMain() (0x00007ff79ffdb5a8) + 8 bytes [h:\yarkupdate\engine\source\runtime\launch\private\windows\launchwindows.cpp:209]
AtlasGame.exe!__tmainCRTStartup() (0x00007ff7a2d0674d) + 21 bytes [f:\dd\vctools\crt\crtw32\dllstuff\crtexe.c:618]
KERNEL32.DLL!UnknownFunction (0x00007ff882ce3034) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ff885853691) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ff885853691) + 0 bytes [UnknownFile:0]

It's a shame as I was actually starting to enjoy the game with the Unofficial server experience.

EDIT: I have tried the usual verify game cache, honestly seemed to make it worse.

[Flam3]

So, found this on the official forums.

https://www.playatlas.com/index.php?/forums/topic/20463-872-fatal-errors-and-connection-issues-sextant-bug-at-border-crossing/

Turns out that the sextant buff on the UI was causing the issue. Tested this by firstly not having the sextant buff active and all was well.

And apparently if you do have the sextant buff and hide the UI before traveling also helps.