Crash Diagnostics: Sodium & OptiFine Mixin Conflict

Fabric / Forge / NeoForge

Pre-loaded crash report example showing exact error lines and troubleshooting steps.

Render Mod Mixin Conflict (OptiFine is incompatible with Sodium / Embeddium / Iris)

Both OptiFine and Sodium/Embeddium are installed and attempting to patch WorldRenderer.

Matched error signature in log:
Caused by: org.spongepowered.asm.mixin.throwables.MixinApplyError: Mixin [sodium.mixins.json:features.chunk_rendering.MixinWorldRenderer] from phase [DEFAULT] in config [sodium.mixins.json] FAILED during APPLY
Troubleshooting steps:
  1. Remove the OptiFine .jar file from your mods folder.
  2. Use Iris Shaders (Fabric) or Oculus (Forge) for shaders.

Questions & reference

How do I fix: Render Mod Mixin Conflict (OptiFine is incompatible with Sodium / Embeddium / Iris)?

Both OptiFine and Sodium/Embeddium are installed and attempting to patch WorldRenderer. Remove the OptiFine .jar file from your mods folder. Use Iris Shaders (Fabric) or Oculus (Forge) for shaders.

Where do I find my Minecraft error log?

Open your game profile folder. Copy a file from crash-reports or logs/latest.log. Exit Code 1 alone does not explain the crash.

Where is my log sent?

Analysis runs in your browser. Your log is not uploaded to DEPTANA, stored in settings, or included in a shared URL. The text limit is two million characters.

Does a match prove the cause?

Diagnostics checks known error signatures. A match suggests what to inspect; it does not prove the sole cause. If no rule matches, the tool says so.