Nvidium does not guarantee a specific FPS multiplier. Its main advantage appears when terrain rendering is CPU-limited, especially at larger render distances. A small improvement can be normal on a GPU-bound system, at low render distance, with active shaders, or in a world limited by entities and simulation.
Confirm supported hardware
Check that Minecraft is using an NVIDIA GTX 16-series/Turing-or-newer GPU with mesh-shader support. Laptops may launch Java on integrated graphics even when a compatible NVIDIA GPU is installed. Use operating-system graphics settings or the NVIDIA control panel to assign the launcher and Java process to the high-performance GPU.
Confirm the mod actually loaded
Verify that the selected profile contains one matching Sodium JAR and one matching Nvidium JAR. Read the latest log for dependency or mixin errors. A development ZIP package in the mods folder is not a loaded release. Fabric API should not be used as a generic fix unless another installed mod requires it.
Disable active shaders
Nvidium disables its accelerated renderer while Iris is actively using shaders. Turn the shader pack off and restart before measuring Nvidium. Comparing shader-on performance with shader-off performance measures two very different pipelines.
Use a controlled benchmark
- Use the same world, location, resolution and render distance.
- Wait for nearby chunks to finish loading.
- Compare Sodium-only against Sodium plus Nvidium.
- Measure frame-time consistency as well as average FPS.
- Repeat the route instead of relying on one momentary counter.
Check the real bottleneck
Lower GPU resolution or effects temporarily. If FPS rises sharply, the GPU is already the limit and moving more terrain work to it may not help. If performance collapses around many entities, redstone or world generation, the bottleneck may be simulation rather than terrain culling.
Watch VRAM and render-distance settings
Very large render distances keep more terrain data available and can pressure VRAM. Reduce render distance, close GPU-heavy applications and avoid extreme settings that cause memory paging. A stable lower setting usually feels better than a higher average FPS with repeated stalls.
Test mod conflicts
Create a clean instance with only the loader, matching Sodium and Nvidium. If performance improves, add other rendering, entity, chunk and replay mods back in small groups. Keep versions documented so a successful combination can be restored.
Update carefully
Use a current official NVIDIA driver, but change one variable at a time. Updating Minecraft, Sodium, Nvidium, loader and driver together makes the cause of a regression difficult to identify. Check the selected build metadata and known issue notes for version-specific problems.
Collect useful diagnostics
Before opening an issue, record the exact Minecraft, loader, Sodium and Nvidium versions; GPU model; driver version; operating system; render distance; shader state; and a link to the relevant log. Explain whether the issue also occurs with Sodium alone. Specific comparisons help maintainers distinguish a Nvidium regression from a general modpack or hardware bottleneck.
Restore a known-good baseline
If several changes were made at once, return to the last stable profile and update one component at a time. Keep copies of working JAR versions and configuration files. A controlled rollback is faster than repeatedly changing random settings and gives a clear point from which to identify the first version that introduced the slowdown.
Separate loading stutter from steady FPS
Chunk generation and first-time loading can produce temporary pauses that are not the same as steady rendering performance. Repeat the same route after terrain is cached, then compare the second run. This helps distinguish generation work from the terrain-rendering bottleneck Nvidium is designed to reduce.
