Open JayTee42 opened 4 months ago
I'm aware of this, and I have plans to try address this case in the next release if everyone else on the team is fine with it. In the TOML file, it'd probably look like this:
[umu] game_id = '0' exe = '/home/foo/WINE/flowers/drive_c/GOG Games/Flowers - Le Volume Sur Printemps/FLOWERS.exe' prefix = '/home/foo/WINE/flowers' proton = 'GE-Proton' # Will use the latest GE-Proton
Same for users' environment variables as it makes mores sense to define them under a table. For example:
[umu] game_id = '0' exe = '/home/foo/WINE/flowers/drive_c/GOG Games/Flowers - Le Volume Sur Printemps/FLOWERS.exe' prefix = '/home/foo/WINE/flowers' proton = 'GE-Proton' # Will use the latest GE-Proton [env] mesa_loader_driver_oveerride = 'zink' # Will use the zink driver when running the game zink_debug = 'nir,spirv,tgsi,validation'
When invoking
umu-run
from the CLI, we can omit thePROTONPATH
env to use the latest version of UMU-Proton, right? How to achieve the same thing from a TOML config file passed toumu-run
? Omittingproton
from the file does not work since it is required. And passing an empty string is also forbidden. We could specify an absolute path to~/.local/share/Steam/compatibilitytools.d/UMU-Proton-9.0-2
or similar, but that one changes for every new version of UMU-Proton.