PERFORMANCE & FPS

How Render Distance Affects Complementary Shaders Performance

Illustration for: How Render Distance Affects Complementary Shaders Performance

Of all the dials that decide how Complementary Shaders performs, render distance is the heaviest, because it does not add a cost, it multiplies every other cost. More chunks means more terrain to draw, more shadow map to fill, more water to reflect and more sky to meet at the horizon. This guide explains how render distance interacts with the pack, how it differs from simulation distance, and how to find the setting your machine can honestly sustain.

Why distance multiplies shader cost

Doubling render distance roughly quadruples the visible terrain (the area grows with the square of the radius). Every one of those chunks must be lit by the pack's lighting model; the ones within shadow distance join the shadow render; water among them joins the reflection render. A shader pack therefore feels render distance far more than vanilla does, a distance that was free in vanilla can be the entire performance problem with shaders on. This is why "the pack is slow" so often means "the pack is being asked to shade a small country".

Render distance is not simulation distance

  • Render distance (client): how far you see. This is the performance dial in this article.
  • Simulation distance (world/server): how far the game simulates, crops grow, mobs move, redstone ticks. It costs CPU, not GPU, and the shader neither knows nor cares about it.

Confusing the two leads to pointless sacrifices: lowering simulation distance will not fix shader frame rates, and lowering render distance will not stop your farms, it just means you watch them from closer.

The interactions that matter

  • With shadow distance: shadows only render within their own distance cap, which is usually shorter than render distance. Raising render distance alone does not extend shadows, one reason distant terrain can look flatter, and a hint that shadow distance, not render distance, may be your real lever (shadow settings).
  • With fog: fog is the curtain at the edge of the world. At short distances, slightly denser fog disguises the cutoff so well that many players prefer the look and the frame rate. Tune them together (atmosphere settings).
  • With reflections: water reflects what is rendered. Long distances over ocean are the most expensive common scene in the game with shaders on.

Finding your distance

  1. Start from your current distance. In an open vista scene, note the settled frame rate.
  2. Reduce by two chunks. Re-test the same scene, same view.
  3. Repeat until the frame rate is comfortably where you want it, then, if you have headroom, try adding one chunk back.
  4. Check your busiest scene (base, farms) at the chosen distance; it, not the vista, is the real exam.
  5. Adjust fog so the horizon reads naturally at the final distance.

Typical outcomes (as orientation, not promises): weak hardware settles around 6–8 chunks with the Potato profile; mid-range machines live happily at 10–14; high-end systems push further, especially over land. The method that verifies your own numbers is the performance optimisation guide.

A note on servers

On multiplayer servers, your effective view is capped by the server's view distance no matter what your client requests. If your frames are fine but the world ends abruptly, that is the server's setting, not a shader fault, and lowering your client distance to match the server's cap can reclaim performance you were spending on nothing.

Distance over a long session: heat, travel, and chunk flow

A distance that tests well in a five-minute check can behave differently across an evening. Travelling, especially fast travel by elytra, boat, or horse, keeps chunk loading continuous, and every newly arrived chunk must be lit, shadowed where applicable, and reflected where water is present. A setting that is comfortable while standing at base may therefore strain while exploring, which is why the finding-your-distance steps should include a travel test, not only static scenes. Heat adds a second drift: laptops in particular may sustain a demanding distance early in a session and throttle later, so a borderline setting feels like it "got worse" when the machine, not the world, changed. If that pattern sounds familiar, choose the distance that still feels even in the last half hour of play, plugged in with vents unobstructed, rather than the distance that impressed you in the first five minutes.

Screen size changes what a distance feels like

Render distance is judged on a screen, and screens differ. On a large monitor viewed up close, the edge of the world occupies more of your vision, fog transitions are easier to scrutinise, and a short distance can feel shorter than the same setting on a laptop across a desk. On a smaller display, or when playing further from the screen, the horizon sits in a narrower part of your view and a modest distance with well-tuned fog often reads as generous. Resolution interacts here too: a high-resolution display renders the cutoff and distant terrain more crisply, which can make pop-in at the edge more noticeable even though the underlying distance is unchanged. None of this changes the cost maths, visible area still grows with the square of the radius, but it explains why two players on similar hardware defend different "perfect" distances, and why advice should always be re-tested on your own desk rather than adopted whole.

Revisit distance when your world grows

Render distance is often set on the first day in a world and never reconsidered, yet the world it must draw does not stay still. A starter plain becomes a base with storage, farms, lighting, and entity-heavy builds; a coastline develops docks and beacons over the very water that makes reflections expensive. When a familiar area starts to feel heavier, the correct first question is not whether the pack changed but whether the scene did, and whether the distance chosen for an empty landscape is still the distance this landscape can afford. Lowering it by a chunk or two as a world matures, with fog adjusted to suit, is normal maintenance rather than defeat. The same applies in reverse after a move: a fresh, lighter area may honestly sustain a longer view, and raising distance there, tested by the method in the performance optimisation guide, is a legitimate reward rather than a risk.

Frequently asked questions

Why did halving render distance double my FPS?

Because the visible area fell to roughly a quarter. Distance is quadratic, which is why it out-leverages every per-effect setting, see increase FPS.

Does render distance affect how the pack looks up close?

Only indirectly: a distance your GPU can afford leaves budget for higher shadow and reflection quality nearby, which usually looks better than distant terrain rendered cheaply.

What is the "best" render distance for Complementary?

The highest one your machine sustains smoothly in your busiest scene, with fog tuned to suit it. There is no universal number, and anyone selling one has not seen your world.