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

loathingkernel commented on 2020-11-19 20:43 (UTC) (edited on 2020-11-19 21:03 (UTC) by loathingkernel)

@randyzhu No it should not, definitely should not. I have thought about it but GE's git habits are messy to say least, and it makes it almost impossible to follow different branches. Releases are tagged before the final version, sometimes at the start of the release but not always, branches are getting merged and reused for different things, branches that per their title do the same thing, and changes from upstream proton are merged by hand rather than rebasing or cherry-picking. All this make it really hard to follow what commit/branch each release refers to. That is why this package always follows the latest release by date of release rather than version number or branch.

gyscos commented on 2020-11-19 20:38 (UTC) (edited on 2020-11-19 20:58 (UTC) by gyscos)

Well, without any vkd3d installed (is that what you wanted me to try?), I get unsurprisingly:

../../proton-ge-custom/wine/dlls/d3d12/d3d12_main.c:39:10: fatal error: vkd3d.h: No such file or directory
   39 | #include <vkd3d.h>
      |          ^~~~~~~~~

Full log: https://gist.github.com/e167b24d6a3ff8984d1556c331b3cf5e

Now trying after installing community/vkd3d=1.2. At least its /usr/include/vkd3d/vkd3d_shader.h file does seem to include the proper type definitions...

randyzhu commented on 2020-11-19 20:22 (UTC)

Is this package based on stable releases or pre-releases? If it's based on the stable version, this package should be renamed to proton-ge-custom-stable, and another pre-release package should be called proton-ge-custom.

loathingkernel commented on 2020-11-19 20:04 (UTC) (edited on 2020-11-19 20:07 (UTC) by loathingkernel)

Actually no, you are onto something. Since the last proton update vkd3d is compiled separately as a Windows dll rather than built-in in wine, hence proton's vkd3d is not available prior to building wine and the system one is used. If you try again, can you temporarily remove vkd3d altogether before building and see if it happens? If it works, I will disable wine's vkd3d to accommodate such potential issues as proton doesn't need it anyway.

gyscos commented on 2020-11-19 19:42 (UTC) (edited on 2020-11-19 19:44 (UTC) by gyscos)

The full log is pretty big (much larger than my terminal history), will need to re-build to get it.

In the meantime I think it might be because I have aur/vkd3d-valve=1.1-2 rather than community/vkd3d=1.2? Seems to be where PFN_vkd3d_shader_compile is defined.

EDIT: nevermind, I guess it uses the include from the vkd3d-proton submodule and just ignores my system one.

loathingkernel commented on 2020-11-19 19:15 (UTC) (edited on 2020-11-19 19:17 (UTC) by loathingkernel)

Could you post the complete log somewhere? This is not happening here. A dependency might be missing or it could be something else, I can't know without the complete log.

gyscos commented on 2020-11-19 19:00 (UTC)

Getting some errors building this package (many build errors, here are the first few ones):

../../proton-ge-custom/wine/dlls/wined3d/shader_spirv.c:34:8: error: unknown type name ‘PFN_vkd3d_shader_compile’
   34 | static PFN_vkd3d_shader_compile vkd3d_shader_compile;
      |        ^~~~~~~~~~~~~~~~~~~~~~~~
../../proton-ge-custom/wine/dlls/wined3d/shader_spirv.c:35:8: error: unknown type name ‘PFN_vkd3d_shader_free_messages’
   35 | static PFN_vkd3d_shader_free_messages vkd3d_shader_free_messages;
      |        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../proton-ge-custom/wine/dlls/wined3d/shader_spirv.c:36:8: error: unknown type name ‘PFN_vkd3d_shader_free_scan_descriptor_info’
   36 | static PFN_vkd3d_shader_free_scan_descriptor_info vkd3d_shader_free_scan_descriptor_info;
      |        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../proton-ge-custom/wine/dlls/wined3d/shader_spirv.c:38:8: error: unknown type name ‘PFN_vkd3d_shader_get_version’
   38 | static PFN_vkd3d_shader_get_version vkd3d_shader_get_version;
      |        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~

PedroHLC commented on 2020-11-01 18:40 (UTC)

@loathingkernel it fails to build in a clean chroot without it, so you just need to add it to makedepends...

In file included from .././syn-vrclient32/vrclient/vrclient_main.c:19:
.././syn-vrclient32/vrclient/dxvk-interop.h:39:10: fatal error: vulkan/vulkan.h: No such file or directory
   39 | #include <vulkan/vulkan.h>
      |          ^~~~~~~~~~~~~~~~~
compilation terminated.

loathingkernel commented on 2020-11-01 18:12 (UTC)

@rustemb care to elaborate on that? Is it failing to build? And with what error?

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