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: 41
Popularity: 3.11
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 .. 27 28 29 30 31 32 33 34 Next › Last »

rustemb commented on 2020-11-01 17:57 (UTC)

missing vulkan-headers

loathingkernel commented on 2020-10-20 16:20 (UTC) (edited on 2020-10-20 16:20 (UTC) by loathingkernel)

@Dude803 It doesn't matter, the wine-mono version required by each wine version is hard-coded, that is why it is included and not linked to the system wine-mono.

Dude803 commented on 2020-10-20 15:48 (UTC)

There is a new version of wine-mono

loathingkernel commented on 2020-09-29 07:39 (UTC) (edited on 2020-09-29 07:40 (UTC) by loathingkernel)

@gyscos Nope, find what package requires python-tqdm and report it there. Building this one doesn't directly depend on it.

gyscos commented on 2020-09-29 00:18 (UTC)

Seems like I had to install python-tqdm to be able to build, should it be added to the make-depends?

loathingkernel commented on 2020-08-08 07:48 (UTC) (edited on 2020-08-08 07:49 (UTC) by loathingkernel)

It is not a new version per se, it is a different stable branch which is also based on a previous wine version, namely 5.9, something that will require manual intervention to upgrade.

Your issue is not with this package but python-fontparts, that is what is missing the mangled dependencies, as it is explicitly stated in the log you posted.

These two things combined make me think that updating this package to a previous version will cause more confusion and the stable branch should be a different package.

MrWhiskers commented on 2020-08-08 00:04 (UTC) (edited on 2020-08-08 00:05 (UTC) by MrWhiskers)

Seems out of date again (new version released 11 days ago).

Also the current version doesn't seem to resolve for me:

==> Making package: python-fontparts 0.9.2-1 (Fri 07 Aug 2020 08:00:05 PM EDT)
==> Checking runtime dependencies...
==> Missing dependencies:
  -> python-booleanoperations
==> Checking buildtime dependencies...
==> Missing dependencies:
  -> python-fontpens
==> ERROR: Could not resolve all dependencies.

and I cannot install those individually, they seem to have dependencies on one another?

loathingkernel commented on 2020-06-26 08:59 (UTC) (edited on 2020-06-26 08:59 (UTC) by loathingkernel)

@SolarAquarion I am aware of it, rebasing the makfile and testing take time though which I don't have presently due to exams. Maybe I will find some in the near future.

SolarAquarion commented on 2020-06-25 19:46 (UTC)

there has been a updated version

atxnor commented on 2020-06-17 08:57 (UTC)

@Plexcon before build this pkg use this: yay -i mingw-w64-gcc-bin

« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 Next › Last »