News: 0001488240

  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)

Mesa's Gallium3D Direct3D 9 "Nine" State Tracker To Be Retired

([Mesa] 6 Hours Ago Gallium Nine)


It's crazy that [1]Gallium Nine is already a decade old for providing a Direct3D 9 (D3D9) state tracker implementation for Gallium3D hardware drivers. Gallium Nine was useful years ago for speeding up Direct3D 9 support when using Wine on Linux for Windows games/applications but it hasn't been well maintained in years with DXVK pretty much taking over for efficiently mapping Direct3D atop the Vulkan API. It's time to sunset Gallium Nine.

In the early years and well before Vulkan came onto the scene, [2]Gallium Nine allowed for better performance of D3D9 games on Wine. This was also a time at which Valve's Steam Play (Proton) didn't even exist yet. But with time the Nine state tracker has become less relevant. Gallium3D Nine developer Axel Davy recently announced his intention to ending Gallium Nine. It hasn't been well maintained in years, there aren't many users left, and "DXVK just works" well these days. Plus there aren't too many Linux enthusiasts/gamers all focused on D3D9 these days compared to the more recent versions of Direct3D that are also supported by DXVK. Plus DXVK going the Vulkan API route works on more drivers than just the Mesa Gallium3D drivers.

Thus as Axel [3]announced , it's the end of the road for Gallium Nine. The pull request for removing Gallium Nine from the Mesa codebase is expected to be submitted soon.



[1] https://www.phoronix.com/search/Gallium+Nine

[2] https://www.phoronix.com/news/MTgxNzU

[3] https://lists.freedesktop.org/archives/mesa-dev/2024-August/226299.html



Alexmitter

ridge

ahrs

davidbepo

lorn10

GeneralZod

mxan

dragorth

aviallon

=== ALL USERS PLEASE NOTE ========================

JCL support as alternative to system menu.

In our continuing effort to support languages other than LISP on the CADDR,
we have developed an OS/360-compatible JCL. This can be used as an
alternative to the standard system menu. Type System J to get to a JCL
interactive read-execute-diagnose loop window. [Note that for 360
compatibility, all input lines are truncated to 80 characters.] This
window also maintains a mouse-sensitive display of critical job parameters
such as dataset allocation, core allocation, channels, etc. When a JCL
syntax error is detected or your job ABENDs, the window-oriented JCL
debugger is entered. The JCL debugger displays appropriate OS/360 error
messages (such as IEC703, "disk error") and allows you to dequeue your job.