Crashing Upon Launch
Whenever I try join my server, and sometimes so much as launch the game, I crash with the same logs as found below. It is on a linux server with these mods:
No idea why honestly.
Only happens on the server.
Logs:
Solution:Jump to solution
TL;DR
Was an issue of shaders not decompressing properly from an HDD, if you receive this error message, try installing on an SSD, if on steam, install only games with such errors on SSD should you be struggling for space...
22 Replies
update: I created a new world then joined the server, works but will likely crash again as usual
it's a rendering shader crash so I'd be suprised if it was particularly server related. Honestly rebooting your PC might resolve it, or clearing your shader cache
My apologies for the late reply, where would I find shader cache?
simplest way is to go to
Steam -> Settings -> Downloads then turn Enable Shader Pre-caching off and back onTried both, no changes.
perhaps corruption?
>debughere
Not sure. Can you post a full debug zip?
We need more information to help you. Before launching the game again, open the Mod Manager and use the "Generate debug info" option, then send the zip file produced here in this channel.
If you need to access older log files, see https://docs.ficsit.app/satisfactory-modding/latest/faq.html#Files_Logs
Automated responses for whar (679764737910767686)
Key Details for SMMDebug-2025-11-20-17-34-09.zip
smm_tls_timeout
Something is preventing SMM from contacting ficsit.app to determine what mod versions are avaialble. Are you using a VPN or proxy? Can you access https://ficsit.app in your web browser?
No vpn or proxy
Link is accessable
Every mod is latest version from the list in initial message
Wireshark it is
Shows up when I try launch
It's unrelated to your crash, anyway
could try changing your rendering engine
>rhiborked
There are a few things to try if your RHI is causing crashes.
1) Try switching your RHI. If you're using DX11 or DX12, switch to the other. If you're using Vulkan, try DX12 before DX11
2) Try verifying your game files.
3) Update/reinstall your graphics drivers
4) Try disabling hierarchal Z-buffer occlusion in the game's graphics settings.
5) Try tuning your graphics card's clock down, especially if has been overclocked (by you or the vendor)
For more info, run one of the following bot commands by sending it as a chat message:
>dx11 >dx12 >vulkan >verifyepic >verifysteam>debugmods
otherwise, it'll have to be this process
Follow this flowchart to troubleshoot issues caused by mods (crashes, unexpected behavior, etc.). More information can be found on the docs: https://docs.ficsit.app/satisfactory-modding/latest/faq.html#_how_can_i_troubleshoot_crash_issues
Nuked my cache folder and I'm in game
Also verified my game folders
if it doesnt crash in the next 4 hours, its resolved and ill mark it as such, thank you for your assistance and solution! @sjhoward
Absolute legend
oh interesting, just to clarify - your shader cache folder or your SMM cache folder?
My satisfactory cache
Mb spitter interupted me
Nuked my cache, settings, basiclly everything except save files and let it rebuild
and just like that it's back
welp
Re-installed on a diff drive and it worked like a charm
Solution
TL;DR
Was an issue of shaders not decompressing properly from an HDD, if you receive this error message, try installing on an SSD, if on steam, install only games with such errors on SSD should you be struggling for space
that being said
@Sam (Check for updates 🔄)
How would I go about pointing smm to my new download location
C:\SteamLibrary\steamapps\common\Satisfactory is new location
(i let steam fire at will basically)As long as steam knows where it is it should be better automatically
Occasionally steams libraryfolder files get out of date which can usually be fixed by rebooting steam or removing & readding the library folder in steam settings
Thank you!