Install UE4SS

Find the game executable directory

Almost every failed install is a right file in the wrong folder. Get this bit right and the rest is drag and drop.

Unreal games have two folders that look like candidates. The outer one holds a small wrapper executable; the real game lives further in. You want the inner one — the folder containing BeachInvasion1944-Win64-Shipping.exe.

The quickest route in Steam:

• Right-click Beach Invasion 1944 in your library
• Choose Manage → Browse local files
• Explorer opens at the game root. From there open BeachInvasion1944 → Binaries → Win64

On a default install that lands you at:

C:\Program Files (x86)\Steam\steamapps\common\BeachInvasion1944\BeachInvasion1944\Binaries\Win64\

On a second drive or a custom Steam library it looks like the path below — which is the one in the screenshots on this site:

F:\SteamLibrary\steamapps\common\BeachInvasion1944\BeachInvasion1944\Binaries\Win64\

You are in the right place when you can see BeachInvasion1944-Win64-Shipping.exe sitting there — roughly 76 MB, and much larger than the wrapper you passed on the way in. Here is that folder with everything already installed:

Full size · 1920×1080

Know the four directory ideas

UE4SS documentation uses these four terms constantly. Two minutes here saves confusion later.

Game directory

The outer folder, holding a small wrapper executable and a folder named after the game. Not where UE4SS goes.

Game executable directory

The Binaries\Win64 folder holding the real, large executable. This is where the proxy DLL must live, always.

Root directory

Wherever UE4SS.dll itself sits. In a basic install this is the same folder as the executable.

Working directory

Wherever UE4SS-settings.ini, Mods\ and UE4SS.log sit. In a basic install this is also the same folder.

For a single game, all three of the last ones collapse into one folder, and that is what this guide does. UE4SS also supports a central install shared across many games, where the root and working directories live elsewhere — the official installation guide covers that, and it is unnecessary here.

Download the right build

Four downloads are offered and only one of them is the one you want.

Go to the latest UE4SS release on GitHub and open the Assets list at the bottom of the release notes. The current stable release is v3.0.1.

Extract the contents into Win64

Contents, not the folder containing them. This is the single most common mistake.

Open the zip and copy what is inside it directly into the Win64 folder from step 01. You should end up with the files themselves next to the executable — not a folder called UE4SS_v3.0.1 holding them.

Binaries\Win64\
├── BeachInvasion1944-Win64-Shipping.exe   ← already there
├── Mods\                                  ← from the zip
├── Changelog.md                           ← from the zip
├── README.md                              ← from the zip
├── UE4SS-settings.ini                     ← from the zip
├── UE4SS.dll                              ← from the zip
└── dwmapi.dll                             ← from the zip

These are the six items the zip contributes, and what each one is for:

Launch and verify it loaded

Do not tune anything yet. Prove it is running first.

Start the game normally through Steam. Then, back in the Win64 folder, look for a new file:

UE4SS.log

A fresh UE4SS.log with a current timestamp is your proof. Open it — the top should report the engine version it detected and the addresses it resolved, with no lines reading failed or Could not find.

Two other quick confirmations:

• In game, press F10 or @ to open the console that UE4SS's built-in ConsoleEnablerMod unlocks.
• Enable the GUI console in UE4SS-settings.ini and check that a separate window appears.

Settings worth knowing about

Three lines in UE4SS-settings.ini fix nearly every problem people hit with the 3.0.x releases.

UE4SS-settings.ini is plain text — open it in Notepad or anything similar. Change one thing at a time and relaunch, so you always know what caused what.

; The GUI console window comes up blank or white
GraphicsAPI = dx11

; The game crashes on startup with UE4SS installed
bUseUObjectArrayCache = false

; Show the UE4SS console window (dev builds have this on already)
GuiConsoleEnabled = 1
GuiConsoleVisible = 1

There is also a launch argument worth remembering. Adding it to Steam's launch options starts the game with UE4SS dormant, without uninstalling anything:

--disable-ue4ss

Remove the argument again to re-enable it. This is a much better first diagnostic step than deleting files when you are trying to work out whether UE4SS is involved in a problem.

Adding UE4SS mods later

The Mods folder, and the load list that controls it.

UE4SS mods go into the Mods\ folder that came out of the zip. Each mod is its own subfolder, and a plain-text mods.txt in the same directory controls which ones load and in what order.

Mods\
├── mods.txt                    ← the load list
├── ConsoleEnablerMod\          ← built in
├── ConsoleCommandsMod\         ← built in
└── SomeModYouDownloaded\
    └── Scripts\
        └── main.lua

ConsoleEnablerMod : 1
ConsoleCommandsMod : 1
SomeModYouDownloaded : 1

; 1 loads the mod, 0 skips it.
; The folder name here must match the folder name on disk exactly.

Removing or pausing UE4SS

Nothing here is permanent.

Pause it for one session: launch with --disable-ue4ss.

Disable it without deleting: rename the proxy so Windows stops loading it.

dwmapi.dll   →   dwmapi.dll.bak

Remove it completely: delete the files the zip added.

dwmapi.dll
UE4SS.dll
UE4SS-settings.ini
UE4SS.log
Changelog.md
README.md
Mods\  (the whole folder)