Sodium pushed 0.9.3-alpha.1 on 20 September, five days after its stable 26.3 build. Three fixes, one of which matters a great deal if you play on integrated Intel graphics and have spent the past week assuming your machine was the problem.
The three changes
- Graphical glitches on some Intel integrated GPUs, fixed. This is the one to act on. Intel iGPUs are the most common graphics hardware in the laptop population, and a rendering bug there affects a very large number of players.
- Fluid culling for non-full blocks with unusual shapes, fixed. Water and lava rendering incorrectly against blocks that are not full cubes – stairs, slabs, and the more awkward shapes the game has accumulated.
- macOS fullscreen menu visibility option, now shown on the Video Settings screen. The option existed; it was not exposed where anyone would find it.
That is a small release, and the small releases are where most of a renderer’s real work lands. Nobody writes a headline about fluid culling.
The alpha label, again
0.9.2 on 15 September was a stable release. 0.9.3-alpha.1 is not. The two exist side by side on the project page and the stable one has roughly sixty times the downloads, which is the correct ratio.
The question worth asking is whether the Intel fix is worth an alpha build. If you are seeing the glitches, yes – a rendering artefact that makes the game unpleasant to look at is worse than a build that might have a bug you have not hit. If you are not, wait for 0.9.3 proper.
That is the whole decision, and it is the same one every time a performance mod ships a targeted fix on the alpha channel.
Context: the Vulkan backend
Sodium 0.9.x introduced early Vulkan support alongside the existing OpenGL path, and the project has been clear that performance on the new backend is already good on many devices and expected to improve.
A new graphics backend is exactly the situation that produces vendor-specific bugs. Intel, AMD and Nvidia drivers implement the same specification differently, and code that works on two of them and not the third is the normal failure mode of the first year of any Vulkan implementation.
So an Intel iGPU fix arriving now is not a sign of trouble. It is the expected shape of the work, and it is the reason to keep the mod current rather than pinning a version and forgetting about it.
What to do if you see glitches
- Update Sodium first. Most rendering artefacts on 26.3 right now trace to the renderer rather than to your setup.
- If the artefact persists, switch backends in Video Settings and see whether it follows. A bug that appears on one backend and not the other is a Sodium issue worth reporting.
- Update your graphics driver. On an Intel iGPU in a laptop, the driver shipped by the manufacturer is frequently years old.
- Only then start removing other mods.
Step four last, always. Bisecting a mod folder is slow and it is rarely the answer for something that looks like a rendering fault rather than a crash.
Where it sits in the stack
Sodium is at roughly 228.7 million downloads and 40,800 followers, which makes it the most installed mod on Modrinth by a wide margin and the thing everything else in a client stack is built around.
It handles terrain rendering. Entity Culling handles entities you cannot see. Sodium Extra adds the settings Sodium deliberately leaves out. None of those overlap.
The order to install them is in the performance mod roundup.
Licence is Polyform Shield, which permits use and modification but restricts competing with the project. Not relevant to players; relevant to anyone forking it.
Bottom line
Take 0.9.3-alpha.1 if your screen looks wrong on Intel integrated graphics. Stay on 0.9.2 otherwise and pick up the fixes when the stable lands. Either way the rest of the 26.3 client stack is where it was.
Reading a Sodium version string
The naming is dense and worth decoding once. A build like mc26.3-0.9.3-alpha.1-fabric carries four things: the Minecraft version it targets, the Sodium version, the release channel and build number, and the loader.
The common installation mistake is grabbing a build for the right Sodium version and the wrong game version, which fails to load with a message that looks alarming and means nothing more than that. Always match the mc prefix to your client first and everything else second.
Why rendering bugs cluster on integrated graphics
Integrated GPUs share memory with the CPU, expose a narrower set of driver features, and are tested far less by graphics developers than discrete cards – not out of neglect, but because the developer’s own machine usually has a discrete card in it.
The result is that a rendering bug specific to integrated hardware often survives until enough users report it, which takes days rather than hours because the affected players are also the ones least likely to assume the mod is at fault. Someone playing on a laptop iGPU has spent years being told their hardware is the problem.
The practical lesson for anyone on that hardware: report it. A rendering artefact you assume is normal for your laptop is frequently a bug that nobody with a desktop has ever seen.
Images: Tectonic and Explorify project galleries.