Hey there!
I’m a solo dev working on a sci-fi grand strategy game (I didn’t manage to find if self-promo is allowed so I’ll keep the name for myself).
I was updating my planning and started to think: since my game will be published on Steam, it will be playable on Linux using Compatibility Mode even if I don’t specifically target Linux itself. I myself play on an Ubuntu and this allows me to play almost every Windows game (old ones are more capricious, but recent ones are ok).
So I’m wondering, is there really an advantage to have native Linux support nowadays? As a solo dev, the thing I lack the most is time. The days/weeks/months it would take me to add it and fix all the probable bugs it entails could be used to improve the game itself or add features instead for example.
On a more general note, what do you other Linux players expect from a Linux game?
If you yourself use/are familiar with Linux and willing to actually test and polish your Linux version to the same standard as your Windows version, then a native Linux version is always appreciated.
However these days, it’s probably not necessary and a lazy afterthought Linux version is like a bad console port, and because we DO have the option to run the Windows version, it’s probably worse than no Linux version at all.
So it really depends on your personal feelings towards Linux, and nobody’s going to judge you for not providing a native version you can’t personally test and support. That’s why we have Proton.
I use Bazzite, which is literally designed for gaming (pretty much steamOS), and more often than not, the Windows version with proton works better than the native Linux runtime.
It’s not the OS, it’s the game.
Honestly, I wouldn’t bother.
Linux is a small market and people who buy exclusively native linux games is even smaller. If your game works fine with Proton that’s great.
You’re a solo dev and should pick your battles. I would focus on getting steam deck verified instead, if possible.
I would focus on getting steam deck verified instead, if possible.
One billion times this. That’s a checkmark that increases your marketshare by a lot. Desktop Linux users (not all, but some) look to that as a good indicator on whether it’ll run for them because it’s even harder to make it run well on the steam deck. Kind of a “two birds one stone” thing
I was going to do it anyway, but your answers gave me even more confidence in how important it is! Thank you :)
I really appreciate when a dev puts the extra effort in to make a Linux port, but I can understand when a solo dev such as you doesn’t have much time to spend on porting. To be honest, I’m just happy if the developers at the very least test the game on Linux using Proton and WINE to make sure it’s working well and correctly. That way if making a native port really is that much of a hassle, I expect them to at least test it on Linux. I think that most large teams should make a (good) native port, though.
I’m using Ubuntu myself to develop actually so I’m kind of doing that all the time. The problem is, my machine isn’t everyone’s machine, my drivers aren’t anyone’s drivers, and so on.
In the end I think that I’ll try to give Linux builds to testers to see if they report a lot of bugs or not and decide at that moment if it’s too much work or not.
Sounds like a good strategy. I don’t know all the details, but from the way I understand it, your Linux build would be run by Steam in a Linux container, Steam Runtime. So build and test against that if you can. If I have it right, maybe the Steam Runtime container will give you more confidence if you are able to go with a Linux build.
edit: If you sell your game through Steam.
Honestly, I prefer you go with Proton. Some of the native games I have are quite a few versions behind their windows counterparts. AND most likely it will run better anyways. Better for you, better for gamers. Win-win.
*Lin-lin
Its about practicality.
Even big studios cant handle supporting a native linux version and having it run well while supporting windows versions… which usually ends up with people running the windows version via proton over the native version (Looking at you, Cities Skylines, Truck Simulator games, and more)
So I would say take the easy route and develop for windows with checks to make sure it runs okay in proton, probably a lot less headache and effort than trying to create a seperate native linux codebase.
Agreed.
I’m a big Linux guy but you have to make compromises in this universe. Proton is amazing and should be the goal for most developers.
I personally am fine with Proton, the native Linux build usually doesn’t work as well as the Windows one because devs don’t usually care because of smaller market share (or don’t have the time as is often the case with indie studios).
What’s the name of the game? I’ll add it to my wishlist if it sounds like something I’d enjoy.
Also, if I may ask, do a GOG release, I do 90% of my gaming there.
Proton it will probably be then :) The game is Uncharted Sectors, I don’t have a Steam page public yet, but you can subscribe to the mailing list if you are interested, subscribers get access to the beta (https://uncharted-sectors.com/)
I’m not that familiar with GOG, I’ll take a look at it. Does it have a similar Linux compatibility layer? Because if not I do need to make a native build then
Proton is usable even without Steam, you simply publish the Windows version only and people will figure it out. If you make sure it works with the Steam Compatibility layer (Proton), it’s easy to run anywhere on Linux.
For GOG the easiest would be Heroic Games Launcher which also uses Proton.
Noted, thank you :)
I honestly mostly shop for “SteamDeck verified”.
Sigh… this is exactly the sort of developer decision people were worried about when Proton first came out, and why some Linux users were opposed to it. Obviously in retrospect the benefits of Proton have been worth it, but those folks wouldn’t be wrong to say “I told you so.”
My take on it is that if you’re not developing Xbox-first (which would imply being forced into DirectX etc.) you should pick libraries that give you cross-platform compatibility “for free” (I know it’s not that simple, but you know what I mean) to begin with. It has to be part of the plan from the beginning (and integrated into your build/test pipeline, etc.); writing the whole game for Windows first and then trying to add Linux support after the fact is a fool’s errand.
This is a good take… You can tell when newer (usually indie) games were built on OS-agnostic engines; you can’t really tell the difference between the Linux runtime and proton.
Otherwise, proton is often better.
Well, I’m using Godot which can target all three big OS, though clicking on the export button and actually supporting a platform is not the same.
In the end I think I’ll try to make builds for all OSes and have testers for each platform, and estimate the viability of the builds from the amount of bugs they give me back.
In the end I think I’ll try to make builds for all OSes and have testers for each platform, and estimate the viability of the builds from the amount of bugs they give me back.
Don’t forget to consider the possibility that getting more bug reports from Linux users doesn’t necessarily mean the Linux version is more buggy, but instead that Linux users may be better at finding bugs or more willing to report them.
deleted by creator
I find that native clients are almost always a worse experience than running through Proton. Cursors not hiding or not appearing, inability to adjust certain graphics/display settings, and, rarely, worse performance than through Proton (including not actually managing to init).
That said, Proton has its own irritating quirks. Try turning off mouse acceleration in Skyrim on Linux for instance. Have to use protontricks to find the appid, then you have to nav to it in any of the locations that it could be found (depending on flatpak, native, etc.), and then you have to sift through the prefix to find the bloody INI that has the setting to toggle.
But as an indie dev, you should do whatever makes less work for you so you can do more with your time. If supporting native Linux will increase your workload and detract from work on the game itself, then simply don’t support it. Just make sure that your Windows builds work via Proton.
EDIT: Here’s a specific example from today. For reference, I normally play everything through Proton so I haven’t intentionally loaded a native game for like 6 months. But today I loaded up Yooka-Laylee not realizing it had a native version. Get in, alt tab to screencast on Discord aaand… the game nixed my cursor entirely. I mean, it likely just locked it to the game window, but that still means that I couldn’t interact with my PC outside the game window. So quickly downloaded the Proton version and it worked just fine after that.
Native is always better, but Proton (what’s used by steam OS to run windows games) has worked for me for every title I’ve tried (even some small indie titles)… Sometimes graphics settings can be inconsistent, but I’d say it’s a pretty safe bet if you’re using an established engine it will just work with Proton
That is my experience too, I guess some Linux builds are just poorly optimized in comparison to the Windows ones.
Valve’s engineers did a wonderful job with Proton honestly
Get us some Linux exclusives and we can stick it up towards Windows amirite
Haha problem is I have a kid to feed, and I fear that cutting myself from 90% of my potential player might be a bad play if I want to be able to continue feeding him
Choose whatever is best for you.
That being said, as a Linux user I always appreciate a native Linux version of a game that runs well and is updated promptly.
As far as I know, there are game engines that make it easier to publish on many platforms, but I’m no expert.
Yes to both. I want games that work well on Linux, so I’m happy with whichever you choose to test. If you provide both, I have options.
Yes. It’s still needed. Mostly because not everyone using Linux is using a controller or other peripheral input device that just works natively (look at non-steam os handhelds and Bazzite for instance). On smaller screened devices, menus and keyboard specific options can be problematic regardless of other compatibility features.
