my game won't work (also im running it on epic games)
so for context I have uninstalled and deleted the folder for games and mods but still get this error. Included with the black background is a message from when i open it through epic and the one with the white background is what I get when it goes just lightly pass the loading screen but not up to the point to where it kicks over to actually loading the game
Solution:Jump to solution
"Shader compilation failures are Fatal." is a bug in 1.0 unrelated to mods and can be fixed by adding or removing the -dx11 launch argument from your game. For more info see >dx11
-# Responding to 1.0shaders triggered by @Borketh...5 Replies
>smm1.0
-# (Known issue
TargetRename1.0 / smmsteam1.0 / Temp1.0PluginFailedToLoad / DisableMods1.0 )
You cant play with mods on 1.0 yet!
Learn more: https://discord.com/channels/555424930502541343/555428529903239178/1282788921259987057
If you're trying to launch the game without mods:
1.0 has renamed the game target, preventing SMM from being able to automatically uninstall mods for you.
1. To manually turn off mods, delete the FactoryGame/Mods folder from your game install directory manually. Here's how to find the game install directory: https://docs.ficsit.app/satisfactory-modding/latest/faq.html#Files_GameInstall
- Even after you do this, SMM still won't work, and you will still get the "folder that does not exist" error message! You have to launch the game from Epic/Steam for now. Close SMM and don't use it again until we announce that mods are updated.
- If you have issues launching the game after this, also delete the FactoryGame/Plugins folder, then verify your game files to restore it: https://docs.ficsit.app/satisfactory-modding/latest/faq.html#_how_do_i_verify_my_game_files
- If you're still having issues, post the next error you get!shader compilation failures are fatal
Solution
"Shader compilation failures are Fatal." is a bug in 1.0 unrelated to mods and can be fixed by adding or removing the -dx11 launch argument from your game. For more info see >dx11
-# Responding to 1.0shaders triggered by @Borketh>dx11
(idk how this system worksbut i gotthe same problem)