The Mound: Omen of Cthulhu can look excellent, but the jungle is rough on frame pacing. The best starting point is simple: cap the game at a frame rate your worst expedition can hold, use a quality-first upscaler, and lower only the settings tied to the problem you can actually reproduce.
Best Settings for The Mound
Start here after installing Patch 1.01. These are test values, not benchmark guarantees: run the same jungle route three times, then change one setting at a time.
Balanced starting profile
Use the exact options shown by your GPU and current game build.
Display & response
- Resolution
- Native output
- Framerate Limit
- 60 first
- Upscaling / Quality Mode
- Compatible option / Quality
- DLSS Frame Generation
- Off while testing
Image & feel
- Overall Quality
- Preset, then Custom
- View Distance / Lighting / Visual Effects Quality
- Test Medium
- Texture / Postprocessing Quality
- Medium; compare Postprocessing Low
- Camera Style / Motion Blur
- Normal / Off for clarity
If the full route cannot hold 60 FPS, choose a lower cap your system can sustain. If it holds 60 cleanly, test 90. A steady target beats a counter that collapses every time the jungle starts streaming.
What Patch 1.01 Actually Changed
Patch 1.01, released July 21, says it improved PC performance profiles, fixed the Motion Blur slider, and added distant level-of-detail models in areas with visible pop-in. It does not provide a measured FPS uplift, so old launch settings should be retested rather than treated as permanent fixes.
The patch notes call the more responsive camera behavior Standard, while the current selection screen labels it Normal. Use Normal if Cinematic feels delayed or uncomfortable. That changes camera response and comfort; it is not an FPS boost.
The official requirements ask for 16 GB of RAM, DirectX 12, and 23 GB of storage. The recommended GPUs are an RTX 3070 8 GB or RX 6750 XT 12 GB, but the store lists no resolution, preset, upscaling mode, or target frame rate. Treat those specifications as compatibility guidance—not a promise of 60 FPS.
Change the setting tied to the symptom
Do not destroy image quality to fix the wrong bottleneck.
Lower resolution helps a lot
You are likely GPU-bound. Keep output native, compare Quality and Balanced upscaling, then test Lighting and Visual Effects one step lower.
The same boundary always hitches
That points toward traversal or event work. Repeat three passes. If the first improves but the boundary spike remains, another graphics preset may not remove it.
1080p barely helps
Check CPU and GPU frame time. Test View Distance one step lower and compare solo, client, and host behavior before cutting every visual setting.
The camera feels heavy
Switch Camera Style to Normal and test again. Judge responsiveness separately from FPS so a comfort improvement is not mistaken for a performance gain.
DLSS, FSR 4, XeSS, and Frame Generation
The PC version exposes DLSS, FSR 4, XeSS, and TSR depending on your hardware. Nacon also confirms DLSS 4.5 Super Resolution and Dynamic Multi Frame Generation for compatible RTX 50-series cards.
Begin with the compatible Quality mode. Move to Balanced only when lowering internal resolution clearly improves the same test route. Compare foliage, rain, particles, and weapon motion—not only the FPS counter. The sharpest still frame is not always the cleanest image in motion.
Keep Frame Generation off while diagnosing. It can make displayed motion look smoother, but it does not remove CPU limits, traversal hitches, or a weak base frame rate. Enable it only after the game already feels stable and responsive. Official material does not establish universal FSR or XeSS Frame Generation support, so trust the options shown on your own system.
With a variable refresh rate (VRR) display, use one frame limiter and keep the cap below the rate your worst route can hold. Test VSync only as part of your chosen sync setup. If available, start with NVIDIA Reflex: On before forcing driver Low Latency Mode.
Use a three-pass test
- Record the build, driver, resolution, cap, upscaler, and host/client role.
- Run the same two-minute route three times.
- Change one setting, repeat the route, and validate it in traversal, combat, and co-op.
Low-End PC and Laptop Route
- Start at 1080p output and use the compatible upscaler on Quality.
- Set Framerate Limit to 60, or choose a lower target the full expedition can hold.
- Reapply a lower Overall Quality preset, switch to Custom, and test from there.
- Compare Medium and Low Postprocessing Quality. Test Lighting Quality and Visual Effects Quality one step at a time.
- Lower Texture Quality only when longer traversal produces repeatable video-memory pressure. Video memory, or VRAM, is the memory on the graphics card used for textures and other assets.
- Use Camera Style: Normal if Cinematic feels delayed. Leave Frame Generation off until the base game feels good.
For Windows-side basics, close recording tools or browser tabs that are measurably consuming resources, use the laptop’s intended gaming mode, and watch sustained temperatures and clocks. Hone’s guide to increasing FPS on PC covers the general cleanup without pretending a registry tweak can repair engine-level stutter.
The Short Version
Use native output with a quality-first upscaler, cap the game at a target the worst route can sustain, and test Medium as a starting point for the expensive visual groups. Keep Frame Generation off until the base game is stable. If lowering resolution barely changes FPS, stop sacrificing image quality and investigate CPU, host, or engine pressure instead.
Once the same route holds your chosen limit, use Hone to clean up avoidable Windows-side load and save the profile for your next expedition.
The Mound PC Settings FAQ
What are the best settings for The Mound: Omen of Cthulhu?
Start at native output resolution with a compatible upscaler on Quality, cap the game at 60 FPS or another sustainable target, and test Medium for View Distance, Lighting, Textures, and Visual Effects. Compare Medium and Low Postprocessing, and keep Frame Generation off while testing.
Did Patch 1.01 fix performance?
Patch 1.01 says it improved PC performance profiles, fixed Motion Blur, and added distant LODs, but the developer published no benchmark gain. Reapply a preset and retest your own route.
Which upscaler should I use?
Use the compatible DLSS, FSR 4, XeSS, or TSR option shown for your GPU. Start with Quality, test Balanced only when GPU-bound, and compare foliage, rain, particles, and motion on the same route.
How do I reduce stutter in The Mound?
Run the same route three times. If only the first pass improves, record it as warm-up. If the same boundary always spikes, treat it as traversal or event work. Lower Texture Quality only when longer routes show repeatable VRAM pressure.
Youtube