That's a pretty wacky setup. I think you're largely on your own here. If you're running outside the Steam runtime, then possibly it can't find the loader executable, but that's just a guess.
If you're running outside the Steam runtime, then possibly it can't find the loader executable,
Noted @aeikum. Where exactly can I find the loader executable? I'm still very new to this and its taking some time to know the ropes.
Also, just to clarify...
I assumed that the directories .proton and Proton 4.11 are all that's needed to run Proton standalone.
I mentioned the above in my original post.
Is this assumption correct?
I looked a tiny little bit into this.
"This is not possible since the wine executable does exist in the /dist/bin/ location."
The file not found error could be a bit misleading (errors can at times be very misleading). eg "Raised when a file or directory is requested but doesn’t exist."
https://docs.python.org/3/library/exceptions.html#FileNotFoundError
There are possibly other situations with that depending on what the code is doing. One way or another, it cannot find the file from what or where it is.
For example, in this situation
the person recommends "OR, Python doesn't have the permissions to access the files at that path…". That is not to say the file's perm could be correct but Python (not you) must be able to access the full path as well. If it can't then can you say that the file is not found? Yes.
There are other weird things that can happen though such as if the code knows the full path but uses relative path eg "../someFolder/someFile".
I'm not sure of all the values its holding or if its using full vs relative paths etc. Didn't really look at it that way. Just pointing out some things.
Seconding this.
I am running on NixOS. Both the steam distributed 4.11 and 5.0 give this error.
proton 4.11x2 2020-03PROTON_NO_ESYNC=1x1 2020-03PROTON_USE_WINED3D11=1x1 2020-03STEAM_COMPAT_DATA_PATH=$PWD/.protonx1 2020-03STEAM_COMPAT_DATA_PATH=~/.proton/x1 2020-03
Proton version: 4.11
I've been testing out different (non-steam) game executables using the following proton terminal command.
STEAM_COMPAT_DATA_PATH=~/.proton/ ~/.steam/steam/steamapps/common/Proton\ 4.11/proton run ./game-file.exeAt first, I tested in my PC (running Ubuntu 18.04) which I had pre-installed Steam on. The command worked as intended and Proton handled most games I threw at it.
Then I thought of running a VM instance on Azure (Ubuntu 18.04) and seeing if I can replicate the functionality.
Based on the previously mentioned command above I assumed that the directories .proton and Proton 4.11 are all that's needed to run Proton standalone. So I extracted those 2 folders separately, put them in a single directory and re-ran my command via a bash script (accounting for the changes in location). It worked fine in my local machine.
That script is as follows:
But as soon as I run it on the Azure VM, I get the following error:
This is not possible since the wine executable does exist in the /dist/bin/ location.

Assuming it was something to do with Azure's VM, I thought of recreating an exact environment in my local machine via VirtualBox (using an Ubuntu 18.04 iso) and retrying.
Alas, the results were the same.
I'm assuming this means there are other directories or files that I haven't accounted for which are being utilized by the command, although not explicitly mentioned.
My questions are;
**Please note that this version of Proton I've used was not built from source, rather it was the one extracted from
~/.steam/steam/steamapps/common