Minecraft Dungeons II Best PC Graphics Settings
SymptomFrame rate is uncapped or unstable, or effects look noisy or flicker on PC.
To get Minecraft Dungeons II (Minecraft Dungeons 2) running smoothly on PC, cap your frame rate to your monitor’s refresh rate, turn Effects down from maximum if you see flicker or noise, and match your PC to the Steam requirements. Players report the game is well optimized: one reviewer saw 240 FPS on Ultra, while others report a hard-to-cap first launch and noisy effects at the top setting. We haven’t played the game yet, so we don’t list exact menu names; option names in your build may differ.
What the requirements say
Per the Steam store page:
| Minimum | Recommended | |
|---|---|---|
| OS | Windows 10 64-bit (1703+) | Windows 10 64-bit (1703+) |
| CPU | Intel Core i3-8100 / AMD Ryzen 3 2200G | Intel Core i5-8400 / AMD Ryzen 5 2600 |
| RAM | 8 GB | 16 GB |
| GPU | GTX 1050 / RX 560, 2 GB VRAM | GTX 1060 / RX 580, 6 GB VRAM |
| DirectX | 11 | 11 |
See our system requirements guide for more.
What players report on launch day
- Uncapped frames: one reviewer saw about 1,200 FPS on first launch and advised lowering the frame rate and starting windowed.
- High refresh rates work: another reported running at their full 240 Hz monitor rate on Ultra.
- Noise and flicker: a reviewer said visuals looked noisy and flickering with effects at maximum.
- Cutscenes at 24 FPS: multiple reviewers noticed them and disliked it.
- Artifacts on some AMD setups: one reviewer with an RX 9070 XT saw cutscene artifacts and texture unloading, but not during gameplay.
- Weak spots: a Surface Pro ARM owner reported stuttering, and Unreal Engine crashes were reported at launch; see crash on launch.
These are individual reports, not benchmarks.
Blurry image and 25 FPS cutscenes
A Steam thread on this (14 replies within a few hours of launch) has several players saying the game looks lower resolution than expected and that fog and smoke look blurry or pixelated. One player at Ultra settings reported 144 FPS in gameplay but cutscenes capped near 25 FPS, and another said gameplay was locked to 60 FPS on Steam. Someone said the render looked like a lower resolution scaled up; one poster said the pixelation might be part of the art style. Two players said they tried editing the game’s .ini config and saw no change, and a third mentioned config tweaks going around but could not vouch for them. We could not confirm a fix or an official explanation as of Sep 29, 2026. If it bothers you, try the settings below first and send feedback.
Settings to try, in order
- Cap your frame rate. Set it to your monitor’s refresh rate (60, 144, 165, and so on) in the game if offered, otherwise in the driver’s control panel. This reduces heat and stutter.
- Turn on the highest sensible resolution for your GPU, then lower Effects first. If Effects at maximum cause flicker, drop one step.
- Lower Shadows if frames dip in crowded co-op fights.
- Use upscaling if the game offers it. We have not confirmed which upscalers the game supports.
- Run in borderless or windowed if alt-tabbing or the first launch misbehaves.
- Update your GPU driver and close overlays.
Windows-side tweaks that help any PC game
These are general Windows steps, not confirmed game-specific fixes:
- Pick the right GPU on laptops. In Settings > System > Display > Graphics, add the game and set it to High performance so it doesn’t run on integrated graphics.
- Use a performance power plan and plug in the laptop. Many stutters on portables come from power saving.
- Turn on Game Mode in Settings > Gaming, and close browsers with many tabs to free RAM. The game’s minimum is 8 GB.
- Enable variable refresh rate (G-Sync or FreeSync) if your monitor has it, then cap the frame rate a few frames below the maximum refresh rate.
- Watch temperatures. An uncapped launch can heat a laptop quickly, which is another reason to cap frames early.
Controls tip
The game plays best on a controller according to launch-day reviewers. Keyboard and mouse uses click-to-move, and many players are asking for WASD.
Co-op performance
Lag with four players is reported by some reviewers; a strong wired connection helps. See co-op and crossplay issues.
What we could not verify
Exact option names, default values, and whether the game has a built-in frame limiter. We’ll update this page after we’ve tested the PC build.
Individual results depend on your hardware; treat these as starting points, not guarantees.
FAQ
Why is the game running at 1,000+ FPS on my first launch?
One reviewer reported roughly 1,200 FPS on first launch with their CPU spinning up hard, and suggested lowering the frame rate and using windowed mode at first. Cap your frame rate to your monitor's refresh rate in the game, in the Nvidia/AMD control panel or with a limiter.
Why are cutscenes choppy?
Several reviewers and a Steam thread say cutscenes look capped at about 24 to 25 FPS even though gameplay runs at your full refresh rate. That looks like a design choice or limitation rather than your PC; see the blurry image section for related reports.
Does the game support WASD movement?
Players say no. Movement on PC is click-to-move with the mouse, or a controller. A controller is the recommended way to play.
Which settings should I lower first?
Effects, shadows and any resolution-scaling extras. One reviewer described noisy, flickering visuals with effects at maximum.