Unknown
This game runs flawlessly on my PC. It's fun and very rewarding to play. Using Proton Experimental but not required.
Multiplayer not possible on different game servers; you always get stuck on the loading screen.
Proton Experimental Proton 8.0-3 Proton GE-Custom z.âŻB. GE-Proton8-25 Tested various Proton versions and a few startup parameters, but the error persists! Single player mode runs without any problems!
I was having an issue with the game not opening whatsoever- no matter what I did. I couldn't figure out what the issue was, but decided to check for an Nvidia driver update. And I updated from 560 to 575 and the game works perfectly now. An update to the game rendered it unoperable on my past driver, which is kind of annoying/concerning. But at least I found a solution.
gamemoderun mangohud gamescope -w 2560 -h 1440 -f --sharpness 6 --force-grab-cursor -- %command%
gamemoderun â Enables GameMode (performance optimizations)
mangohud â Enables MangoHud (performance overlay)
gamescope â Runs the game in a nested Wayland session
-w 2560 â Sets width to 2560 (upscales from 1080p to 1440p)
-h 1440 â Sets height to 1440 (upscales from 1080p to 1440p)
-f â Enables fullscreen
--sharpness 6 â Applies very high sharpness to scaling
--force-grab-cursor â Forces the game to grab the mouse cursor
-- %command% â Executes the game with these options
Used protontricks to launch winecfg to set the Graphics DPI to 192 to make the game scale correctly when using the Wayland backend for Wine/Proton.
The game code is braindead. It uses a mixture of software rendering and hardware (OS) rendering for the mouse cursor, leading the game cursor to jump around randomly when you hover any textbox in the game. It is therefore impossible to target/click on the textbox. This bug only happens on Wayland.
There are three workarounds: Run the game via X11, or run it via gamescope, or run it with the Wayland rendering backend for Wine/Proton.
Read the post by "Chimpans" at the official Satisfactory bug report forum to see the workarounds for the game's mouse bugs on Linux:
https://questions.satisfactorygame.com/post/66eedcad772a987f4a8c2101
(And if you have a forum account, upvote the bug report itself so that the developers might finally fix their game code.)
Works fine
crashed the first time I got into the game
I only changed the graphical API to Vulkan, other than that I didn't change anything
Game works great, and in my case runs better than on Windows, averaging at around 120FPS with no upscaling, 4K res and full ultra graphics.
Install & Play. I also tried "Steam Experimental" Proton and works just as well.
LD_PRELOAD="" %command% -vulkan
Tabbing out and in can make the game way laggier or have it crash
Random bursts of input and performance lag when deconstructing, building large blueprints, or blowing up rocks. They need to turn off the building animation and change whatever they're doing to make blown up rocks tank my FPS to about 5
Awful framerate for no apparent reason, I can get about 25fps average after dropping the settings but it drops for no reason quite often
Crashes for no apparent reason very frequently
Nothing that I think is linux exclusive, but this game is ridiculously buggy. I've found bugs with rails, pipes, signals, blueprints, stations, motor vehicles. You name it
Nothing works any more
-dx11
I was running vulkan on proton 9 for a while and preloading shaders, but that was crashing quite often for no obvious reason. So I switched to dx12 on proton 10 and that worked for a while but it was very laggy, so I increased my upscaling which didn't help performance at all, and instead after closing the game I'm now I'm completely unable to launch the game with any settings at all. I've tried forcing vulcan, dx11, dx12, preloading, hotfix versions, old version, etc etc and absolutely nothing can even get me to the menu screen. Vulkan in particular now claims I don't even have the ability to run the vulkan engine despite it working in the past
Won't open anymore. I played 100+ hours on the 1.0 release but after a hotfix a few months back it just shows the splash and then closes.
-vulkan
Used to work. Doesn't even get to the menu now.
Decreased Graphic settings
On Steam Deck, make sure to display Steam Input for the controller, otherwise it won't work correctly. Otherwise pretty good performance
Outstanding performance on Linux. All graphics settings are maxed and never have had a stutter or massive drop in FPS.
On rare occasions, when I am launching the game while working on another screen not hosting the game, as I come back to the game screen the mouse mouses but the L/R mouse clicks are not functional. This requires a restart of the game. Its rare, but its happened multiple times.
Amazing game, amazing performance. Highly recommend this game on Linux.
%command% -dx11
Saves carried over from windows 10, the blueprints did not, not sure if it's due to blueprints not saving to cloud or something else.
Game asked to install Microsoft Visual C++ on launch with CachyOS Proton, switching to Proton Experimental allowed me to launch the game. Loaded my save and ran around for 5 minutes, the game runs as expected.
great game!
- AMD FSR: The upscaling with AMD FSR resulted in an almost complete dark screen when I was near radioactive material. => I disabled AMD FSR.
- Shader compilation: Dont skip the shader compilation, otherwise I got sometimes stutters.
.
game-performance %command%
%command% -vulkan
In areas with heavy use of lights some artifacs show up on beams, might be a vulkan thing
Runs with a few more fps with using -vulkan but not needed
If you like automation, It ran really well. I was satisfied after "trouble shooting" attempts. Ebcak aside, 10/10 would satisfy again.
Installed Proton 9.0.4, and then CachyOS 10.0
First game to tell me I needed Visual C++ on linux after installing and running through proton compatability. Saw people speak about disabling the cache download, and did so prior to attemping to trouble shoot installing a windows program on linux.
Solution: half an hour of frustation of searching how to install Visual C++ on linux, ended up hitting the install/yes button.. Went through a download, booted up quickly.
I hope this saves another that's used to windows, but new to linux and doesn't just.. attempt to click the install, trying to avoid having to troubleshoot.. I hope this saves someone atleast 20 minutes to an hour of time.. Also, you're on linux, don't fear troubleshooting, it's been easy on Linux Mint so far.. Expand your mind like your factory, It Must Grow.
LD_PRELOAD="" PROTON_ENABLE_WAYLAND=1 ENABLE_VKBASALT=1 game-performance %command% -vulkan
I forced vulkan because the game used to fall back to dx11 for some reason, and it seems to give more performance, but I didn't do comprehensive testing between them. vkbasalt used for CAS (sharpness) effect, because in-game TAA is too blurry for my liking even at native 1440p. Overall no issues with the game, it's a very enjoyable experience!
works great
We connected through Steam and it just worked
.
mangohud DRI_PRIME=0 RADV_PERFTEST=ngg,rapm,radv_rt=1,sam,cache_compressor,wave32,dualcu VKD3D_CONFIG=dxr11,dxr,no_upload_hvv mesa_glthread=true AMD_DEBUG=zerovram,nodma RADV_VIDEO_DECODE=0 PROTON_ENABLE_NVAPI=0 DXVK_ASYNC=1 %command%
Didn't carry over from Windows, lost all saves i had.
Successfully finished the game with no major issues.
No crashs, no visual glitchs or slow-downs; I was even able to turn on all my preferred mods, some of which are pretty game-changing.
can't install without proton (I think?) without however? The game worked just fine without mods, after turning on mods it crashed the first-time on boot-up; restarting fixed it just fine.
Ended up turning on 9.0-4; diden't realize till later that not going with the default of 'hotfix' counted as "tinkering"--haven't bothered trying with that version.
this is a slow boot-up process where the vulken shaders are processed or something (about 1-2 minutes) but after that it worked just fine.
Laggy input pops up very rarely, most of the time restarting the game fixes the issue.
One day the game stopped working for me: It stuck on the loading screen forever. I figured out, that disabling the shader cache in Steam fixes the issue.
-vulkan
randomly for no apparent reason. Just put auto save to 5min
đ
%command% -dx11 -norhithread
Had to force dx11 as dx12 was giving me around 15 fps (vs 35 from dx11).
Also, vulkan completely didn't work for me with the error of "LogWindows: Error: appError called: Assertion failed: bSuccess [File:C:\BuildAgent\work\9fc8da665efb5ffd\UE4\Engine\Source\Runtime\VulkanRHI\Private\VulkanCommandBuffer.cpp] [Line: 503] "
Had a crash/freeze up as i was playing just today, unsure the cause, will be looking in to that. otherwise it runs smoothly, and as it should. I just bought the game June 2025 so i have no reference to how it runs in Windows to compare.
LD_PRELOAD="" %command% -dx12
On certain anti-aliasing modes only? TAA seems okay
Windows DX12: 70-75FPS average
Linux DX12: 60-69FPS average
Regardless of FPS, feels slightly smoother on Windows, although you'd need a back-to-back comparison to notice
For Intel Arc B580, DX12 seems to be the best option at this time - Vulkan seems to crash with a memory leak, DX11 worse performance
