News: 0001623453

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

RadeonSI Driver Lands Fixes For EDuke32 For Those Wanting To Enjoy Duke Nukem 3D In 2026

([Radeon] 6 Hours Ago EDuke32)


It's fairly rare for the RadeonSI Gallium3D driver to hit OpenGL rendering game bugs these days as besides more games going opting for Vulkan API use, RadeonSI is rather robust and very mature at this stage. Recently though a Linux gamer that upgraded to a Radeon RX 9070 XT RDNA4 graphics card noticed that the open-source EDuke32 Duke Nukem 3D build and its derivatives were failing to render properly with the RadeonSI driver.

A week ago there was [1]a bug report over EDuke32 and its derivatives like Ion Fury were failing to properly render textures/sprites on the RDNA4 graphics card. The vintage games would render fine if falling back to the software rendering rather than OpenGL. Here's some examples of the faulty rendering on RDNA4 with RadeonSI:

It was discovered that the EDuke32 issue dealt with the engine allocating very large textures. Well known RadeonSI developer Marek Olšák of AMD in turn merged a change for [2]using uint16 for coordinates to fix 64K blits and [3]64K graphics blit support and other fixes. With the latest Mesa code, EDuke32 and titles based on it should be rendering correctly on RDNA4 graphics hardware.

Even if you aren't into Duke Nukem 3D or other such titles, these 64K texture fixes should help other software too on AMD RDNA4. A bug report over [4]disappearing Blender icons , also on RDNA4, appear fixed by these RadeonSI changes too.



[1] https://gitlab.freedesktop.org/mesa/mesa/-/work_items/15101

[2] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40565

[3] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40634

[4] https://gitlab.freedesktop.org/mesa/mesa/-/work_items/15125



"Don't drop acid, take it pass-fail!"
-- Bryan Michael Wendt