0 votes
31 views
in Bug Report by (120 points)

This one is likely a hard one, I've found nothing on the types of errors I've been getting for this. I suspect it's something about my hardware, but it's weird because I've never had any issues with other unreal games before despite my unconventional hardware setup.

When I first started playing, I was about to play about 30 minutes, then it gave me a crash with Assertion failed in the SceneRendering.h. This was followed by a lot of issues getting the game to even start back up, it would either run and just show a black screen, or run and show the satisfatory logo and spinning wheel forever requiring multiple restarts of the game and the epic launcher (which itself has had so many problems...). Then I would finally be able to load back in only for the game to crash again shortly after loading the same. Sometimes it's the same Assertion failure, sometimes it was a memory access violation. Sometimes I even get a fatal error game thread timeout, this one only shows up when I can't even get to the main menu.
I thought maybe the save was corrupted so I made a new game. No dice.
I thought maybe the experimental build might be different, no dice. Looks like currently they are actually the same build version as well.
I'm incredibly frustrated, because the game is legitimately fun but I have been unable to play for longer than 30 minutes at this rate. Since I deleted my save I think I've had to go through the intro video a hundred times as the game will crash sometime between the character getting up out of the site, and shortly after I deconstruct the pod. I've tried all three landing spots as well. Let me know of any additional files / logs you'd like.

One of the outputs from the assertion failed type crashes:

Version: 106504

Assertion failed: PrimitiveCustomDataMemStack.GetSlack() > 0 [File:c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\renderer\private\SceneRendering.h] [Line: 1270]

FactoryGame_Win64_Shipping!FDebug::AssertFailed() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\core\private\misc\assertionmacros.cpp:429]
FactoryGame_Win64_Shipping!ComputeAndMarkRelevanceForViewParallel() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\renderer\private\scenevisibility.cpp:2150]
FactoryGame_Win64_Shipping!FSceneRenderer::ComputeViewVisibility() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\renderer\private\scenevisibility.cpp:3094]
FactoryGame_Win64_Shipping!FDeferredShadingSceneRenderer::InitViews() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\renderer\private\scenevisibility.cpp:3379]
FactoryGame_Win64_Shipping!FDeferredShadingSceneRenderer::Render() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\renderer\private\deferredshadingrenderer.cpp:610]
FactoryGame_Win64_Shipping!RenderViewFamily_RenderThread() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\renderer\private\scenerendering.cpp:2953]
FactoryGame_Win64_Shipping!TGraphTask<`FRendererModule::BeginRenderingViewFamily'::`26'::EURCMacro_FDrawSceneCommand>::ExecuteTask() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\core\public\async\taskgraphinterfaces.h:829]
FactoryGame_Win64_Shipping!FNamedTaskThread::ProcessTasksNamedThread() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\core\private\async\taskgraph.cpp:678]
FactoryGame_Win64_Shipping!FNamedTaskThread::ProcessTasksUntilQuit() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\core\private\async\taskgraph.cpp:575]
FactoryGame_Win64_Shipping!RenderingThreadMain() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\rendercore\private\renderingthread.cpp:333]
FactoryGame_Win64_Shipping!FRenderingThread::Run() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\rendercore\private\renderingthread.cpp:467]
FactoryGame_Win64_Shipping!FRunnableThreadWin::Run() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:76]

The error that often shows up when I can't even get past the title screen:

Version: 106504

Fatal error: [File:C:\Jenkins\workspace\I_BuildVersion-staging\UE4\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp] [Line: 1119] GameThread timed out waiting for RenderThread after 3175.43 secs

FactoryGame_Win64_Shipping!FDebug::AssertFailed() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\core\private\misc\assertionmacros.cpp:429]
FactoryGame_Win64_Shipping!GameThreadWaitForTask() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\rendercore\private\renderingthread.cpp:1125]
FactoryGame_Win64_Shipping!FlushRenderingCommands() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\rendercore\private\renderingthread.cpp:1226]
FactoryGame_Win64_Shipping!FDefaultGameMoviePlayer::WaitForMovieToFinish() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\movieplayer\private\defaultgamemovieplayer.cpp:440]
FactoryGame_Win64_Shipping!FEngineLoop::Init() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\launch\private\launchengineloop.cpp:3069]
FactoryGame_Win64_Shipping!GuardedMain() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\launch\private\launch.cpp:205]
FactoryGame_Win64_Shipping!GuardedMainWrapper() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\launch\private\windows\launchwindows.cpp:145]
FactoryGame_Win64_Shipping!WinMain() [c:\jenkins\workspace\i_buildversion-staging\ue4\engine\source\runtime\launch\private\windows\launchwindows.cpp:276]
FactoryGame_Win64_Shipping!__scrt_common_main_seh() [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:253]
kernel32
ntdll

System stats:
         Operating System: Windows 10 Pro 64-bit (10.0, Build 18362) (18362.19h1_release.190318-1202)
                 Language: English (Regional Setting: English)
      System Manufacturer: QEMU
             System Model: Standard PC (i440FX + PIIX, 1996)
                     BIOS: 0.0.0 (type: UEFI)
                Processor: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (8 CPUs), ~3.7GHz
                   Memory: 16000MB RAM
      Available OS Memory: 15998MB RAM
                Page File: 4446MB used, 14495MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: DirectX 12
 Card name: NVIDIA GeForce GTX 1080

The astute would go "What's System Manufacturer: QEMU"? I am running windows 10 inside a virtual machine, using VFIO GPU passthrough. This is where I think something may be going funky for some reason, because if "normal windows users" were having as many crashes as I am then I'm sure it would be posted about all over the place. The curiosity is however that I have never had any similar problems with any other unreal engine game, or any game in general. Hopefully we can find a solution that isn't just me having to refund it because I can't play at all.

I'd also like to take the time to say that I do hope in the future if you decide to add Satisfactory to other platforms that support Linux, I hope you consider publishing linux native versions as well. I've heard one of the upsides of the unreal engine is the ease at cross platform compiling and what not. The only reason I have to run this "unusual windows setup" is due to certain games not being native, or not working with wine/proton/steam play. In this case, since EGS doesn't support linux, and seemingly doesn't intend on it, I understand why currently there is no native linux support. But once that exclusivity deal is up, perhaps that could change.

Welcome to Satisfactory Q&A, where you can ask questions and receive answers from other members of the community.
In order to keep this site accessible for everybody, please write your post in english :)
August 28th update: We've removed downvotes! One major reason is because we don't want to discourage folks from posting legitimate suggestions / reports / questions with fear of being mass downvoted (which has been happening a LOT). So we now allow you to upvote what you like, or ignore what you don't. Points have also been adjusted to account for this change.
Please use the search function before posting a new question and upvote existing ones to bring more attention to them, It will help us a lot. <3
Remember to mark resolved questions as answered by clicking on the check mark located under the upvotes of each answer.
...