The primary goal for mega factory stability is reducing MainThread hitching. Every conveyor belt, machine animation, and power line update must be processed by the CPU. By modifying the Engine.ini, we can implement a “Precision Infrastructure” profile: moving as many tasks as possible to worker threads (Async) and increasing the maximum data transfer rate to prevent “teleporting” items on belts.
Hardware Compatibility & Expectations
- CPU Strategy: Satisfactory is extremely sensitive to CPU cache. These tweaks help distribute the “Update” load, but a high-frequency CPU (like a Ryzen X3D) remains the best hardware fix.
- RAM/VRAM: For mega factories, 32GB of RAM is effectively the minimum. We will set the
TextureStreamingto utilize this headroom properly. - DirectX 12: These tweaks are optimized for the DX12 renderer, which handles modern multi-threading much better than the legacy DX11 or Vulkan paths.
Backup and Preparation
Editing this file can cause the game to crash if the syntax is wrong.
- Completely exit Satisfactory.
- Navigate to your local AppData folder (path below).
- Copy Engine.ini, right-click, and save a backup copy as
Engine.ini.bak. - Open the original with Notepad++.
File Location
The configuration file is located in your local factory game folder: %LOCALAPPDATA%\FactoryGame\Saved\Config\WindowsNoEditor\Engine.ini (Note: If using Steam, it might be in \Windows\ instead of \WindowsNoEditor\ depending on your version.)
Best Engine.ini Settings for Mega Factories
Add the following blocks to the bottom of your file. These are categorized for better organization:
[/Script/Engine.Engine]
bSmoothFrameRate=true
MinDesiredFrameRate=30.000000
bAllowAsyncRenderThreadUpdates=1
bAllowAsyncRenderThreadUpdatesDuringGamethreadUpdates=1
[SystemSettings]
r.TextureStreaming=1
r.Streaming.LimitPoolSizeToVRAMAmount=1
r.CreateShadersOnLoad=1
r.Shadow.DistanceScale=1.5
r.ViewDistanceScale=1.0
tick.AllowAsyncTickDispatch=1
tick.AllowAsyncTickCleanup=1
[/Script/Engine.Player]
ConfiguredInternetSpeed=104857600
ConfiguredLanSpeed=104857600
[/Script/OnlineSubsystemUtils.IpNetDriver]
MaxClientRate=104857600
MaxInternetClientRate=104857600Pro Tip: The
MaxClientRatesettings are essential for multiplayer. If you see items “jittering” or sliding on belts while playing with friends, it’s often because the default network buffer is too small to send the data for thousands of items at once.
Key Parameters Explained
| Parameter | Recommended Value | Impact |
| tick.AllowAsyncTickDispatch | 1 | Moves machine/logic “ticks” to background threads, reducing MainThread lag. |
| r.CreateShadersOnLoad | 1 | Pre-compiles shaders to prevent “stutter” when looking at new factory sections. |
| r.Shadow.DistanceScale | 1.5 | Extends shadow rendering distance so your mega-towers don’t “pop” in. |
| MaxInternetClientRate | 104857600 | (100Mbps) Unlocks the network bandwidth for massive belt data in co-op. |
| bSmoothFrameRate | true | Helps stabilize frame-pacing when your FPS is fluctuating wildly. |
In-Game Settings vs. Config
To complement your Engine.ini, match these in-game Video settings:
- Conveyor Item Quality: Set to Low/Near. Rendering the physical 3D mesh of every iron plate on a 1km belt is a massive GPU hit.
- LOD Dithering: Set to OFF. This reduces the “fuzzy” transitions between high and low-quality models in the distance.
- Global Illumination (Lumen): Set to OFF. While beautiful, Lumen calculates real-time light bounces for every foundation and wall, which will crush your FPS in a mega-base.
- Max Sign Display Distance: Set to Near. If you have hundreds of signs for organization, they can cause significant UI rendering overhead.
Troubleshooting & Common Fixes
- Long Loading Times: Setting
r.CreateShadersOnLoad=1will make the initial loading screen longer, but the game will be much smoother once you are in. - Invisible Walls/Floors: This is a “Streaming” issue. If it occurs, change
r.TextureStreamingto 0 (Disabled), but ensure you have at least 16GB of RAM. - Settings Resetting: Satisfactory occasionally overwrites the file after a major “Experimental” branch update. Set the file to Read-only if this happens.
Frequently Asked Questions (FAQ)
Does “Async Tick” affect factory math?
No. It only changes how the CPU handles the scheduling of those calculations. Your machines will still produce items at the exact same rate per minute.
Why set ViewDistanceScale to 1.0?
Even on high-end PCs, setting this to “Ultra” or above in a mega-base forces the engine to calculate occlusion for thousands of machines you can’t even see. 1.0 (High) is the most stable “sweet spot.”
Will these settings fix “Auto-Save” stutters?
Partially. Auto-save lag is caused by the game serializing your entire world into a file. While these settings help the engine recover faster, the only true fix for auto-save lag is moving your save file to an NVMe M.2 SSD.
Conclusion and Expected Results
By manually refining your Engine.ini, you are shifting the “heavy lifting” away from the game’s main execution thread. You can expect fewer micro-stutters when traveling through your base, smoother belt animations in multiplayer, and a more stable experience as you approach the final phases of the Space Elevator.