Nvidium and Iris can be installed in the same Minecraft profile, but they do not provide their main rendering features simultaneously. The official Nvidium project states that Nvidium disables its accelerated renderer while Iris is actively using shaders.
This distinction matters: “the game launches with both mods installed” does not mean Nvidium is accelerating terrain while a shader pack is enabled.
What happens when shaders are enabled
When Iris activates a shader pack, Nvidium turns off its GPU-driven terrain backend so the compatible Sodium/Iris rendering path can be used. The shader pack may work normally, but Nvidium's mesh-shader performance benefit is not active during that session.
What happens when shaders are disabled
With Iris still installed but no shader pack actively enabled, a compatible Nvidium build can use its renderer again. Restarting the game may be helpful after changing major rendering settings, especially when diagnosing a visual problem or confirming which backend is active.
A practical profile strategy
For predictable testing, create two launcher profiles. Use one profile for Sodium plus Nvidium without active shaders, and another for Sodium plus Iris and shader packs. Separate profiles make version changes easier to manage and prevent assumptions about which renderer is active.
Troubleshooting visual issues
- Disable the shader pack and restart before testing Nvidium.
- Confirm Nvidium, Sodium and Iris versions support the same Minecraft release.
- Remove duplicate or outdated rendering JARs.
- Test with a minimal mod list to isolate pipeline conflicts.
- Update the NVIDIA driver from an official source.
- Check the latest log for an explicit compatibility or mixin error.
Performance expectations
Shader packs can shift the bottleneck heavily toward the GPU. Even without Nvidium active, shader performance depends on resolution, shadow quality, volumetric effects and the shader pack itself. Compare shader-on performance against the same shader settings, not against a shader-off Nvidium test.
The accurate compatibility summary
Nvidium and Iris may coexist as installed mods, but active Iris shaders disable Nvidium's accelerated terrain path. There is no configuration that should be advertised as “Nvidium performance plus active Iris shaders” unless the project behavior changes that behavior in a future release. Recheck the current compatibility notes after major Nvidium, Sodium or Iris updates.
How to compare two profiles fairly
Use the same world, camera route, resolution and non-shader video settings. In the Nvidium profile, keep shaders inactive. In the Iris profile, use one fixed shader preset. Record both average FPS and visible frame-time spikes, but do not describe the result as a direct Nvidium-versus-shader benchmark because the renderers and visual workload are different.
When both mods may still be convenient
Keeping Iris installed can be useful for players who switch between performance-focused gameplay and shader screenshots. The important point is to understand the active mode: shader off allows a compatible Nvidium path; shader on prioritizes the Iris shader pipeline and disables Nvidium's accelerated backend.
Check status after updates
Shader and renderer compatibility can change when Minecraft, Sodium, Iris or Nvidium updates. After any major version change, review the current compatibility notes and release details, then retest both profiles. Do not carry an old workaround forward automatically when the underlying compatibility behavior may have changed.
Use clear language in modpack notes
When documenting a pack, say that both mods are installed but Nvidium is inactive while shaders are enabled. Avoid labels such as “fully compatible” when readers may interpret them as simultaneous acceleration. Clear wording prevents misleading performance expectations and unnecessary bug reports.
