Mesa 26.1.0-rc3 arrives as a quiet stability patch that fixes actual driver headaches instead of chasing flashy new features. The release corrects HEVC decode misreads, brings back RADV multiview support for vkd3d-proton users, and patches Intel shader precompilation along with a lingering NIR floating-point math bug. Anyone planning to test the build should download the official tarball and verify the checksums before compiling, since graphics stack glitches can easily break desktop sessions or game launches. The final version drops next week after one more candidate window closes out any remaining critical issues.

Mesa 26.1.0-rc3 Drops Video Decoding Fixes and RADV Multiview Support

The third release candidate for Mesa 26.1.0 lands with a solid batch of driver patches that actually matter to people running Linux desktops or gaming rigs. Readers will get the straight facts on what changed, which GPU vendors see real improvements, and how to grab the build before the final version ships next week.

Driver Updates and Stability Fixes

The patch set leans heavily on stability tweaks rather than flashy new features, which is exactly what you want from a release candidate. A few standout changes include a fix for HEVC decode that stops the driver from misreading picture order counts, and a re-introduction of DGC plus multiview support in RADV that only activates when running through vkd3d-proton. That last one matters because many Windows games ported to Linux rely on those exact flags to avoid stuttering during heavy frame pacing. Intel users will also notice shader precompilation getting patched for Gen6 hardware and newer, which usually means fewer random crashes in older integrated graphics setups. The NIR optimization pass finally corrects an exactness bug that could mess up floating point math in certain shaders, so visual artifacts should drop across the board. It is fairly common to watch desktop environments freeze after a rushed graphics stack update, and Mesa is no exception since it touches everything from display servers to Vulkan layers.

Installation Notes

Downloading the source tarball is straightforward since the project hosts everything on their official server with full checksums and a PGP signature attached. Users should always verify the SHA256 hash before compiling because even minor corruption during download can break the build process or leave the system in an unstable state.

SHA256: c9e8d8a3f9bd1244267ccd4f2f33c91dc17e65e2686b3ec4469744c1374354f2 mesa-26.1.0-rc3.tar.xz
SHA512: b49503159f82dbef6eeb52eb765a366b27809da803af0e3c1b5ad44fd586387a07398e18a16592240c6cd470ed2ae7510ab922684496b680e94da27296f0e181 mesa-26.1.0-rc3.tar.xz

The archive unpacks into a standard directory structure where running configure followed by make will handle the heavy lifting. Those who prefer not to compile from scratch can usually find prebuilt packages through their distribution testing repositories or third-party PPA channels, though those builds sometimes lag behind upstream commits by a few days. Release candidates are not meant for daily drivers unless someone actually enjoys debugging driver crashes at two in the morning. Anyone testing this build should keep a fallback kernel or live USB handy just in case the DRM subsystem decides to misbehave during boot. The project expects another candidate by May sixth, so there is still time for critical bugs to surface before the final version locks down.

Grab the build if you want early access to these fixes, but keep an eye on the issue tracker if something acts up. The Mesa team usually squashes the remaining kinks quickly once the final version gets the green light. Happy compiling and may your frame times stay smooth.