Skip to content

Quick Start

Jump to bottom
bbfox0703 edited this page Jun 25, 2026 · 2 revisions

🌐 English · 繁體中文 · 日本語

Quick Start: Install & Run

There are two ways to get UE5CEDumper into a game and stream live data to the UI:

  • Method A — Proxy DLL (recommended, no Cheat Engine needed)
  • Method B — Cheat Engine DLL injection (for games where a proxy can't load)

Pick one — never run both at the same time (see Don't mix methods).

0. Get the files

Option 1 — Download a release (easiest): Grab the latest UE5CEDumper-vNNNN-win-x64.zip from Releases and extract it anywhere.

Option 2 — Build from source:

powershell -NoProfile -ExecutionPolicy Bypass -File build.ps1 -Mode Publish -Clean

Output lands in dist\. (Needs Visual Studio 2022 / MSVC v143, CMake 3.25+, Ninja, .NET SDK 10.)

Either way you get:

File Used for Purpose
UE5DumpUI.exe both The GUI you connect with. Keep the support .dlls next to it.
proxy\version.dll, proxy\dxgi.dll, proxy\dinput8.dll A The three proxy variants — you copy one into the game folder.
UE5CEDumper.CT B Cheat Engine table that injects the DLL and starts the pipe server.
UE5Dumper.dll B The DLL the .CT injects into the game.
ue5_dissect.lua, other .dlls support Runtime/CE helpers — leave them where they are.

Requirements: Windows 10/11 x64 · a running UE4 / UE5 x64 game · Cheat Engine 7.6+ (only for Method B).

Method A — Proxy DLL (recommended)

No Cheat Engine required. Windows side-loads our DLL when the game starts.

  1. Place one proxy DLL. Copy a single file from proxy\ into the game's executable folder (next to the game's .exe). Start with version.dll.
  2. Launch the game normally. The proxy loads automatically and starts the pipe server in the background.
  3. Load a save / reach the main game world so UE objects are populated in memory.
  4. Connect + scan. Run UE5DumpUI.exe → Connect → Start Scan.
  5. Navigate & analyze. Browse the UObject tree, find instances, drill into containers, export CE structures.

Which proxy DLL?

  • version.dll — works for most games. Try this first.
  • dxgi.dll — use if the game launches but the UI can't connect: the EXE simply doesn't import version.dll. Every D3D11/D3D12 UE game imports dxgi, so it loads reliably.
  • dinput8.dll — alternative for some gamepad/DirectInput titles.

💡 The UI's Proxy Deploy tab can scan your Steam library, pick the right proxy per game, and deploy it for you.

Modular builds (e.g. Satisfactory)

Some games ship the real executable under Engine\Binaries\Win64\ instead of the game's own folder. Put the proxy next to that actual .exe (the Proxy Deploy tab detects this layout and places it automatically). Verified on Satisfactory v1.2.3.1 / UE 5.6 with version.dll.

Method B — Cheat Engine DLL injection

Use this when a proxy can't load — e.g. EA app / Epic launcher titles that restrict the DLL search path, or anti-tamper that blocks side-loaded DLLs. The scan itself works exactly the same once the DLL is inside the process.

  1. Attach. Open Cheat Engine 7.6+, attach the game process, and load a save first so game data is in memory.
  2. Open the table. Open UE5CEDumper.CT. Enable init <== enable after process attached, then enable Inject DLL + Start Pipe Server.
  3. Auto-scan. The DLL locates GObjects / GNames / GWorld and detects the UE version & memory layout automatically. Give it a few seconds.
  4. Connect. Run UE5DumpUI.exe → Connect (the scan from the .CT has already run).
  5. Navigate & analyze. Same workflow as Method A.

Don't mix methods

If a proxy DLL is in the game folder, do not also CE-inject UE5Dumper.dll. The DLL detects a duplicate instance and skips auto-start to prevent conflicts. Choose Proxy or Cheat Engine, not both.

Troubleshooting

Symptom Fix
UI won't connect (proxy) Wrong proxy variant → try dxgi.dll. Or the proxy isn't next to the actual exe → for modular builds place it in Engine\Binaries\Win64\.
UI won't connect (CE) Confirm the game is attached and both the init and Inject DLL scripts are enabled; wait for the scan to finish before clicking Connect.
Empty / no objects Load a save and reach the main game world before scanning — engine objects aren't populated at the title/menu screen.
EA / Epic launcher title Proxies don't load (launcher restricts the DLL search path) → use Method B (Cheat Engine).
GWorld not found A few games hide GWorld behind a decoy; the dumper recovers it automatically, but you can also start from Object Tree or Instance Finder.

Next steps

  • Full feature list, panels, and screenshots: Repository README.
  • Deeper guides (tips, export formats, technical notes): the repo's docs/ folder.

Clone this wiki locally