-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues when using Protontricks #6
Comments
Not out of scope at all! This program is supposed to work with all setups involving Steam, including Proton stuff. Could you run the enforcer in debug mode and send here the output, please? |
This'll take me a while, looks like I nuked half my Steam installation by accident and have to restore a couple things before I can get back to you. In the meantime, could I just clarify again what to look for? Would anything involving that exact Steam runtime path be the thing to keep an eye out for in the debug log? |
Pretty much. Once you find the line(s), you can just scroll up to check whether there are other relevant ones. |
Managed to get the following:
Since the full log, even after only about half a minute of runtime, was about 100MB in size, I've uploaded the rest of it here. |
I checked the relevant lines in the full log and didn't spot any obvious issues, I would check with |
I can't say I've ever used |
Were you able to gather info through |
Afraid not, I haven't gotten around to that yet and it seems a bit above my level of expertise. Sorry. |
Figured I'd post another issue report, though as per the accompanying email I sent regarding this I wasn't sure whether this was still in scope.
I came across a couple of issues with tools like Protontricks when the enforcer is up and running. Firstly, every installed Proton game seems to be listed twice:
Further to that, configuring these games does not seem to work when using the enforcer as part of the script back in #4. As an example, when trying to install the
d3dx9_43
verb for BIT.TRIP CORE (app ID 205060), Protontricks simply returns the following output before hanging indefinitely:The text was updated successfully, but these errors were encountered: