Skip to content
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

Proton-TkG doesn't run with umu-launcher both in lutris and with only umu-launcher #99

Closed
s0mebodyhelpme opened this issue May 4, 2024 · 6 comments

Comments

@s0mebodyhelpme
Copy link

When running with a proton build made with Frogging-Family's proton-tkg, the following is always displayed with both just umu-launcher and with the symlink method mentioned in #88 :

wine: could not load ntdll.so: /home/al/.local/share/Steam/compatibilitytools.d/proton_tkg_experimental.bleeding.edge.9.0.94733.20240504/files/lib/ntdll.so: cannot open shared object file: No such file or directory

in any game. however, it works with the latest GE-Proton given by lutris. upon inspection, though, it does seem that the file and folder structure are the same for both proton builds. how this occurs on TkG and not GE is odd to me.

Many thanks for the hard work on this project and consideration given to my issue, if any! and kindly feel free to ask for details if necessary!

@R1kaB3rN
Copy link
Member

R1kaB3rN commented May 4, 2024

Actually, the folder structures are not the same because there isn't a wine subdirectory in the path you listed. Here's an example of GE-Proton's build of the to the ntdll.so file:

./GE-Proton9-4/files/lib/wine/i386-unix/ntdll.so
./GE-Proton9-4/files/lib64/wine/x86_64-unix/ntdll.so

Do all proton-tkg builds not contain that subdirectory?

@R1kaB3rN
Copy link
Member

R1kaB3rN commented May 4, 2024

Also, do you know if Proton builds made with Frogging-Family's proton-tkg are specifically designed to run natively? If so, this is not supported and I don't really find it odd that you're experiencing issues as the proton-tkg's script and upstream's Makefile build Proton differently and have different expectations.

@loathingKernel
Copy link
Contributor

Also, do you know if Proton builds made with Frogging-Family's proton-tkg are specifically designed to run natively?

This is most likely the case indeed. I am looking through the build scripts of proton-tkg and all things point towards it being built outside of Steam Linux Runtime.

@s0mebodyhelpme
Copy link
Author

s0mebodyhelpme commented May 5, 2024

@R1kaB3rN , it seems that my initial inspection was a bit off. Sorry. It turns out that, within the wine subidrectory of lib directory under files, the ntdll.so file exists within i386-unix, just like the latest GE Proton which works (at least my copy). Here are screenshots of the subdirectories for both Proton vesions for you to look at:

05-05-2024+11:41:35
05-05-2024+11:41:40
05-05-2024+11:42:06
05-05-2024+11:42:13

@R1kaB3rN
Copy link
Member

R1kaB3rN commented May 5, 2024

Thanks for re-confirming the directory structure for me.

However, even if the directory structures are the same, the two Proton builds will be built differently. Examining the proton-tkg build script, it will call run.sh then proceed to build Proton (wine) build against the Scout runtime as well as some of the host libraries instead of against the Sniper platform within a container. Using custom builds of Proton this way is not official, and will result in issues and differences when running inside Pressure Vessel. This will apply to Lutris or just any launcher that uses umu as its runtime, and this is currently out of scope for this project because the goal is to run games the way Valve does using official builds.

Therefore, I'll have to close this issue.

@R1kaB3rN R1kaB3rN closed this as completed May 5, 2024
@R1kaB3rN
Copy link
Member

R1kaB3rN commented May 5, 2024

In the future though, I might add a feature to allow not using Pressure Vessel. However, this feature would be strictly for debugging purposes, so any issues reported with that setting enabled will be closed instantly and users will be on their own.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants