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. The game is out now and launch-week reviews echo the same complaints — frame dips plus co-op desyncas the sharpest new one. We're re-measuring everything against the 1.0 build and updating as numbers firm up. 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 (now fixed)
The launch update fixed camera smoothing: disabling all camera effects gives true 1:1 mouse-to-camera movement. If the game felt laggy or 'floaty', this is the setting — and there's a Cinematic vs Default preset for it too. FOV was also widened to 75–125.
Install on an SSD
Steam does not formally require one — the listed requirement is 23 GB of space with no drive type named — but the streaming-heavy jungle produces exactly the hitching players complain about when it runs off a mechanical drive. This is the cheapest fix on the list.
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 is the one that actually bites.
Where to next
When it's not slow but dead.
The official spec sheet, with the myths removed.
Handheld expectations, honestly set.
1.01 added PC performance profiles and a camera pre-config screen.
Once it runs — your first expedition.
Everything else in short form.
Performance questions
Why is The Mound stuttering on a good PC?
Four common causes: settings changes that silently need a game restart, first-run UE5 shader compilation, installing on a mechanical drive, and the camera mode — patch 1.01 added a pre-configuration screen because the cinematic camera reads as input lag to some players. Also check the new PC performance profiles that patch shipped. Fix those 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.
Did performance improve at launch?
Partially. Launch reviews still report frame dips, and co-op desync emerged as the sharpest new complaint of launch week. ACE Team's demo-era patch cadence was strong — watch the post-launch patch notes; this page updates as 1.0 numbers firm up.