I still have nightmares about editing Xorg config files in 2008 just to get a refresh rate that didn’t make my eyes bleed. Back then, “Linux gaming” was mostly a euphemism for “spending four hours in a terminal to play Tux Racer at 15 FPS.”
We’ve come a long way. Obviously. But if you’ve been daily driving Linux on your desktop anytime in the last six months, you know we traded one problem for another. We went from “nothing works” to “everything works, but in twelve different, incompatible ways.”
You’ve got Steam managing its own prefixes. Lutris doing its own thing. Heroic Games Launcher handling Epic and GOG with a completely different folder structure. Bottles creating sandboxed environments that don’t talk to anything else. It’s a mess. A functional mess, but a mess nonetheless.
That’s why this recent push for the Open Gaming Collective (OGC) caught my eye. And frankly, my first reaction wasn’t excitement. It was the “xkcd 927” reflex: Great, another standard to compete with the existing fourteen standards.
But after digging into what they’re actually shipping in the latest Bazzite builds as of January 2026, I’m starting to think this might actually stick. Maybe.
The “Prefix Hell” Problem
Here’s the specific headache the OGC is trying to solve. I have Cyberpunk 2077 installed via Steam. I have Alan Wake 2 via Heroic (Epic Store). Both need Wine/Proton. Both need DXVK. Both create massive “compatdata” folders (prefixes) that duplicate hundreds of megabytes of Windows DLLs and registry files.
Until recently, these launchers acted like jealous exes. They refused to talk to each other. If I wanted to use a specific GE-Proton version I downloaded for Steam in Heroic, I had to symlink folders manually or use a tool like ProtonUp-Qt to download the same runner twice in different locations.
It’s stupid. It wastes disk space. It wastes bandwidth.
The OGC’s proposal—which Bazzite and a few other immutable distros started implementing late last year—is basically a unified directory standard for compatibility tools. It sounds boring as hell, but it’s huge.
Real-World Test: The Storage Saver
I decided to test if this actually works or if it’s just documentation ware. I grabbed my Framework 16 (running the Bazzite 3.9 “Gnome” image, Jan 2026 build) and wiped my gaming partition to start fresh.
The Setup:

- OS: Bazzite 3.9 (Fedora 43 base)
- Kernel: Linux 6.12.9-fsync
- Goal: Install three different launchers and see if they can share a single Proton runtime without me intervening.
I installed the OGC-compliant versions of Steam (Flatpak), Heroic, and Bottles. I used protontricks to pull down GE-Proton9-25 just once into the shared directory /var/lib/compatibility-tools.d/ (a path that didn’t exist in my distro six months ago).
The Result:
It actually worked. I opened Heroic, and it immediately detected the GE-Proton version I downloaded via the
Frequently asked questions
What is the Open Gaming Collective (OGC) trying to solve on Linux?
The OGC addresses Linux’s ‘prefix hell’ problem, where launchers like Steam, Heroic, Lutris, and Bottles each maintain separate, incompatible compatibility tool directories. Running Cyberpunk 2077 via Steam and Alan Wake 2 via Heroic forced users to duplicate hundreds of megabytes of Wine/Proton/DXVK files, symlink folders manually, or use ProtonUp-Qt to download identical runners twice. OGC proposes a unified directory standard so launchers can share a single Proton runtime.
Which Linux distro first implemented the OGC unified compatibility directory?
Bazzite, an immutable Fedora-based distro, began implementing the OGC proposal in late 2025, alongside a few other immutable distros. The tested build was Bazzite 3.9 (Gnome image, January 2026) running on a Fedora 43 base with the Linux 6.12.9-fsync kernel. The OGC-compliant setup uses a shared path at /var/lib/compatibility-tools.d/, which didn’t exist in the distro six months prior to the January 2026 build.
Can Steam, Heroic, and Bottles share the same Proton runtime on Bazzite?
In a real-world test on a Framework 16 running Bazzite 3.9, installing OGC-compliant Flatpak versions of Steam, Heroic, and Bottles allowed them to share a single Proton runtime without manual intervention. GE-Proton9-25 was pulled once via protontricks into the shared /var/lib/compatibility-tools.d/ directory, and Heroic immediately detected the version downloaded through the other launcher. It worked as advertised.
Why is the xkcd 927 ‘another standard’ concern relevant to the OGC?
The initial reaction to OGC was skepticism rooted in xkcd 927’s joke that new unification standards just add to the pile of competing ones. Linux gaming already fragments across Steam’s prefixes, Lutris’s system, Heroic’s folder structure for Epic and GOG, and Bottles’s sandboxed environments. However, after examining what OGC actually ships in January 2026 Bazzite builds, the author became cautiously optimistic that this particular standard might stick.
