Path configuration

[TDGalea]

Hello there.

Please accept my apologies if you're unable to help here, but I've tried all sorts of combinations when editing the paths contained within the script and I cannot for the life of me get wstart to see the Proton versions along with the games.
Now, don't get me wrong - I know I've got an odd setup here. I've got multiple install drives and thanks to that, two different locations to deal with. But I'm hoping this might be okay, and I'm just getting something wrong.

The split comes from the fact that the proton version I want to use is at "/mnt/2TB/Games/steamapps/compatdata" while the game is installed at "/mnt/2TBext4/Games/steamapps/common".

Is this an impossible situation for wstart, or have I just managed to avoid the correct combination of paths?

Thanks!

[noabody]

pntop="$HOME/.steam"
# top level linux steam dir
pnapp="$pntop/steam/steamapps"
# steamapps subdir
pnbin="$pnapp/common"
# proton subdir normally under top/app
pnpfx="$pnapp/compatdata"
# proton prefix subdir normally under top/app

You can see that each variable adds to one another in that pnapp references $pntop, pnbin references $pnapp, etc. Strictly speaking, if we were to expand all the variables, it would look like this:

pntop="$HOME/.steam"
# top level linux steam dir
pnapp="$HOME/.steam/steam/steamapps"
# steamapps subdir
pnbin="$HOME/.steam/steam/steamapps/common"
# proton subdir normally under top/app
pnpfx="$HOME/.steam/steam/steamapps/compatdata"
# proton prefix subdir normally under top/app

Your proton version is going to be pnbin and your proton environments (wine prefix) will be in pnpfx. Your games are probably in pnbin="$HOME/.steam/steam/steamapps/common" but it doesn't matter. What matters is how you're trying to launch a game. Is it with wstart -ps, which should menu all of the installed games and launch with Steam, or wstart -pp.

wstart -pp would be a problem since it only finds programs installed within a wine prefix and Steam never installs the game within the prefix. wstart -pp needs the full path to a game so it would look something like wstart -pp ~/.local/share/Steam/steamapps/common/Oblivion/Oblivion.exe or wstart -pp ~/.local/share/Steam/steamapps/common/Oblivion which would generate a menu of the executable files in that path.

You could even use wstart -pp /mnt/2TBext4/Games/steamapps/common and that would maybe generate a menu but it'd probably have a ton of entries.

Anyway, you can set pnbin (steamapps/common) and pnpfx (steamapps/compatdata) to the exact paths you want and they don't have to be the same. Once you figure out if you'd like to try wstart -pp to launch a game wstart -pu can create a shortcut on the desktop based on the desk variable.

Honestly, I suspect most users will be interested in wstart -pc which, when the variables are correct, will menu the proton version, then the prefix, common programs for maintenance such as Wine Configuration, and ask to launch as wine or proton (default). This way you can make changes to the prefix.

To give you a better idea of the order of operation for wstart -pp, I'll use this command: wstart -pp ~/.local/share/Steam/steamapps/common/Oblivion which generates this output for me, based on the games I have installed:

1) Proton 7.0/dist		3) protonge/files
2) Proton - Experimental/files	4) quit
Please enter your choice: 
3 ** we're selecting our proton and I'm using ProtonGE **

1493710  Proton Experimental
1887720  Proton 7.0
22320  The Elder Scrolls III: Morrowind
22330  The Elder Scrolls IV: Oblivion 
489830  The Elder Scrolls V: Skyrim Special Edition
1) 0/pfx	3) 1580130/pfx	5) 22320/pfx	7) 489830/pfx	9) quit
2) 1493710/pfx	4) 1887720/pfx	6) 22330/pfx	8) .client/pfx
Please enter your choice: 
6 ** we need to match the game Oblivion to its prefix, menu says 22330 is for Oblivion and that corresponds to option 6 **

1) 4gb_patch.exe	   4) OblivionLauncher.exe
2) directx/DXSETUP.exe	   5) OblivionModManager.exe
3) Oblivion.exe		   6) quit
Please enter your choice: 
3 ** choose any executable you want, I'll use Oblivion.exe, option 3 **

wine loader? [y/N] 
press return for Proton loader which is ```proton run```,  running it from wine directly would be 'y'

Of course this actually fails for me because of Steam DRM. Launching the game directly doesn't set the environment up properly. Once the game is running, though, we should be able to attach ancillary programs to the same instance. This might be good for running a game trainer or something.