Package Details: proton-ge-custom 2:GE.Proton9.4-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: 37
Popularity: 0.32
First Submitted: 2020-03-23 23:52 (UTC)
Last Updated: 2024-04-15 17:30 (UTC)

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

1 2 3 4 5 6 .. 33 Next › Last »

corax2.05 commented on 2024-04-03 15:08 (UTC)

@loathingkernel That works. Thank you very much for your effort!

loathingkernel commented on 2024-03-27 18:38 (UTC)

@CucumberSpace What can I do about a network issue on your side exactly?

  [28] Timeout was reached (Operation too slow. Less than 10 bytes/sec transferred the last 30 seconds)

This looks obvious to me

loathingkernel commented on 2024-03-27 18:36 (UTC) (edited on 2024-03-27 18:37 (UTC) by loathingkernel)

@corax2.05 From latest pacman changelog

              - makepkg:
                - Add checksum support for git/mercurial/bzr sources

In the last release the checksums now also contain the sha256sum of the git repository.

Either wait for Manjaro to update pacman or edit the PKGBUILD and replace the checksum of the repository with 'SKIP'

CucumberSpace commented on 2024-03-27 16:50 (UTC) 

error: failed to get `miniz_oxide` as a dependency of package `png v0.17.13`
    ... which satisfies dependency `png = "^0.17.2"` of package `gst-plugin-png v0.9.11 (/home/cucumbersp/.cache/yay/proton-ge-custom/src/proton-ge-custom/gst-plugins-rs/video/png)`

Caused by:
  failed to query replaced source registry `crates-io`

Caused by:
  download of mi/ni/miniz_oxide failed

Caused by:
  failed to download from `https://index.crates.io/mi/ni/miniz_oxide`

Caused by:
  [28] Timeout was reached (Operation too slow. Less than 10 bytes/sec transferred the last 30 seconds)
==> ERROR: A failure occurred in prepare().

corax2.05 commented on 2024-03-25 16:25 (UTC)

you are right, it's Manjaro. I cleand the folder and there is enough free space. System is up to date.

The build before some weeks runs fine.

The downloaded files in proton-ge-custom are: 0001-AUR-Pkgbuild-changes.patch 0002-AUR-Do-not-update-cargo-crates.patch 0003-AUR-Remove-kaldi-openfst-vosk-api-modules-because-of.patch 0004-AUR-Copy-DLL-dependencies-of-32bit-libvkd3d-dlls-int.patch 0005-AUR-Strip-binaries-early.patch 0006-AUR-Fix-hwnd-redefinition.patch PKGBUILD proton-ge-custom proton-ge-custom.install src wine-gecko-2.47.4-x86_64.tar.xz wine-gecko-2.47.4-x86.tar.xz wine-mono-9.0.0-x86.tar.xz I'm the owner and permissions are -rw-r--r-- The other files where found at the build... that seems strange.

xiota commented on 2024-03-23 23:57 (UTC)

When all else fails, try building in a clean chroot.

loathingkernel commented on 2024-03-23 23:17 (UTC) (edited on 2024-03-23 23:25 (UTC) by loathingkernel)

@xiota indeed the error looks weird, but if it was a download problem it would fail earlier when the git sources were updated, if it was a permissions problem it would also happen when the sources were pulled as git wouldn't be able to write them on disk. I do not know how it would behave if not enough free space was available, but I guess git would fail in this case too.

Given that the sources are in a folder named proton-ge-custom, if previous pacman checked only the checksum of files and not folders, it stands to reason to report that a "file" named proton-ge-custom was not found despite successfully downloading the sources.

xiota commented on 2024-03-23 21:58 (UTC)

The error message says the files/folders NOT FOUND. That is not a Manjaro problem. Most likely permissions, free space, or download problems.

loathingkernel commented on 2024-03-23 21:31 (UTC) (edited on 2024-03-23 21:31 (UTC) by loathingkernel)

@corax2.05 my guess is that you are using manjaro, which has the stupid practice of holding back packages, in this case pacman that's why it fails to validate the checksum for the VCS sources for proton-ge-custom repo. That's a problem with your distribution, not this package.

That or you haven't updated your system in the past week.

corax2.05 commented on 2024-03-23 17:49 (UTC) (edited on 2024-03-23 17:50 (UTC) by corax2.05)

hm... I can't see what the problem is.

Building proton-ge-custom... ==> Making package: proton-ge-custom 2:GE.Proton9.2-1 (Sa 23 Mär 2024 18:45:55 CET) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Cloning proton-ge-custom git repo... Cloning into bare repository '/var/tmp/proton-ge-custom/proton-ge-custom'... -> Downloading wine-gecko-2.47.4-x86.tar.xz... % Total % Received % Xferd Average Speed Time Time Time Current

CUT

99 39.0M 99 38.7M 0 0 5570k 0 0:00:07 0:00:07 --:--:-- 6003k 100 39.0M 100 39.0M 0 0 5576k 0 0:00:07 0:00:07 --:--:-- 6004k -> Found 0001-AUR-Pkgbuild-changes.patch -> Found 0002-AUR-Do-not-update-cargo-crates.patch -> Found 0003-AUR-Remove-kaldi-openfst-vosk-api-modules-because-of.patch -> Found 0004-AUR-Copy-DLL-dependencies-of-32bit-libvkd3d-dlls-int.patch -> Found 0005-AUR-Strip-binaries-early.patch -> Found 0006-AUR-Fix-hwnd-redefinition.patch ==> Validating source files with sha256sums... proton-ge-custom ... NOT FOUND wine-gecko-2.47.4-x86.tar.xz ... Passed wine-gecko-2.47.4-x86_64.tar.xz ... Passed wine-mono-9.0.0-x86.tar.xz ... Passed 0001-AUR-Pkgbuild-changes.patch ... Passed 0002-AUR-Do-not-update-cargo-crates.patch ... Passed 0003-AUR-Remove-kaldi-openfst-vosk-api-modules-because-of.patch ... Passed 0004-AUR-Copy-DLL-dependencies-of-32bit-libvkd3d-dlls-int.patch ... Passed 0005-AUR-Strip-binaries-early.patch ... Passed 0006-AUR-Fix-hwnd-redefinition.patch ... Passed ==> ERROR: One or more files did not pass the validity check! Failed to build proton-ge-custom

1 2 3 4 5 6 .. 33 Next › Last »