How to Configure the Graphics of an MMO or Survival Game, Step by Step

Configuring the graphics of a big-world game is a job of method, not guessing. The rule: only the settings that move your bottleneck work. If the GPU limits you, lowering population changes nothing; if the CPU limits you, lowering the resolution does not either. This guide gives a nine-step recipe and a table of what loads each component, written for MMOs and survival games but valid for almost any game.

Before you start

• Up-to-date drivers, the graphics one and the chipset one.
• Display at its native resolution and maximum refresh rate in Windows settings.
• Display mode: fullscreen or borderless. Borderless makes window switching comfortable; fullscreen can give slightly lower latency in some games.
• Variable sync (G-Sync or FreeSync) on if your display has it (guide).
• A measuring tool: an overlay with frame rate, frame time, GPU usage and per-thread CPU usage. More in how to measure your PC’s performance.

The nine steps

1. Start from a High preset, not Ultra or Low. It is where the ratio of quality to cost is usually best.
2. Choose the worst scene: the busiest area you will play (a crowded city, a big base, a battle). If you tune in an empty landscape, the settings will fall short when it matters.
3. Measure at your native resolution: average frame rate, 1 % low and GPU usage. That is your starting point.
4. Identify your limit with the resolution test (CPU-bound versus GPU-bound).
5. If the GPU limits you, start by enabling an upscaler (DLSS, FSR, XeSS or the engine’s own) in Quality mode, then lower shadows, global illumination and volumetric effects one level.
6. If the CPU limits you, lower population or character density, object draw distance, distant shadows and vegetation. Do not lower the resolution.
7. Change one setting at a time and measure again in the same spot. If frame time does not drop, undo the change.
8. Match textures to your VRAM, not to your GPU: raise the quality until video memory use approaches 80-90 % of your card’s, and no further.
9. Set a frame limit a little below what the PC sustains, or at the display’s rate, and save the profile.

What each setting loads

Setting	Loads	Impact on frame rate	What to do
Internal resolution / upscaler	GPU	Very high	First lever if the GPU limits you; Quality mode before lowering resolution
Shadows (quality)	GPU and CPU	High	Lower one level; keep the sun shadow sharp
Shadows (distance)	CPU	Medium-high	Reducing it helps a CPU-limited PC
Global illumination	GPU	High	Lower a level before turning it off
Volumetrics (clouds, fog)	GPU	High at altitude or with weather	Lower quality before removing them
Reflections and ray tracing	GPU	High	Turn off or lower them if you want frames
Population / character density	CPU	High in crowded scenes	First lever if the CPU limits you
Object draw distance	CPU	Medium-high	Lower density before distance
Vegetation and terrain detail	CPU and GPU	Medium	Reduce density
Textures	VRAM	Low on frame rate	Match to your card’s memory
Anisotropic filtering	GPU	Very low	Leave it high (16x)
Ambient occlusion	GPU	Low-medium	Raising costs little, lowering saves little
Post-processing (blur, grain, aberration)	GPU	Low	Personal taste; turning them off often improves sharpness
Anti-aliasing	GPU	Medium	A good temporal method or DLAA is worth it
Frame generation	GPU	Raises displayed frames	Only with a stable base; adds latency (guide)

The impact figures are qualitative and change from game to game. For engines with Lumen, Epic itself budgets about 4 ms per frame for 60 fps on console, and dropping one quality level cuts its cost roughly in half; we cover it in more detail in our guide to optimizing Unreal Engine 5 games.

Three starting profiles

Profile	Starting point	Settings
GPU-limited, 1440p display	High	Upscaler on Quality, shadows on Medium-High, volumetrics on Medium
CPU-limited in crowded zones	High	Population and draw distance on Medium; native resolution; distant shadows on Medium
Tight VRAM (8 GB)	Medium-High	Textures on Medium, upscaler on Quality, lower internal resolution

Common mistakes

• Lowering everything “just in case”: you lose quality and gain nothing if the setting was not your limit.
• Tuning in an easy scene and later finding that the crowded zone performs much worse.
• Confusing the average with smoothness: look at the 1 % and 0.1 % lows (frames per second and milliseconds).
• Enabling frame generation on an unstable base: it multiplies the problems instead of fixing them.
• Forgetting the frame limit: a PC running flat out with no cap heats more and gives less regular frames.

A worked example, with no invented figures

Imagine a player with a 12 GB graphics card and a mid-range processor who, in the busiest city, sees a low frame rate with the Ultra preset at 1440p. Follow the recipe:

1. Switch to High. The improvement is usually immediate, with little visible loss.
2. Measure with the resolution test. The GPU is at 98 %: it is GPU-bound.
3. Enable the upscaler in Quality mode and lower shadows one level. The GPU drops from its maximum and the frame rate rises.
4. Measure again: now the GPU sits at 80 % and one CPU thread is near 100 %. The limit has moved to the CPU, which is to be expected.
5. For that last stretch, lower population one level. If frame time improves, keep it; if not, raise it again, because it was not your limit.

The result is not “the best setting”; it is the setting that costs the least visual quality for the limit you have. Each PC will reach a different profile with the same recipe.

When to review again

A configuration is not forever. Repeat the resolution test after updating the graphics drivers, after a big game patch, after changing display or resolution, and after changing a part of the PC. Save one profile per situation (for example, one for crowded zones and one for exploring) if the game allows it.

And in COLONIZED

COLONIZED is a space survival MMO built with Unreal Engine 5 (closed alpha applications open, first waves planned for winter 2026-2027, not yet playable). The final settings have not been announced, and this guide is general, but the logic is the one we apply when optimizing the development build: measure in pairs and change one thing at a time. We have not published system requirements or frame rate figures.