I’m asking because I just bought Cronos: The New Dawn on Steam because it has a native Linux port. To be fair, I would have bought it at some point anyway but I got excited when I saw it had a Linux port. The game is missing features that the Windows version has, It runs horribly at any setting other than very low. I think they only bothered testing for the SteamDeck. But if that’s the case, why does it support FSR 4.0? To be fair, the Windows version doesn’t run amazing either if you enable ray tracing but it still performs way better than the Linux port. Why do devs keep doing this? I’ve bought many Linux games that have problems that the Windows versions don’t have. Why even make a port if you’re not going to bother testing or optimizing it?
You must log in or # to comment.
Because it costs money to maintain that most indie studios don’t have given the small target audience. I simply always use Proton, even if a native version exists.
Yeah I get that and I’m not disagreeing. But why port it at all, that being the case?
It might also be a single dev who pushed for it. With only a 1-3% market share, the company is unlikely to push resources at it. That 1 dev getting any working version out is a win in many ways.
Also, most Linux users are a lot better trained at reporting bugs. Most of the time, this is a good thing, letting them get fixed in FOSS development setups. Unfortunately, in gaming, it ends up making Linux look a buggy mess. When 60% of your big reports come from 0.5% of your users, companies can panic. Even if the same bugs exist in windows, just no one bothers to report them.
It might also be a single dev who pushed for it. With only a 1-3% market share, the company is unlikely to push resources at it.
And yet Microsoft and all PC OEMs panic at the existence of Steam Deck and throw resources at Windows-based competitors.
The same reason a dam owner panics over a finger sized leak. A hole becomes a crack, a crack a breach, and a breach can collapse the whole dam.
It’s gonna be different case by case, but my best guess would be it starts as wanting to please the community, then realising Linux users get weird errors they never hear about from Windows users and then deciding that all 5 Linux users are not worth it if the issue doesn’t concern majority (Windows) users.
As for missing features, usually it happens because they use some Windows-native feature (like direct DirectX calls) which saves them implementing workarounds for their engine. And porting to some Linux api is delayed indefinitely for the same reasons as bug fixes: not large enough user base.
Linux gamers often say stuff like “it’s literally one toggle in [insert game engine here]” but that’s never the case. Doesn’t mean new devs don’t fall for it.
IMO we should fuck native Linux builds - game engines are complex and messy beasts, building on one platform and testing on Proton is the best for everyone, IMO.
Linux gamers often say stuff like “it’s literally one toggle in [insert game engine here]” but that’s never the case. Doesn’t mean new devs don’t fall for it.
If developers (those that come from Windows) fall for anything, it’s the myth that Proton is already perfect and native ports have no value.
With Steam Deck the hurdle for game developers to dog food native ports of their games is lower than ever. SteamOS comes with Podman and Distrobox, so installing the Steam Linux Runtime SDK on Steam Deck’s desktop mode should be doable after reading a howto.
I have a question (an honest one, not implying anything). Given that most games work perfectly on Proton, why does a Linux port excite you?
It can be beneficial in terms of performance if done right. The native Linux build of Baldur’s Gate 3 runs considerably better than the Windows version via Proton, even though the Proton version already runs better than it runs on Windows natively.
Good question. It means to me that developers thought that Linux as a platform was worth targeting. One could conclude, the more Linux ports we see, then more people must be using Linux. It’s my dream for us not to be treated as second class citizens where computer operating systems are concerned.
It’s a baby step thing. They want to develop for Linux but so far it’s about 3% of steam users that use it. So when a studio does its testing/optimizing they focus on the platform their player base is using most.
Obviously there’s a negative feedback loop here. Players avoid Linux because of issues which causes devs to neglect it because of player numbers which causes issues in the game…
Steam is pushing Linux currently but it’s hard to overcome the dominant position windows and consoles have. We’ll get there though.
On paper, a Linux version of a game would perform slightly better, because they wouldn’t have to use Windows system calls for synchronization and disk I/O.
This seems to be true for the games in my Steam library that have good Linux versions, though I can’t comment on the performance of bad ones because obviously I play those through Proton.
It takes a lot of effort for little money.
It takes a lot of effort for little money.
The effort is not that high if the engine used already supports Linux and was written with cross-platform compatibility in mind (which is every modern engine because of consoles).
👌👍
I know this is gonna dig deep, but consider this…
Linux just barely broke 3% share. As a company, whose goal is to make money, would you focus on what 97% of your base uses, or the 3%?
Further more, the company needs to spend QC resources for 1-2 versions of Windows, vs the multitude of Linux distros, but let’s say you can get a passable port, may not be the best but for minimal effort you can sell to a handful of that 3%, the business thinks “why not?”
In the grand scheme of things, native Linix ports is still low on the priority list for a company focused on making money
A lot of the “native ports” are done by a third party studio, and they don’t maintain it. Because of this, many games perform better through proton than natively.
Also save data is not shared between the versions, so if you’ve already sunk a lot of time into playing the buggy native port, switching to proton requires you to start over.
Also save data is not shared between the versions, so if you’ve already sunk a lot of time into playing the buggy native port, switching to proton requires you to start over.
To mess this up one as to be a special kind of stupid. It literally only requires to set up a few paths on the SteamWorks web UI: https://partner.steamgames.com/doc/features/cloud?l=english#steam_auto-cloud
Ya, and with Proton working so well, I’d rather focus on Windows, then at most work with Valve on making sure the game runs well with Proton. Way less work.
Linux just barely broke 3% share. As a company, whose goal is to make money, would you focus on what 97% of your base uses, or the 3%?
If your game is mobile friendly, treating Steam Deck not as an afterthought may be beneficial. Proton is not perfect. It has bugs, it loads a whole fake Windows environment into memory and API translation costs CPU and battery.
Further more, the company needs to spend QC resources for 1-2 versions of Windows, vs the multitude of Linux distros
That’s completely wrong. For games, the developer only needs to target whatever the latest Steam Linux Runtime is. It’s 100% identical across all distributions where the Linux version of Steam runs. That’s its entire point. Steam Linux Runtime is a more stable target than playing catch up with yearly Proton releases.
Unreal Engine’s Linux builds are very neglected compared to Windows. Windows gets DX12 which is the main rendering API for the engine, Vulkan (which the native Linux version uses, also available on Windows) is a complete after-thought unless you’re on Android where it is the main target.
Main Linux target for UE is Red Hat Enterprise Linux for movie CGI. The “we want open platforms” company don’t care about Linux gaming.
Specifically hates linux actually, Tim Sweeny is a huge Windows stan
My partner has had a really bad time trying to run cronos. We thought it was initially Linux problems, it’s the first game on her new rig. Turns out the game just has those problems on windows
Simon the Sorcerer Origins was recently released and their Linux version didn’t even run. Their run script contained just two lines and both of them were plain wrong. And after I fixed them the controller didn’t work.
Leave a bad review then.
I did.
Because they live in a fantasy world where optimizing a game for Windows and pouring countless of hours of QA into the Windows version makes a merely cross-compiled Linux version magically great as well because “PC is PC, right?”
Windows dominated desktop development for years, and Macs did the same in the creative world. So a lot of developers naturally know those systems best. Linux has always had the problem of fragmentation, different distros and different library versions all pulling in slightly different directions, which makes it harder to target reliably. That’s why things like the Steam Deck or Ubuntu LTS matter so much, because they give developers a stable baseline instead of chasing down tickets caused by someone building with the wrong version.
Tools like containers and Flatpak have improved the situation, but the underlying complexity is still there. When a studio doesn’t have the time, budget or experience to handle that, the Linux port is usually where the cracks show. The ones that tend to get it right are teams with stronger engineering depth, which is why you often see the better native ports coming from studios behind RPGs and sims where crossplatform work is already part of their pipeline.
Same reason why a nightmare for me is someone asking me to make an app I’m working work on Windows.
First I don’t have a windows machine. IDK where you get the iso any more. I think RKE2 support windows worker nodes but no clue what that really means. I don’t even know what that install would look like. After solving that I have to figure out how to build images for windows. No idea there. Then how do I add those tests to my pipelines, which I assume meaning adding those windows worker nodes to my test cluster, which now means I have to see how to quarantine them or somehow get the security suit working on them. Does my networking stack work on it?
After all that I can then ask, how do I compile my apps specific code and try and run it there. How do I do that for Windows? I have no real freaking clue. I think rust and python can pull most stuff fine but sometimes my depencies build with Linux in mind and don’t work off the bat. Should I make a Windows dual boot to build/dev/test? Will my dev tools work on it?
It’s not devs in general. Bloober is notorious for releasing poorly optimized games. They probably run terribly on windows too.
That hasn’t been my experience. I’ve played most of their horror games. I haven’t played The Medium yet but I will soon. Their games generally run pretty well for me. I will admit, I am a fan boy though. They are one of my favorite game developers.
The question is backwards: why are you not natively developing games for linux distros to see all the pitfalls developers deal with on a shoestring budget?
Easy to ask a question you do not traverse, harder to pave an easier road for everyone else.IMO: additional CD/CI pipeline and according QA, paired with the technological regression we’ve seen in real time graphics over the past few years and videogames being developed in sweatshops with a carbon-nanofibre budget, while ads get all the budget is a poor foundation in general.
Why commit to anything more than the bare minimum, when you need to desperately try to reach that while the circumstances are against you?
I feel like I never use native Linux versions. The exception thus far has been Two-Point Museum and Vintage Story. There are other games that have native Linux versions, Necesse and Mind Over Magic come to mind, but in my experience the Linux ports are never that stable and have spontaneous crashes that can be avoided altogether by running in Proton.
deleted by creator
