Game crashes at the end of loading a non-dedicated session

[Ryzane]

Game crashes at the end of loading a non-dedicated session

So a friend of mine and I started a new Aberration world yesterday and wanted to transfer some Extinction creatures into it and after we tamed the creatures in Extinction and wanted to load up the Aberration world again, the game crashed. So far I've tried verifying the game files via steam and deleting the GameUserSettings file, neither of them worked. the game always crashes at the end of world loading, just when I hear the very first sound, after which an error window opens.
This is the crashstack file I found:

Assertion failed: CaptureIndex >= 0 [File:F:\build\Live310Jenkins\Engine\Source\Runtime\Renderer\Private\ReflectionEnvironmentCapture.cpp] [Line: 666]



VERSION: 310.111
KERNELBASE.dll!UnknownFunction (0x00007fffe7e83e49) + 0 bytes [UnknownFile:0]
ShooterGame.exe!FOutputDevice::Logf__VA() (0x00007ff7c30e53da) + 179 bytes [f:\build\live310jenkins\engine\source\runtime\core\private\misc\outputdevice.cpp:145]
ShooterGame.exe!FDebug::AssertFailed() (0x00007ff7c30e598d) + 190 bytes [f:\build\live310jenkins\engine\source\runtime\core\private\misc\outputdevice.cpp:220]
ShooterGame.exe!FindOrAllocateCubemapIndex() (0x00007ff7c468720f) + 0 bytes [f:\build\live310jenkins\engine\source\runtime\renderer\private\reflectionenvironmentcapture.cpp:667]
ShooterGame.exe!UploadReflectionCaptureRaw_RenderingThread() (0x00007ff7c3a31bda) + 14 bytes [f:\build\live310jenkins\engine\source\runtime\engine\private\reflectioncapturecomponent.cpp:1540]
ShooterGame.exe!TGraphTask<`UReflectionCaptureComponent::UploadNewDerivedData'::`7'::EURCMacro_UploadCaptureCommand>::ExecuteTask() (0x00007ff7c3a5b8c0) + 17 bytes [f:\build\live310jenkins\engine\source\runtime\core\public\async\taskgraphinterfaces.h:871]
ShooterGame.exe!FNamedTaskThread::ProcessTasksNamedThread() (0x00007ff7c3054c38) + 0 bytes [f:\build\live310jenkins\engine\source\runtime\core\private\async\taskgraph.cpp:939]
ShooterGame.exe!FNamedTaskThread::ProcessTasksUntilQuit() (0x00007ff7c3053ded) + 0 bytes [f:\build\live310jenkins\engine\source\runtime\core\private\async\taskgraph.cpp:680]
ShooterGame.exe!RenderingThreadMain() (0x00007ff7c3527259) + 0 bytes [f:\build\live310jenkins\engine\source\runtime\rendercore\private\renderingthread.cpp:265]
ShooterGame.exe!FRenderingThread::Run() (0x00007ff7c3527650) + 0 bytes [f:\build\live310jenkins\engine\source\runtime\rendercore\private\renderingthread.cpp:385]
ShooterGame.exe!FRunnableThreadWin::Run() (0x00007ff7c3136c06) + 0 bytes [f:\build\live310jenkins\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:73]
ShooterGame.exe!FRunnableThreadWin::GuardedRun() (0x00007ff7c3136ac8) + 8 bytes [f:\build\live310jenkins\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:26]
KERNEL32.DLL!UnknownFunction (0x00007fffe8356fd4) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007fffea31cec1) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007fffea31cec1) + 0 bytes [UnknownFile:0]

My PC:
Ryzen 5 2400G
GTX 1050 Ti
ASUS Prime B350-Plus
16GB DDR4

Anyone know a solution? I really don't wanna redownload the game :c

[TheEclipseee]

What's your host tether distance set to? If you can, try turning it down.

[Ryzane]

I tried that too after posting the discussion since I read about it online and I originally had it set to 50, which allows my friend and me to be on opposite sites of most maps and it worked fine (even when we first played aberration), and then, after some testing, the highest tether distance that didn't crash seemed to be 15, but then, when I tried that with my friend, it crashed again and that's when I just gave up for the day. I might try messing with that setting again when I find the time (and will).

[TheEclipseee]

I've only ever seen this issue on Ab, you should at least be able to continue playing on other maps with normal distances. And yeah it's pretty annoying, seems completely random what distances it decides to crash at. I think I was set to 100 or something initially, then had to reduce it to 25 or so, and was then able to turn it back up to 50 again later, so maybe you'll be able to bump it up again at some point even if it has to be set quite low for now.