Thank you for helping to keep GamingOnLinux civil and safe!
Please tell us why you're reporting this content. Please note we store your IP address for all reports to help prevent spam and abuse. You can also email any complaints to: [email protected].
- The original Pillars of Eternity is getting a turn-based mode Beta on November 5
- GE-Proton 10-25 brings fixes for Nioh 2, WoW, Rockstar Launcher and more
- Anti-grav racer BallisticNG brings new tracks, enhanced online play and more for the final update
- Chizha Mount Ling Dock for Steam Deck looks premium and it's fully featured but pricey
- The Siege Update for Dwarf Fortress has arrived
- > See more over 30 days here
Recently Updated
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
Last Epoch, TW Warhammer (the Feral versions just performs straight up worse, is months behind thus destroying mod support, etc. ), tons of Adventure Maker games (or Adventure Studio? You know, the one everyone and their mum use to create point & click games) have severe issues on Linux especially with windowing and input, Ark, Rust; and the list goes on and on.
That's not anecdotal but confirmed by all the error reports you see for issues and the suggested solution 9/10 times being "switch to Proton".
It is also confirmed by devs shutting down their Linux version because they don't want to deal with the Linux-specific issues (meaning they did have enough of those to be bothersome).
"Works for me" is always anecdotal and no argument when obviously lots of people are having issues.
Funny enough, one thread I've seen throughout all of this is that often the issue isn't actually in the stuff related to graphics (which is arguably the main focus of the work being done on Proton, dxvk, etc), but in the native libraries used for windowing & window refreshing, input, etc.
Surprisingly often, it comes down to usage of ancient SDL1 (which, please devs, just don't. Ever.).
So switching to Proton will solve the issues not because of some graphical bug, but because the native libraries used for the native Linux version are, frankly, crap - or outdated.
There are undeniably lots of cases where it does not work well for people - and then Proton becomes an option.
The other way around just doesn't happen because if Proton is the default already, there IS no native version to switch to.
When you look at ProtonDB and the games that are reported to not work there, they are overwhelmingly of the multiplayer variant. That's probably 70-80% of the less than 10% of games that are reported as worse than Silver - and we all know the issues there are not Linux, but devs opting for the blunt hammer to their cheating issues.
In other words, the chance that your (non-MP) game will work fine on Proton is way over 90%.
The chance that the native version will work just fine? Hard to say without official data (which I doubt anyone has), but given the amount of reports and sentiments you generally see, I doubt it is better than the Proton stats.
Of course I wouldn't recommend going for Proton straight away if there is a native Linux version - because most likely that will work just fine and it will also perform better in that case.
But the approach to just switch to Proton always to get a higher chance at having no issues at all seems at least understandable to me.