GE-Proton 11-8 and 11-9 land on Valve's Proton 11, hours apart
The maintainer shipped a feature release on October 13, then a hotfix just hours later to fix a Crimson Desert hang and a broken HDR detection.
GloriousEggroll pushed GE-Proton 11-8 to GitHub on October 13 at about 20:46 UTC, and 11-9 went out roughly three and a half hours later, just past midnight on the 14th. Both sit on Valve's Proton 11 foundation, meaning they're rebased on Wine 11. But the spacing is what actually tells you something.
11-8 was the first GE-Proton update since 11-7, a June 24 release. That's a three-month gap for a project that used to move far faster, and the community had begun to worry. A r/linux_gaming thread from earlier this year openly discussed the delay, and several people called the fork overdue. If GE-Proton is your daily driver, the silence was loud.
What's inside 11-8 and the 11-9 catch
The feature release covers a lot of ground without much fuss. Controllers are the main event. There's an automatic PlayStation-to-XInput fallback when Steam Input is off, plus fixes for DualSense detection in Diablo IV and new DualSense Edge support. That matters if you game on a PS5 pad, since GE-Proton has historically led on the controller side. It's arguably competing where Valve's default falls short.
The changelog also reaches into Wayland and windowing. It fixes overlay closures under Wine-Wayland, Battle.net tray menus, and a grab bag of titles like Warframe, Deadlock on Niri, and Guild Wars. Video playback gains AV1 decoding, and Resident Evil 4's corrupt intro is fixed. There's an opt-in Bluetooth LE toggle for Zwift and Rouvy, plus a return for ARM64 DXVK-NVAPI builds.
Then came 11-9, and it explains the rush. It's not a random late-night bump. Two fixes, one of which looks like it came straight from 11-8 itself.
Automatic HDR detection now works for DX11/DXVK and DX12/VKD3D-Proton under Wine-Wayland or Gamescope. The manual PROTON_ENABLE_HDR flag is largely pointless now. But 11-8's HDR detection apparently reported HDR screens as SDR, breaking Dragon's Dogma 2 and others. The maintainer caught it within hours and sent a hotfix. It's the kind of fast feedback loop you want on your side of the keyboard, and it quietly rebuilds trust after a long silence.
It also patches Crimson Desert, which got stuck looping a menu video the moment you pressed Play. Both Wine-Wayland and XWayland builds are affected. Not cheap to get right.
The AI problem GE-Proton shares with upstream
There's a thread worth pulling on. During the 11-7 video rework earlier this year, the maintainer publicly noted AI-assisted work. That alone isn't shocking. It just runs headfirst into a real problem for the projects GE-Proton grows from.
Wine keeps a strict clean-room policy. Its wiki says plainly: don't use an LLM to generate code, since there's no guarantee the training data respects the guidelines or the output is LGPL-compatible. Wine has to be a white-room reimplementation, and AI output can smuggle in fragments of leaked Windows sources. So AI-heavy parts of GE-Proton generally won't go upstream, even when they fix real pain.
Valve and Wine draw hard lines over where code comes from. GE-Proton leans on AI to move quickly for a niche, fixing things at the same time. Neither position is obviously wrong. And Valve has quietly adopted GE-Proton ideas over the years, like the FSR3-to-FSR4 upgrade path, while keeping its own provenance rules. The Hacker News crowd said it best when one user called the fork dynamic "literally how open source development is meant to work," with each side evaluating the other's features.
That back-and-forth is really the point of all this. A fork that can't be trusted to go upstream still forces the main line to react to it. That's how these ecosystems improve.
What you should do now
If you run GE-Proton by hand, grab the tarball from the releases page, drop it into your compatibilitytools folder, then pick it per game or flip it on globally under Steam's Steam Play settings. ProtonUp-Qt does it automatically and ships preinstalled on Bazzite.
One thing before you go poking at environment variables: 11-9 makes HDR detection automatic, so PROTON_ENABLE_HDR and PROTON_USE_HDR are mostly obsolete. You can still set DXVK_NO_HDR=1 to turn HDR reporting off if you need to.
For most people, the right move is simply updating to 11-9 and watching your games. Given the recent history, that feels like a good bet.
Head here to the GE-Proton releases page.
