Platforms

Mandate Order Performance Guide – FPS, Lag, Stutter & Graphics Settings

Quick answer

Mandate Order performance guide for Early Access: FPS, lag, stutter, blurry graphics, DLSS, anti-aliasing, CPU load, GPU settings, and how to improve large-battle performance without inventing benchmarks.

Review record
Published: Last reviewed: Patch-sensitive facts are marked for recheck

Mandate Order Performance Guide

This page covers Mandate Order FPS, lag, stutter, graphics settings, DLSS, anti-aliasing, and low performance as a separate search intent from system requirements. The System Requirements page answers “Can I run it?” This page answers “Why does it run badly, and what should I try?”

Because the Early Access build is still changing, this guide avoids invented benchmark numbers. Use it as a practical settings and diagnosis checklist.

Official Requirements Baseline

Steam lists the minimum GPU tier as GTX 1660 6GB, RX 5600 XT 6GB, or Arc A750, with 16GB RAM and an i7-9700 or Ryzen 5 3600. Recommended hardware moves up to RTX 3070 or RX 6800, with an i7-12700K or Ryzen 7 5800X.

That jump suggests two important things:

  • Large cities and battles can be CPU-sensitive.
  • Higher visual settings and resolution can become GPU-sensitive.

First Settings to Lower

Setting areaWhy it helpsBest first move
ShadowsExpensive in large scenesLower one or two steps
View distance / object detailReduces city and battle draw costLower before texture quality
EffectsBattles and weather can stack effectsLower during siege-heavy runs
Anti-aliasingCan affect clarity and GPU loadTest alternatives if the image looks blurry
Resolution scale / upscalingDirect GPU reliefUse carefully to avoid blur

Low FPS in Large Battles

Large real-time battles stress formation logic, pathfinding, unit animation, combat effects, and rendering at the same time. If FPS drops mainly during battles:

  1. Lower shadows and effects first.
  2. Reduce view distance or object detail.
  3. Close overlays and recording software.
  4. Update GPU drivers.
  5. Avoid stacking huge battles beside the busiest production district when testing performance.

Stutter in City View

City stutter can be caused by pathfinding, production tasks, storage movement, or rendering many buildings and workers. If stutter appears after your settlement grows, test whether it happens while paused, during harvest, during recruitment, or when many routes are active.

Blurry Graphics or Anti-Aliasing

If Mandate Order looks blurry, check resolution scale, upscaling, anti-aliasing mode, motion blur, and display resolution. Do not assume blur means your GPU is too weak. It can also be a settings combination.

DLSS and Upscaling

If DLSS or another upscaler is available in your build, treat it as a tradeoff: it can improve performance, but aggressive modes may soften the image. Start with a quality-focused mode, then move lower only if FPS still feels unstable.

What Not to Do

  • Do not trust random FPS promises without hardware, settings, resolution, map size, and battle size.
  • Do not confuse “meets minimum requirements” with “high settings in large battles.”
  • Do not change every setting at once. Change one cluster, test, then continue.

FAQ

Is Mandate Order CPU or GPU heavy?

It can be both. City simulation, workers, logistics, and large battles can stress the CPU, while high resolution, shadows, effects, and large scenes stress the GPU.

Can a GTX 1660 run Mandate Order?

GTX 1660 6GB is listed as a minimum-class GPU on Steam. That means it should target modest settings, not guaranteed high settings in every large battle.

Should I use DLSS?

Use DLSS or upscaling if your build supports it and GPU load is the problem. If the image becomes blurry, move to a higher-quality mode or adjust anti-aliasing.

Is this the same as the system requirements page?

No. System Requirements covers hardware specs. This page covers FPS, lag, stutter, graphics settings, and practical troubleshooting.