The Mound wiki
The Engine RoomUE5 · DEMO-MEASURED

Performance & settings

The honest version: the demo is beautiful and runs hot, with frame dips below 60 on hardware that should hold it. Here's what demo players verified actually helps — and what to re-test at launch.

Last updated 2026-07-12 · Patch pre-launch demo

Demo feedback split cleanly: broad praise for the atmosphere, and a steady stream of optimization complaints from demo players — "runs hot," frames dipping under 60, and a couple of genuinely angry thread titles. ACE Team patched during the demo window and launch-day drivers usually help UE5 titles, so treat this page as the demo-era baseline we'll re-measure on July 15. Crashes rather than dips? Fatal Error fixes are here.

What demo players verified

Restart after changing settings

The demo's single most misleading quirk: several video settings only take effect after a full game restart. Players benchmarking without restarting concluded settings "do nothing" — they do, after a relaunch.

Turn off camera smoothing

Multiple demo players reported the game feeling significantly better with camera smoothing effects off — it reduces perceived judder even when the frame rate itself doesn't change.

Install on NVMe, full stop

NVMe is listed as required in the official specs. On SATA/HDD installs the streaming-heavy jungle produces exactly the hitching players complain about.

Expect first-run shader compilation

Like most UE5 titles, the first minutes after install or a driver update are rougher while shaders compile. Judge your settings on the second session, not the first.

Cap your frame rate

The demo runs hot — players reported GPUs working hard with frames still dipping below 60. A cap at your monitor's refresh (or just below the dips) evens frame pacing and drops heat and noise.

A sensible starting sheet

Per-setting benchmarks aren't meaningful yet (see the restart quirk), so here is the conservative starting point we use on demo hardware, worth copying until launch data exists: quality preset one notch below what your GPU "should" run (High-tier card → High, not Epic), camera smoothing off, frame cap at refresh, upscaling on Quality rather than native at 1440p and up. The game's horror reads through fog, darkness and lantern light — it loses far less to a preset drop than a bright open-world game would. Your rig should still clear the minimum specs; the 6 GB-VRAM floor and NVMe line are real.

Performance questions

Why is The Mound stuttering on a good PC?

Three demo-era causes: settings changes that silently need a game restart, first-run UE5 shader compilation, and installs on non-NVMe drives (NVMe is required, not recommended). Fix those three before touching quality settings.

What are the best settings for The Mound demo?

Demo-verified: camera smoothing off, frame rate capped, quality preset one notch below your GPU tier, upscaling on Quality at 1440p+. Restart the game after changing anything — several settings only apply on relaunch.

Will performance improve at launch?

Unknown but likely some: ACE Team patched actively during the demo and shipped a known-issues list, and UE5 titles typically gain from launch-day GPU drivers. We re-benchmark on July 15.