Package Details: proton 6.3.5-1

Git Clone URL: https://aur.archlinux.org/proton.git (read-only, click to copy)
Package Base: proton
Description: Compatibility tool for Steam Play based on Wine and additional components
Upstream URL: https://github.com/ValveSoftware/Proton/
Licenses: BSD
Submitter: Forty-Bot
Maintainer: somebody
Last Packager: somebody
Votes: 78
Popularity: 1.94
First Submitted: 2018-08-22 01:23
Last Updated: 2021-06-27 06:39

Pinned Comments

heavysink commented on 2020-07-31 01:35

I haven't found a solution to this for now... I cannot compile it due to 'wine_dlsym' I think it is from upstream after updating wine-valve.

EDIT: proton-git still have this problem... I submitted an issue on Github: https://github.com/ValveSoftware/Proton/issues/4108

MagicAndWires commented on 2019-11-01 16:06

To the people getting the wine/wined3d-interop.h: No such file or directory the 4.17 proton requires a wine-valve version >=4.16, install wine-valve-git instead.

Update:
After some consideration, because new versions of proton require code that has not been released as a stable version yet any kind of "stable" package for wine-valve is going to be hell to maintain and always lagging slightly behind.

If anyone wants to continue a stable package despite this, I've disowned the package so you're welcome to give it a shot, but I'd advise users to just install wine-valve-git instead.

(No changes to the proton PKGBUILD necessary).

Forty-Bot commented on 2018-08-22 01:24

This is in an early state right now. vrclient_x64 needs the custom bundled version of wine, which I plan to make another package for. For now all that's packaged is lsteamclient.

Latest Comments

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

somebody commented on 2021-06-26 01:23

oops... not sure how i didn't notice the edit. re: transition... not quite sure tbh. i guess the only thing that may be a problem is a possible conflict re: the proton executable? i have it somehow, no idea what's providing it. pacman says it's owned by an old version of proton-ge-custom which is a bit odd

edit: other than that it should be fine? given that proton-native is (i'm assuming) basically this (so a drop-in replacement) but with... actual proton

loathingkernel commented on 2021-06-10 10:14

fwiw might want to look into replacing proton-git too?

I don't think it is needed. They push updates to their git only on releases. Maybe a package like proton-experimental tracking the experimental releases would be useful.

EDIT: if you are ok with it, how do you think we should handle the transition?

somebody commented on 2021-06-10 04:57

i just make sure it builds, so no complaints here. don't think my system can handle building the entire thing anyway. fwiw might want to look into replacing proton-git too?

loathingkernel commented on 2021-06-09 20:00

The original plan was to package proton itself. But that never came about.

I tried to do that split package for proton myself but due to the need for extensive patching and that I wanted to provide something that was as close as possible to the upstream package I decided to just patch it to the point that it built without issues instead of splitting it.

If you package proton-native provides the proton binary, then IMO it should replace this package.

It works and function just like proton from valve for all intents and purposes, just built on Arch libraries and without the need for the Valve runtime. It is one big monolithic thing that includes everything the upstream package would.

Forty-Bot commented on 2021-06-09 19:53

I want to ask, why is this named proton since it doesn't provide the main proton executable and it can't be used through steam?

The original plan was to package proton itself. But that never came about.

I am asking because I maintain a complete proton package but the name proton-native that I am using already exists as a React framework and it might cause confusion or issues in the future.

If your package proton-native provides the proton binary, then IMO it should replace this package.

loathingkernel commented on 2021-06-09 19:48

I want to ask, why is this named proton since it doesn't provide the main proton executable and it can't be used through steam? This looks to me more like a joint package of lsteamclient and vrclient from proton rather than a working proton for Arch.

I understand the usefulness of these components but I think this is misleading. I am asking because I maintain a complete proton package but the name proton-native that I am using already exists as a React framework and it might cause confusion or issues in the future.

somebody commented on 2021-05-01 06:31

updated to 6.3, it works fine for me but looking at the comments i can't be 100% sure, please comment if it doesn't work

heavysink commented on 2021-05-01 00:39

I disowned the package. I just cannot make it to work...

Anyone please try anything that may solve the problem for compilation. A possible way: https://github.com/ValveSoftware/Proton/issues/4108

EgidioCaprino commented on 2020-12-11 21:07

I'm getting this error when installing. Can you please help me?

heavysink commented on 2020-12-10 19:20

@ynikitenko update is on the way. I think you just ask each game to use custom proton and point it to the installed proton.