-
-
Notifications
You must be signed in to change notification settings - Fork 268
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
[Bug]: Proton not able to run apps with WineD3D, missing dependencies #3485
Comments
This is still an issue on the latest Bottles. I don't believe I ever saw this issue before 51.13/51.12/51.11. However, I did downgrade to 51.10 for testing and still saw the problem. Attempted multiple versions of the Proton-GE runner (with and without the Steam runtime), and it still resolves the above error. And to clarify, it doesn't need to start as a Proton bottle to experience the problem; swapping an existing Wine runner to a Proton runner will exhibit the problem. Some games I tested: NFS: Underground, The Sims: Complete Edition, LEGO Island. I also tested a non-Flatpak version of Bottles (nix package), and the same problem was there. My debugging info:
|
explains why ge-proton doesn't launch applications for me but sys-wine does(No vulkan available on laptop, explicitly vulkan disabled via UI options) |
@keenanweaver I'm trying to test something with the ProtonGE runner right now and I can't see the checkbox in any bottle -> settings -> compatibility to enable the additional Steam runtime. Should it just be in there under compatibility or does anything else have to be done for the option to enable / disable the runtime show up? Cheers |
Nope, neither the Bottles runtime nor the Steam runtime checkbox is there for me. I just installed bottles freshly on Ubuntu 24.10 and let it install ProtonGE but the two entries in your screenshot are not there. I can see the rest though. |
|
This is the current git version, so no idea why yours would be different unless it was out of date. 🤷 |
Hm, I'm on version 51.15, which should be the newest stable build on Flathub. I'll install it on my secondary pc with Suse and check if the same thing happens here too. |
Ok, tested on Suse and it's the same thing there, both options are missing in my bottles. Does anyone have the current stable version from Flathub installed by any chance? If it's a bug we can file a bug report then. |
At least for me, I needed to install the flatpak version of Steam and launch it once so it downloads the runtime (no need to log in). After that, Steam runtime becomes an option in Bottles. From my experience, a native Steam install won't provide the runtime to Bottles. The Bottles runtime is missing altogether for me. |
I have Steam Flatpak installed in both cases (Ubuntu and openSUSE), and both have Steam runtime 3.0 sniper installed. So Bottles takes the runtime from a preinstalled Steam installation? I always thought it was bundled and included with the Bottles Flatpak (or that it would download it after enabling it via checkbox). If this is the case, might I need to give Bottles permission to access Steam Flatpak via Flatseal maybe? I ask because checking Bottles -> settings -> Steam Proton prefix it tells me that I can't enable that feature, because it couldn't find Steam due to lacking permissions etc. Edit: Thanks for checking @james2432 |
Yeah, I may be full of it 'cause I just wiped out the Steam flatpak and directory altogether, created a new bottle, and the runtime shows up. No idea why this differs from my previous attempts. It even shows up on runners like Soda, when it didn't before. Still no Bottles runtime, though. I manage my permissions through NixOS, so no idea why it's different now. |
That's interesting. I checked the Bottles doc to see if it has any info on how to enable the runtimes or how it works exactly, but didn't find anything relevant. Maybe @mirkobrombin can help us out here? |
Has anyone been able to pin point why the runtime options are missing for some of us on Arch and Suse? |
Sounds like a separate issue from the one being discussed right now. If it's a problem, you should write a separate issue about it rather than hijacking this thread. |
Same here for me.. Wanted to test some Proton-GE since i have issues with EAC on the Game "Deceive Inc." Epic just gave away. Was searching for where to enable "steam runtime" found this thread, checked compability: Nothing. Just like #3485 (comment) Do you need to enable Steam Proton Prefixes for that to appear? |
Proton must always be used with the Steam runtime enabled. Bottles show that option only if steam is found in the common paths. |
Thanks for taking the time, Mirko. So do we have to grant Bottles access to the Steam Flatpak path via Flatseal or is it done any other way? Or should Bottles auto-detect Steam just by having Steam Flatpak installed? |
Correct. You have to give it access to the Steam path, according to its installation method. |
That worked like a charm, thank you! Steam runtime is available now (checkbox for the Bottles runtime is still missing though). PS: It would be nice if both could be bundled with the Bottles Flatpak for ease of use. Cheers |
Describe the bug
When running a prefix using Proton instead of Wine, if an app uses WineD3D (namely anything that uses DirectDraw/
ddraw.dll
), Proton will not be able to run it due to missing two libraries:libvkd3d-1.dll
&libvkd3d-shader-1.dll
. The issue is only resolved by falling back to a different version of Wine rather than Proton - alternatively, symlinking/copying the files to$PREFIX/drive_c/windows/[system32/syswow64]
resolves the issue for Proton and the application will run.For what it's worth, the libraries are included in
{PROTON}/files/lib[64]/vkd3d
Tested with GE-Proton9-11 downloaded from inside Bottles, and Proton - Experimental symlinked from a working Steam install.
To Reproduce
wined3d.dll
rather than DXVK/VKD3D.Package
Flatpak from Flathub
Distribution
Arch Linux
Debugging Information
Troubleshooting Logs
Additional context
I've mostly noticed this with regards to apps using DirectDraw in some form, and it applies to a few different games, mainly older titles (like the 1998 PC port of Final Fantasy VII).
The text was updated successfully, but these errors were encountered: