When you add a custom.exe to steam, steam should automatically set that as protonexperimental. The file extension and the OS should be enough of a hint to steam.
If the game is called Game.exe (99% of all rpg maker games are) - the added game should adopt a name based on the folder where the game is instead of the filename.
If this is not something valve is interested in improving, may I ask if steam client can get some hooks to do it via a bash script?
To make things even more annoying, when you first set proton on a custom executable, steam sets something else. You have to select proton experimental twice every time.
The process sucks:
add exe to steam
find your exe among other Game.exe files
select properties
rename it to something that can be recognised
set it to use proton experimental
do 5 again - because steam client still has this very obvious bug
close the properties
play your game
8 steps!
8.
If you give us a single command to do this or improve the current one, that would make adding custom game executables to steam so much less tedious
When you add a custom.exe to steam, steam should automatically set that as protonexperimental. The file extension and the OS should be enough of a hint to steam.
If the game is called Game.exe (99% of all rpg maker games are) - the added game should adopt a name based on the folder where the game is instead of the filename.
If this is not something valve is interested in improving, may I ask if steam client can get some hooks to do it via a bash script?
addtosteam gamepath --use-proton-experimental --use-game-folder-for-nameTo make things even more annoying, when you first set proton on a custom executable, steam sets something else. You have to select proton experimental twice every time.
The process sucks:
8 steps!
8.
If you give us a single command to do this or improve the current one, that would make adding custom game executables to steam so much less tedious