Use a simple script to run the installers in the same container as the base game:

#!/bin/bash

export STEAM_COMPAT_CLIENT_INSTALL_PATH="$HOME/.local/share/Steam"
export STEAM_COMPAT_DATA_PATH="/$HOME/.local/share/Steam/steamapps/compatdata/*prefix number*/"

"$HOME/.local/share/Steam/steamapps/common/Proton 10.0/proton" run "$HOME/Downloads/StellarisExp1.exe"

Just change the relevant parts to run the other installers, e.g. the installer name and location and the prefix number to match what Steam has generated

I just store all my game files on my NAS and have a set of bash scripts to generate installers for lutris, so if anyone in my family wants to play something I've brought they just run the script, select the game and it does everything for them. Got over 200 games and it works almost flawlessly.

Sure!

I have all the original, un-edited game files stored on my NAS; such as gog setup files, Steam files or just ROMs. Then with each game I store anything else needed to get it to run, such as custom patches, cracks if necessary, mods etc.

I have another folder full of tools, such as Steam Redistributables (DirectX, VCRedist, DotNet etc), any emulators that aren't part of lutris's runners and things like Goldbergs emu. And another folder with the bash scripts for each game.

So my family or anyone visiting can go to the website I run on our local network and download a bash script. This script just checks if they can see the NAS and the game folders, if not, it automatically mounts the directories and logs in for them. Then it reads all the game folders and lets you search for the game you want to install. When you select the game you want it loads their specific script which writes a .yml file to your home directory which lutris can then read; depending on the type of game depends on how elaborate it needs to be.

The script ends by launching lutris and pointing it directly to the .yml file which starts the installation; I've made mine all automatic so no one has to press anything once they select where to install and lutris starts, everything will install itself. Helps keep things simple and reduces errors.

There's a little more detail to each bit, such as using autohotkey to automate installers that don't have silent options, or ISO installs with CD Keys etc but that's the rough gist of my current setup, took a while to get all my games working buy now they are done it's easy for everyone!

Happy to explain or help if anyone has any further questions!

If the pirated game you are running uses the Goldberg Emu or a similar variant then they have the capabilities of Achievement unlocks. If you are on windows you can also combine this with Achievement Watcher which can pick up the achievements and even display them as you get them with toast notifications.

Same here. My current method is a self hosted website on my home network which showcases all available games, followed by a bash script download that will automatically generate the yml file for Lutris to fully install any of my 200+ games.

Whilst this is currently the best way I've found for my setup this app seems like the perfect thing to potentially swap to, if Linux was supported.

It looks like you're missing libva.so.1, so go to your /usr/lib32/ directory and make a symlink to libva.so and call it libva.so.1.

However, this probably won't fix the game. I had to also symlink libvpx.so.1 but after all dependencies were met, GlibC throws an error. I think it was due to the version of GlibC used in the game is very outdated and the systems GlibC no longer uses the same calls, so it bugs out. Similar errors are found in the Life is Strange: Before the Storm Feral Launcher, but that can be patched by compiling a simple file, not sure it's possible for this game.

As far as I know the Linux Native version of Saints Row 2 doesn't work.

Just install the lib32-libnm package. The one Steam is supplying is outdated with the new libgudev 238-1, by installing your own lib32-libnm your system will use that over Steams one and it should launch fine.

Is the executable you are pointing Lutris to in the same location as the steam_emu.ini file or the steamclient64.dll?

Lutris sets the launch directory by default to the same directory as the executable you are launching, but some cracks need the default directory to be somewhere else

A very useful write-up, will definitely be adding these to my repertoire!

I've got all my 200+ games, mostly from Steam, working on Linux and have encountered many of the listed DRM but I mostly solved them using other groups cracks and mainly the Goldberg Emu.

This will certainly help me in the future, especially with some more obscure titles that don't have many pre-cracked files flying around online, many thanks!