Launch arguments
Jump to navigation
Jump to search
There are several launch arguments that alter the behavior of the game when used. Launch arguments have to be entered into the desktop shortcut address, command line, Steam launch options, or Epic Games additional command-line arguments field.
Setting launch arguments
Wherever launch arguments are entered, they have to be separated with a space and must include the dash "-".
Steam
- Open your Steam Library
- Right click the game's title and select Properties.
- On the General tab you'll find Launch Options section.
- Enter the launch options (see below) you wish to apply into the Launch options field at the bottom.
- Close the game's Properties window and launch the game.
Epic Games
- In the Epic Games client click Settings in the lower-left.
- Scroll down until you find a list of all games you currently have installed.
- Select the game.
- Check the box that says Additional Command-Line Arguments.
- Add the required launch arguments (see below) you wish to apply into the box.
- Close Settings and launch the game.
Shortcut
This method works for both launchers, and allows creating different sets of launch arguments.
- Navigate to the game's install directory (default
C:\Program Files\Steam\steamapps\common\Satisfactory
orC:\Program Files\Epic Games\SatisfactoryEarlyAccess
(orSatisfactoryExperimental
)) - Right-click the game executable and select "Create shortcut"
- Right-click the executable and select "Properties"
- Append launch arguments after the path in the Target field
Command line
This method works for both launchers, and allows a set of launch parameters to be used only once, without having to remove them later.
- Navigate to the game's install directory (default
C:\Program Files\Steam\steamapps\common\Satisfactory
orC:\Program Files\Epic Games\SatisfactoryEarlyAccess
(orSatisfactoryExperimental
)) - Open any terminal (CMD, PowerShell, Windows Terminal)
- Drag the game's executable over to the terminal
- Append launch arguments after the path
List of known launch arguments
Argument | Description |
---|---|
Graphics APIs | |
-d3d10
|
Forces DirectX 10 to be used (may not work) |
-d3d11
|
Forces DirectX 11 to be used |
-d3d12
|
Forces DirectX 12 to be used |
-vulkan [2]
|
Forces Vulkan to be used |
Connectivity | |
-NoMultiplayer
|
Disables all multiplayer related connections in-game by preventing the game to connect to EOS |
-NoSteamClient
|
Prevents Steam from starting when playing on Epic Games |
-EpicPortal
|
Internally used for logging in; when set manually, causes the game to skip login to EOS (akin to -NoMultiplayer )
|
Gameplay | |
-DisableSeasonalEvents [4]
|
Disables seasonal events, such as FICSMAS |
Other | |
-epicapp
|
Used when launching the game from Epic Games; the stable branch is set to Crab, experimental to CrabTest |
-epicenv
|
Used when launching the game from Epic Games |
-epicusername
|
Used when launching the game from Epic Games, set to the currently logged in user |
-epicuserid
|
Used when launching the game from Epic Games, set to the currently logged in Epic Account ID |
-epiclocale
|
Used when launching the game from Epic Games, set to the locale of the launcher |
-NO_EOS_OVERLAY [5]
|
Used when launching the game from Steam, prevents EOS overlay from appearing |
-USEALLAVAILABLECORES
|
Forces the game to use all CPU cores |
-nothreadtimeout
|
Disables the max waiting time of 120 seconds for the rendering threads |
-nosplash [6]
|
Disables the splash image on launch |
Other launch arguments can be found in the Unreal Engine 4 Documentation, although they may not all be functional.
References
- ↑ https://docs.unrealengine.com/udk/Three/DirectX11Rendering.html
- ↑ 2.0 2.1 2.2 NEW Features we've added to Update 5 since release
- ↑ https://www.epicgames.com/unrealtournament/forums/unreal-tournament-discussion/ut-game-general-discussion/14221-starting-in-dx12-mode
- ↑ https://store.steampowered.com/news/app/526870/view/5916039151451470744
- ↑ https://steamdb.info/app/526870/config/
- ↑ https://www.pcgamingwiki.com/wiki/Satisfactory#Skip_splash_screen
|