Go to Home Page Complementary Shaders logo
Download

Complementary Broken? Start Here

Complementary problems usually fall into a few buckets: loader conflicts, wrong folders, overly high presets, or outdated ZIPs.

Match the symptom on this checklist, then open the linked guide. Do not reinstall Minecraft first.

Quick checks for every issue

  1. Confirm you are on Java Edition with Iris or OptiFine loaded.
  2. Confirm the Complementary ZIP sits in shaderpacks.
  3. Disable other shader packs and heavy visual mods temporarily.
  4. Drop to Potato or Low and test a new world.
  5. Update GPU drivers when compile errors persist.
  6. Remove OptiFine from Iris instances and the reverse.

Symptom guides

Black screen

World loads but view stays black or pink.

Black screen guide

FPS collapse

Playable vanilla, unplayable with shaders.

FPS boost guide

Update problems

Broken looks after a version jump.

Safe update guide

Options confusion

Not sure which toggle caused pain.

Options guide

Wrong or old ZIP

Pack name missing, compile fails after an update, or a modpack needs a pin.

Versions and archives

Version and download recovery

Many “shader is broken” reports are simply a bad download, an extracted ZIP, or a mismatched archive. Redownload from the download page, keep the file zipped, and confirm the label against the versions page.

If the failure started right after an update, compare notes on the changelog and roll back one build while you test.

Still stuck

Re-read install steps and requirements. If you need site help about broken links or content errors, use the contact page.

Symptom map

Black or pink world

Compile failure, conflict, or heavy preset.

Black screen guide

Low FPS

Profile and effect cost, not always a bad ZIP.

FPS boost guide

Missing pack in list

Wrong folder or loader not running.

Install guide

Broke after updating

Keep a rollback and test in a copy world.

Safe update guide

Build a clean test profile

Create a fresh Fabric profile with Iris, Sodium, and one Complementary ZIP only. If that works, add mods back in batches. This isolates pack conflicts faster than guessing.

Still stuck after a clean profile? Confirm Java vs Bedrock on the Bedrock page, then redownload from the download page.

Common questions

Wrong folder, extracted pack, or loader not active.
Often a compile failure or conflicting mod. Follow the black screen guide.
Complementary Shaders are Java only. See the Bedrock page.
Almost never as a first step. Disable shaders, switch to Potato, or repair the loader stack first.

Keep reading