If I can’t get it working on Linux I get a refund. For the past two years my Steam year in reviews have showed 100% of my play time was on either Steam Deck or desktop Linux.
If I can’t get it working on Linux I get a refund. For the past two years my Steam year in reviews have showed 100% of my play time was on either Steam Deck or desktop Linux.
I remember that! I had Unreal Tournament 2004 and it technically had a native Linux version but it wasn’t on the CD. You had to extract most of the files from the CD and go download the Linux executable file from the unreal website to drop into the installation folder.
Proton is just Wine from Valve. They add their own fixes and patches and whatnot and have an “experimental” branch you can try with games that don’t work right away, but it’s just Wine. Everything Valve does to Proton eventually makes it way back upstream to Wine proper. One reason Valve may not make it available for MacOS themselves is because they’re basing their SteamOS on Linux, and while MacOS and Linux are both Unix “like”, MacOS was/is more based on BSD, so the system calls may not always line up or work exactly the same when translating them. I do think however that Proton, or a modified version of it at least, is what Apple’s game development kit thingy leverages.
After Steam officially released its native Linux client I played Half Life 1, 2 and “Brutal Legend” because they all had native Linux ports before proton was a thing. Before that I remember playing games like Sauerbraten (quake like fps), Battle for Wesnoth (my wife and I still play this together), Frozen Bubble, LBreakout2 and several other Linux native games.
I’m on my laptop so I thought I would elaborate on my first comment to give you things to watch out for if/when you update. I’ve been hosting mine with the zip file manually installed with my own Apache/PHP/MySQL/MariaDB setup for ages now without issue. It’s been rock solid except for, like I said, the occasional changes required to take advantage of new features such as adding new indices to the database or installing an additional php addon. Here’s the things that I noticed with updating to 28.
It seems like they’ve made some substantial under-the-hood changes to the user interface that shouldn’t have been shipped to the “stable” channel. It’s not completely broken, it “is” usable, especially after they restored my bulk move/copy button, but I still can’t use the Retention app, at least last time I looked, so I’ve literally got daily cron scripts to check those folders for old files and delete them, then trigger an occ files:scan of the affected directories to keep the Nextcloud database in sync with the changes. This however, bypasses the built-in trash bin so I can’t recover the files in the event of an issue. I actually considered rolling back to 27 for a bit, but decided against it, so if I were you, I would stick with 27 for a while and keep an ear to the ground regarding any issues people are having that are or aren’t getting fixed in 28.
I’ve hosted mine for years on my own bare metal Debian/Apache install and 28 is the first update that has been a major pain. I’ve had the occasional need to install a new package to enable a new feature, or needed to add new/missing indices to the database, but the web interface literally tells you how to do those things, so they’re not hard.
28 though broke several of the “featured” apps that I use regularly, like “Retention”. It also introduced some questionable UI changes that they had to fix with the recent .1 update. I’ll get occasional errors when trying to move or delete files in the web interface and everything. 28 really feels like beta software, even though we’re a point release in and I got it from the “stable” update channel.
Just one or two, and it’s been quite a while. One of them, I don’t remember which, it was because of some anti cheat that caused the issue.