this post was submitted on 06 Nov 2025
109 points (95.0% liked)

Linux Gaming

22278 readers
169 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

No memes/shitposts/low-effort posts, please.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
monolalia@lemmy.world
109
Why do game devs keep making horrible Linux Ports? (lemmy.world)
submitted 3 weeks ago by daggermoon@lemmy.world to c/linux_gaming@lemmy.world
51 comments fedilink hide all child comments
 

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 are viewing a single comment's thread
view the rest of the comments
[–] rtxn@lemmy.world 55 points 3 weeks ago* (last edited 3 weeks ago) (14 children)

From the sole developer responsible for Factorio's Linux-native port: https://www.factorio.com/blog/post/fff-408

"Why don't most games support macOS and Linux?" is a sentiment I often see echoed across the internet. Supporting a new platform is a lot more than just changing some flags and hitting compile. Windows, macOS, Linux, and the Nintendo Switch all use different compilers, different implementations of the C++ standard library, and have different implementation quirks, bugs, and features. You need to set up CI for the new platform, expand your build system to support the new compiler(s) and architecture(s), and have at least one person on the team that cares enough about the platform to actively maintain it. If you are a video game, you will likely need to add support for another graphics backend (Vulkan or OpenGL) as well, since DirectX is Windows-exclusive.

Many developers will take one look at the Windows market share and decide that it is not worth the trouble to support other platforms. Also, with the meteoric rise of the Steam Deck and Proton, it is easier than ever for game developers to ignore Linux support because Valve does some black magic that lets their game run anyway.

The list of Linux-first games is so short it's not even a factor. It's very difficult to justify the additional effort of implementing a platform that serves exclusively the playerbase with a ~3% market share, especially when a different method exists to serve that same playerbase that works just as well and also serves the 90%+ with no additional effort.

The article I linked also contains an explanation as to why GNOME's decision to drop server-side decorations is fucking stupid.

[–] BananaTrifleViolin@lemmy.world 7 points 3 weeks ago* (last edited 3 weeks ago) (2 children)

Worth saying the 3% market share is very new, and previously the share has been way way below this. At 3% that is millions of users but even that is hard to justify a linux release; many games dont even get MacOS versions even now and it has higher desktop share.

The other problem for linux is version control - libraries are different across distros of different ages, and also constantly update. If you build software on a dependency and it changes in a few years, your game may break. As bad as windows is, when games are distributed a lot of the dependencies are distributed with the game as DLLs and installers for Microsoft tools. But for linux you previously could not guarentee the same version of the same dependency will be available on two distros still actively supported.

It can be surprisingly hard to get old Linux software to run on new Linux distros. People are not generally aware of this as generally its old windows and dos games that people try to get working (so wine or dosbox are used), not old Linux software like Open Office from 2005 or an old version of Firefox. Most linux software continually evolves or its niche and just stops working (unless youre willing to go back and compile from source, and that can get nightmarish if it doesnt compile)

Proton is part of the solution but developing "for" proton is not efficient long term. It is great for enabling windows games to work on linux, but linux native games would be more optimal. We're just lucky we're now in a time where there is a lot of CPU and GPU resource available to support the overhead and windows is also so bloated making linux + proton comparatively better.

I suspect Flatpak may be another part of the solution - Flatpak can essentially be a way of ensuring a game can have a fixed set of dependencies which install on any Linux and should just work. Its not that far off the windows model of packaging DLLs, but is much cleaner and contained.

Nix is another potential approach to this.

But developing for Linux wouldn't take off until the market share is substantially higher. The SteamDeck and tge rumours Steam console may help with that, but for now I think devs relying on Proton makes sense.

[–] Euphoma@lemmy.ml 1 points 3 weeks ago

Steam itself has bundled libs for apps to use (steam linux runtime)

load more comments (1 replies)
load more comments (12 replies)