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
ProtonDB is a great website to check out to get a clue as to how games on Steam are currently running under Proton emulation. It's fair to say, that many classic and older PC games will run great on the Deck.
https://www.protondb.com/
It's possible to install games outside of Steam on the Steam Deck too, however, it's currently more difficult to tell how they will perform.
https://lutris.net/games/warcraft-iii-the-frozen-throne/
https://lutris.net/games/warcraft-iii-reforged/
https://lutris.net/games/myth-the-fallen-lords/
Lutris uses any of the open source software tools developed and produces compatibility fixes to make games run.
Its not yet clear what SteamOS 3 supports in its default protected mode (you cant break anything), Valve have said they will support flatpaks which are a very easy way to install software on Linux. But Lutris does not have a stable version in flatpak form.
The other easy wayo to install softtware on Linux OS is via a software repository like a library of sorts were you'd just search for Lutris and install it, but again its unclear if SteamOS 3 will have one.
Valve have said you can enable dev mode and then installing anything you want.
So its basically wait and see what happens.
Proton is a good translation layer, but there are original source ported engines that you can easily install these days as another compatibility engine.
However to make it easy it's handy if you have the game on steam and not as an external CD.
Games from the 90s and early 2000s tend to have rudimentary DRM protection like install keys and basic disc checks, which although not always trouble-free should pose less of an issue.
However, from the late 90s and onwards, more sophisticated DRM solutions like driver-based DRM, hardware checks, online registration, etc. pp. became increasingly popular. Solutions from that era are almost guaranteed not to work on modern hardware and operating systems - even Windows!
DRM is by far the biggest issue to gaming on Linux and also the greatest threat to gaming culture preservation. DRM-ed products are defective by design![www.defectivebydesign.org]
For your convenience on the Steam Deck, you ideally check if the game is available for (re-)purchase digitally: DRM-free at best, else DRM solutions compatible with WINE/Proton. Same goes for other middleware.
As pointed out before, ProtonDB[www.protondb.com] and Lutris[lutris.net] are good places to get informed about a game's compatibility. Gaming forums and the PCGamingWiki[www.pcgamingwiki.com] can be helpful, too.
Some classics may have received native Linux ports back then, but chances are they won't run on newer Linux versions, as older Linux software tends to require deprecated dependencies.
In the same vein of wanting to play some legacy/vintage/abandonware Linux games like Myth ('damage'), it might worthwhile for the community to come up with an AppImage build environment so all the deprecated deps can be contained therein.
Why AppImages?
* Download a single file, make it Executable, and run.
* AppImage are portable. You can run them off SD Cards and USB Sticks.
* AppImages configs can be either in $HOME or AppImage Config directory so you can have the config directory on the portable storage.
* AppImages are like Android/Mac/NeXTStep Apps - all deps are stored within & execute as the user
Why not Flatpaks? ('damage')
* Flatpacks require elevated privileged and other bullstuff to install.
* Flatpacks lack all the advantages of AppImages
Why not Snaps? ('damage')
* Those are from a Canonical managed store (like Google Play) and need extra rights like Flatpaks.
@retrogunner Depending on who you ask, they will give you a different answer on which way to ship software on Linux best, but comparing Flatpaks to AppImages is like comparing pears and apples. Flatpak is much more comparable to Snap in what it aims for, except not made by discount-Musk[en.wikipedia.org]. On top of that, local installations of Flatpaks don't require sudo – and for most applications, local installations work fine.
Whilst I agree AppImages may be right for videogames and archives, shipping every dependency for every tiny applet independently makes for an inefficient use of disk space and bandwidth.