Lutris is just for organization, and managing the Wineprefixes. I don’t even use it as an installer per se. I install manually with wine and then point Lutris to the right prefix and game executable.
Anyway, the steps outright skipped are:
- Having to unlock the FS for writing and set up SSH and (…) – This is a security liability if you CARE. I don’t, I just think it’s more effort than necessary.
- Transferring the game folder from a PC to the Deck, since you just. Do it all inside the deck itself.
It’s no big deal doing either of those, but I find it less of a hassle.
My procedure for pirated games, on both PC and deck is:
- On terminal, create a prefix by using
export WINEPREFIX=. Like/home/myuser/Games/NameOfTheGame/pfx - Run
winetricks -q corefonts– The fonts ensure the installer won’t have any rendering errors, plus running winetricks at least once forces wine to create the prefix’s folder structure. - Run the installer from the same terminal session, just doing
wine Setup.exe - Usually install to
/home/myuser/Games/NameOfTheGame/gamefor organisation’s sake, but this is unnecessary and requires dealing with Wine’s handling of your unix folders which is always slightly annoying.
From here, you could launch the game directly through Steam, but then Steam would create its own prefix, and some games require fiddling around with the things installed on the wineprefix (or with envvars or…), which is why I use Lutris as a middleman, as it ensures the game will run on the prefix I created, and if anything is missing, I can winetricks it. Lutris even offers a ‘create Steam shortcut’ option to make it all look neat on the Deck’s console mode screen.
Fuck all technology based aesthetics except for whatever it was that Lain was serving.