How to Fix Broken Lighting, Shadows and Water Reflections

The pack loads, the world renders, but something is visibly wrong: shadows crawl or flicker, water sits dead and flat, light looks washed out or banded, reflections are missing or mirrored nonsense. Rendering faults like these sit between "works" and "broken", and they have their own short list of causes. Work through them in this order.

Step 0: Establish what "wrong" means

Before changing anything, separate three possibilities:

• It looks wrong compared to vanilla expectations, but it may be the style working as designed. Unbound's dark nights and Reimagined's bright days have both been reported as "bugs" by players expecting the other style. Compare against the descriptions in the style comparison first.
• It looks wrong compared to yesterday, something changed. That change is your investigation.
• It looks wrong in one place or time, a scene-specific artefact (a particular biome, sunset, or underground), which narrows causes considerably.

Cause 1: A settings combination, not a bug

The most fixable cause. Shadow shimmer and crawling come from shadow resolution spread too thin over shadow distance, raise resolution or reduce distance until the map's detail matches its coverage (shadow settings). Dead water is usually reflections minimised by a low profile or an earlier experiment. Washed-out scenes are often brightness/fill pushed too far. The universal test: switch to a stock profile (no overrides). If the artefact vanishes, it was settings, re-apply yours one at a time and you will meet the culprit personally.

Cause 2: Loader-side rendering options

Loaders carry their own rendering switches, and some fight the pack. In OptiFine, performance options such as Fast Render have historically conflicted with shader rendering, if effects are missing or the image is subtly wrong, return OptiFine's performance and quality pages to defaults and re-test (OptiFine guide). In Iris, check that no per-pack overrides or debug options were left on. Vanilla video settings matter too: the game's own graphics mode and render pipeline options should be at their standard settings while you diagnose.

Cause 3: A resource pack in the fight

Resource packs that recolour water, replace sky textures, or include their own lighting data (PBR-style packs designed for specific other shaders) can produce results that look like shader faults: wrong water colour, double skies, glowing blocks that should not glow. Test with resource packs disabled. If you intentionally use a PBR/labPBR-style pack, know that such packs are built to pair with particular shader support, mismatched pairings give plausible-but-wrong images, the hardest kind to diagnose.

Cause 4: Another rendering mod

Sky replacers, water overhauls, lighting mods, renderer replacements: anything that touches the same pixels negotiates with the pack, and some negotiations fail quietly as artefacts instead of crashes. Isolate by halves as in the triage guide. Performance mods from the Sodium family are designed to cooperate with Iris; unknown "optimisers" are the repeat offenders.

Cause 5: Driver-level artefacts

Banding, corruption patterns, or artefacts that also appear in screenshots from other games point below the game entirely: the driver. Update from the GPU maker's distribution; if the artefact arrived with a driver update, roll back one version as a diagnostic. Background and checks: GPU and driver compatibility.

If it survives all five causes

You may have found a genuine pack bug, they exist, and the project's small post-release revisions (r5.9 → r5.9.3 within two weeks) exist because of reports. Confirm you are on the current release, reproduce the artefact from a stock profile in a clean setup, and note the scene, time of day, versions and GPU. A report with those facts is how real bugs get fixed.

Check the artefact by dimension, time, and place

Before you conclude that lighting or shadows are broken everywhere, test the same stock profile in deliberately different scenes and write down where the artefact appears. Compare midday and sunset in the Overworld, an open plain and a dense forest, the surface and a cave, and then the Nether and the End if you play in them. An artefact that follows you into every dimension and every time of day belongs to the shared setup: loader options, a carried settings combination, a resource pack, or the driver. An artefact that exists in only one dimension, or only underground, or only around water, has a narrower cause, often a mod or resource pack that contributes content for that one context, or a single setting whose effect is only visible there. Sunset-only problems deserve particular care, because long shadows and low sun angles expose shadow resolution and distance limits that are invisible at noon; that is a tuning signal, not automatically a fault.

Single-player and server comparisons help in the same way. Reproduce the scene as closely as you can in a local world on the stock profile. If the artefact is absent locally but present on a server, consider what the server adds, its own resource pack is the first suspect, since a pack that recolours water, replaces sky textures, or carries its own lighting data will change the picture without changing your shader at all. If the artefact is identical locally and on the server, the server is ruled out and your own five causes remain. Whichever comparison you run, change the scene or the context, not your settings, between the two tests; otherwise you will not know which difference explained the result.

If several fixes have already been tried: return in order

Rendering artefacts invite scattered tweaking, and after an hour of it nobody, including you, knows which combination is currently active. When that happens, stop and rebuild the picture in a set order. Move the settings .txt file named after the pack ZIP aside so Complementary starts from defaults, disable resource packs, and return the loader's own options to defaults: for OptiFine that includes its performance and quality pages, and for Iris it means checking that no per-pack overrides were left on. Confirm the pack itself is the current release, r5.9.3, still zipped and selected in Video Settings → Shaders. View the test scenes from the previous section on that clean basis and judge honestly whether the artefact is still present.

If the clean picture is correct, restore your own choices one at a time, in an order you write down: your quality profile first, then individual overrides, then resource packs, then any rendering-adjacent mods in halves. The step that brings the artefact back has identified itself, and you can decide whether that setting, pack, or mod is worth keeping with a compromise elsewhere. If the clean picture is still wrong, note the exact scene, dimension, time of day, biome or structure, and what in the frame is wrong, along with your Minecraft, loader, and pack versions and the GPU shown on the F3 screen. Check whether the same artefact appears in other games or only here, which separates a driver-level problem from a game-level one. A support report carrying that scene description and those versions is far more actionable than a screenshot alone, because it lets someone else stand in the same place, at the same time, on the same profile and see whether they get the same result.

Frequently asked questions