Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Look at CS2, they had sound problems and the mouse input makes problems with multi monitor setups.
They fixed the sound problem the day after they released it, but these are just examples.
Even if devs would provide us with native builds, bug fixes will also be low priority on Linux.
Proton is fine by me.
(In case you were attempting to make a pun on Windows... okay, I hate Microsoft. How they slip in things that absolutely no one wants into their operating systems is pretty disgusting.)
+1
He actually has a point. No-one cares about native linux ports except for half a dozen of people.
As I said, such ports are dead in the water now ...
I really want to know who in the Linux community hurt you, as you seem rather hostile to anyone asking for a port...
From a strict technical point of view, a game running on Proton does not run very differently from a game running on Windows. I'm talking in terms of how it accesses the hardware, etc. It will be a process, talking to the kernel indirectly through a library, talking through the graphics card through an API that gets converted to native GPU code and so on.
So on Windows your program uses a high-level API (relatively speaking) called Win32, which gets converted to native (NT) kernel calls. With Proton you use that same API (Win32) which gets converted to native (Linux) kernel calls. Same way of running the game, just different kernel. Similar story with graphics code, you use some high(ish)-level API like Direct3D, which gets converted to native GPU code. Some details change but it's effectively a very similar way of accessing the hardware.
So the people who want "native" ports need to explain exactly which APIs they would prefer instead. glibc instead of Win32? It's hardly a better solution for games (or for anything...) In fact quite an inferior solution. And not all Linux systems use glibc anyway, some are built using other libc implementations. For graphics, OpenGL or Vulkan instead of Direct3D? Sure, that's quite possibly preferable (and already supported, I play the Vulkan version of this game), but factually if you have a stable implementation of Direct3D on Linux (which we now have) then there is no fundamental difference.
Proton *is* the de-facto native run-time for Linux games. That's what Valve is saying, that's what some Linux vendors (Canonical) have also concluded. Yes, the Proton APIs originate from the Windows world, but so ♥♥♥♥♥♥♥ what? OpenGL did not exactly originate from the Linux world either.
TL;DR there is nothing that is magically *more* native than Proton. There is no known way that would be significantly faster or more stable. The Valve developers accumulate hundreds of man years of expertise running games on Linux and after spending 2 decades on that problem they came up with Proton. They ship their own console running on Proton. Do you know better than they do?
For origins of OpenGL... it originated with SGI and Mesa itself originated from the Amiga.
Officially, Proton only supports a small tiny subset of games! Literally, if you turn off the 'just play everything that is Windows with Proton' it is a tiny list of officially supported titles. And they didn't spend 2 decades developing Proton... They had to wait until the Wine base was getting to a state they could implement it within Steam. Hell, I remember suggesting it like a year before Proton was available. I also remember when Wine could barely run Notepad, and even that at the time was impressive!
Well, you'll have to tell me which studios are still doing Linux ports, actually. Aspyr seems to have stopped this...
And no, I'm not hostile nor hurt, it is just I don't see the point to have Linux or Mac ports for games. It makes no sense from an economical standpoint. So, that's why nobody is doing them anymore.
But I'd like of course to game on Linux since I despise Windows so much, but just ... it unfortunately doesn't make sense.
There are still quite a few indie developers that release native versions. Feral and Aspyr just did ports they mostly had to make contracts to do the ports, which seems to me to be a bad business model all around, since if a bug pops up on one of them, then who do you go to? Is it a porting bug, or a bug in the original game? Then there is the patching differences... it's always been better to get the original developer to do the port.
The funny thing is Valve have been working on Proton for Linux, but I'm kind of surprised it's not available on macOS, then again Apple I think decided they should just do it themselves... then again I think Apple was hoping their Apple Arcade would catch on... it has not.
But yeah, I still see a steady stream of games coming out for Linux, just not the AAA games. Hell, X-Plane is huge and still does a native Linux release.
Let's be fair here. Mac users in general need way more handholding than Linux user to do anything. You can trust that Linux users aren't completely computer illiterate, because people who gravitate towards Linux tend to be a bit more on the PC/tech enthusiast side of things.
Of course I don't count Steam Deck among that, but valve has that verified for steam deck marker for games that are "pick up and play" and deck is designed to be simple to use. You absolutely cannot rely on mac user being capable of doing anything other than knowing how to use apple software on mac.