Mod conflicts

ValidationGpuDevice Cannot Be Cast to GlDevice (NeoForge & Iris)

What it looks like in the log

java.lang.ClassCastException: class net.neoforged.neoforge.client.blaze3d.validation.ValidationGpuDevice cannot be cast to class com.mojang.blaze3d.op

How to fix it

  1. Close Minecraft and open your instance's Minecraft folder (or 'run' folder if you are in a mod development environment).
  2. Open the 'config' folder and locate the 'neoforge-client.toml' file.
  3. Open 'neoforge-client.toml' in a text editor and find the Blaze3D GPU validation layer setting.
  4. Set the validation layer option to 'false', save the file, and relaunch the game.
LoadersNeoforge
SeverityStops the game
CategoryMod conflicts

Check your own logDownload neoforge on 9Minecraft

Related errors

Mod conflictsAE2 Crash Viewing Unnamed Cable Tooltip When Channels Are DisabledUpdate Applied Energistics 2 to the latest `rv3` release for Minecraft 1.7.10, which updates recipes automaticMod conflictsCrash on World Load: class_5944.method_34583 NullPointerException (Iris & Rendering Mod Conflict)Remove or disable Immersive Portals from your `mods` folder if it is installed alongside Iris Shaders, as its Mod conflictsInsecureTextureException: Signature is missing from textures payloadUpdate or remove 3D Skin Layers (skinlayers3d) from your mods folder, as older builds crash when encountering Mod conflictsIris Shaders and Distant Horizons Blaze3D Rendering API CrashOpen your Minecraft instance folder and go into the config directory.Mod conflictsOptiFabric Crash: "resourceName" is null During Shader ReloadUpdate both OptiFabric and Fabric API to the latest builds for your Minecraft version, as newer OptiFabric relMod conflictsSodium Crash: "centroid" is null in DynamicTopoData Translucent SortingDisable shaders before joining the world or Realm: open Options -> Video Settings -> Shader Packs from the mai