-
-
Notifications
You must be signed in to change notification settings - Fork 440
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
Apply protonfixes to all proton types #4140
Comments
I think UMU still breaks the winetricks commands, right? I know we run the known fixes for all wines/protons when possible (like it won't run for things like crossover), but I think winetricks currently fails if UMU is enabled |
hmm.. I'm able to run winetricks just fine from the settings tab |
@imLinguin interesting, that button is actually already pressed and it is still not working. I ran the winetricks manually and then it worked on proton bleeding edge. |
I tried again reinstalling the game and the problem disappeared. I downloaded the game twice and it worked flawlessly. I have no idea what have happened to this game the first two times I downloaded it and I couldn't get it to work. I think this is an issue on my end hahaha. Thanks for all the help anyways! |
Problem description
I tried to open Thief game yesterday and it gave me some errors: Thief crashing on startup after 5 seconds of black screen. I opened an issue on VKD3D thinking that was a problem on their implementation of the d3dcompiler, but actually it was just missing one dependency.
Feature description
I would like to ask if it is possible to auto download and install all necessary dependencies automatically for all proton or wine versions (ex.: proton-ge, wine-ge, wine and steam proton). Heroic has already a repo containing Know-Fixes and it is just a matter of installing this fix even when not using wine-ge and it should fix this game for everyone. Applying the winetricks that is already available would help everyone that does not know how to install dependencies on heroic games launcher.
Alternatives
No response
Additional information
I saw more people lost on how to solve this issue on protondb as well. The two most recent comments for example:
The text was updated successfully, but these errors were encountered: