Package Details: proton-ge-custom 2:GE.Proton9.22-1

Git Clone URL: https://aur.archlinux.org/proton-ge-custom.git (read-only, click to copy)
Package Base: proton-ge-custom
Description: Compatibility tool for Steam Play based on Wine and additional components, GloriousEggroll's custom build
Upstream URL: https://github.com/GloriousEggroll/proton-ge-custom
Keywords: dxvk proton steam valve vkd3d wine
Licenses: custom
Provides: proton
Submitter: loathingkernel
Maintainer: loathingkernel
Last Packager: loathingkernel
Votes: 40
Popularity: 2.15
First Submitted: 2020-03-23 23:52 (UTC)
Last Updated: 2024-12-30 14:02 (UTC)

Dependencies (117)

Required by (7)

Sources (12)

Pinned Comments

loathingkernel commented on 2023-10-12 10:43 (UTC) (edited on 2023-10-12 10:45 (UTC) by loathingkernel)

@rekman, thank you for looking into CUDA issues, at least it gives me an idea on how to fix it. That being said, my position remains to build it in a clean chroot, away from the locally installed packages. It is not feasible for me to carry patches for the build systems of various subprojects in the long run.

By enabling the 0003-AUR-Remove-kaldi-openfst-vosk-api-modules-because-of patch, you lose voice recognition which I assume is not that big of a loss as I haven't encountered a use for it, so I think it is an acceptable alternative.

patlefort commented on 2022-09-22 00:33 (UTC)

Compilation will fail if you happen to have jwasm installed, due to vulkan loader. Workaround: uninstall jwasm or add this line to prepape() in the PKGBUILD:

sed -i 's/VULKAN_LOADER_CMAKE_ARGS = -DUSE_MASM=OFF/VULKAN_LOADER_CMAKE_ARGS = -DUSE_MASM=OFF -DJWASM_FOUND=0/' "$srcdir/$pkgname/Makefile.in"

loathingkernel commented on 2020-11-21 10:28 (UTC) (edited on 2022-09-13 10:55 (UTC) by loathingkernel)

Notes about this package

  • If you encounter issues while using this package, please contact me here first before reporting an issue to the upstream repository.

  • Don't post logs, link to them. If you are using Manjaro, another derivative or an AUR helper, please mention it, I DO NOT TEST AGAINST THEM AND I CANNOT KNOW WHAT MIGHT BE WRONG WITH THE DISTRO/HELPER OF YOUR CHOICE.

  • It takes a LOT of time and space to build. Building with multiple jobs helps but might cause builds to fail in rare cases. Be sure to have at least 16GB of RAM if you are building on tmpfs

  • It is NOT built against Steam Linux Runtime (Sniper, Soldier, etc) and as such it doesn't require it. Still, is detected by Steam and works properly (preferable through steam-native).

  • This PKGBUILD uses CFLAGS, CXXFLAGS and LDFLAGS hardcoded in the PKGBUILD itself. By default it uses the same C[XX]FLAGS as upstream, namely -march=nocona and -mtune=core-avx2. To change them you will have to edit the PKGBUILD itself. Due to the nature of this package some flags can cause it to fail to build or not function properly. I try to filter them out but it is based on testing. If you have a feeling that compile-time options are involved in the issues you are having please include them in your comment. Currently the filtered options are -fstack-protector-{,-strong,-all}(dxvk and vkd3d only), -fno-plt, -z,relro, -z,now. Also the use of AVX instructions is disabled through -mno-avx.

  • If you are not using CFLAGS and CXXFLAGS specific to your system this package won't offer much in terms of performance as the upstream build flags already target the nocona (Core2) architecture. It will possibly perform worse than upstream. The only benefits you get is not depending on steam linux runtime as well as linking to Arch libraries. If you still want to build it, you can uncomment the relevant lines in the PKGBUILD to enable CFLAGS and CXXFLAGS similar to the upstream.

  • There have been reports with afdko failing to find its dependencies during building. I can't do anything about that as I don't maintain that package. It is NOT an issue with this package and I haven't found a way to not depend on it. Please don't report fails due to afdko (or any of its python- dependencies, they are pulled in due to afdko and only used by that), it has been discussed enough. There are possible workarounds in the comments.

  • It contains a patch to store game prefixes in the main Steam Library under $HOME/.local/share/Steam/steamapps/compatdata. It helps with isolation of game prefixes between users and works around issues with shared libraries on NTFS partitions due to drive symlinks. To enable it, set the PROTON_USER_COMPAT_DATA env variable to 1.

  • This package requires a Rust 32 bit target, please run rustup target install i686-unknown-linux-gnu BEFORE posting any issues if you're using rustup.

Latest Comments

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 34 Next › Last »

loathingkernel commented on 2022-02-15 11:55 (UTC) (edited on 2022-02-15 11:55 (UTC) by loathingkernel)

@nicman23 It already is in the makedepends. Whatever issue you are having with it, is on your side.

nicman23 commented on 2022-02-15 09:31 (UTC) (edited on 2022-02-15 10:27 (UTC) by nicman23)

please add python-virtualenv to makedepends

loathingkernel commented on 2021-12-28 18:52 (UTC)

@patlefort That patch was a hack at best. The proper solution should be implemented in Steam itself and I have created a relevant bug report (there are a few more bug reports that would eventually achieve the same thing) but it was ignored.

@Freso Because of build failures that I wasn't able to resolve in time for the holidays. I will look into it again when I return to my base.

Freso commented on 2021-12-28 15:17 (UTC)

Why was 7.0rc2-GE-1 rolled back?

patlefort commented on 2021-12-28 03:29 (UTC)

I think the proton-user_compat_data.patch doesn't work with steam's autocloud. The vdf file will still be generated inside the compatdata directory in the target game library folder and saves will not be synced.

Erde commented on 2021-12-04 19:55 (UTC)

It is also trivial to change said behavior, but in that case, caveat emptor. Imho, it is better to have a package that compiles and works for most users and those seeking further customization to make relevant changes, than risk the majority to have changes just to get a working build.

loathingkernel commented on 2021-12-01 13:10 (UTC) (edited on 2021-12-01 17:24 (UTC) by loathingkernel)

@rvalles, I feel strongly that I have explained my rationale for doing so in the pinned comment and the comments in the PKGBUILD itself. I have also explained what is the point of the package in the pinned comment. If you want to address any of these points specifically, feel free to do so but in a less vague manner than the "the Arch way", because there are packages in the repos that do exactly that if it is required.

rvalles commented on 2021-12-01 12:29 (UTC) (edited on 2021-12-01 12:29 (UTC) by rvalles)

I feel strongly that the PKGBUILD should not override my makepkg.conf C[XX]FLAGS. This is not the Arch way.

There's little point to building this relative to -bin if it isn't to target my own machine.

theriddick commented on 2021-11-13 06:49 (UTC)

If I build this; is it grabbing the latest MASTER or just the 19+ day old 6.20-1????

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 34 Next › Last »