Package Details: proton 4.11.11-3

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: PrinceMachiavell
Last Packager: PrinceMachiavell
Votes: 65
Popularity: 1.16
First Submitted: 2018-08-22 01:23
Last Updated: 2019-12-19 22:03

Pinned Comments

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

« First ‹ Previous 1 2 3 4 5 Next › Last »

Forty-Bot commented on 2018-11-11 00:33

@Kiwii as far as I can tell, vrclient depends on headers which are not present in other versions of wine.

Kiwii commented on 2018-10-24 17:32

@Tom_B, at this time, the package only builds lsteamclient.dll.so (in 32 and 64 bit), not Wine or the Proton run script.

From my understanding, this should be the library that allows a game run in regular Wine to communicate to the native Steam client, but I couldn't figure out how to set it up either. (And I lost my motivation to tinker with it when Valve updated Proton's Wine to 3.16)

Tom_B commented on 2018-10-01 09:14

Am I being stupid here? I've installed the package but don't know how to execute it:

$ proton bash: proton: command not found

$ wine --version wine-3.16 (Staging)

which is the version I already had installed. How do I launch proton?

Kiwii commented on 2018-09-27 20:53

What's the required setup to make an application in a prefix be able to use this lsteamclient.dll.so to communicate with the native Steam client?

Do I have to copy the stuff from the native Steam client's legacycompat directory somewhere into the prefix or the game folder?

greyltc commented on 2018-09-09 11:37

@Forty-Bot,

It would be difficult to replace the built-in version of proton which comes with steam. I will look into it when I've managed to integrate all existing components.

That comment seems to disagree with what Valve has written in their blog on 21 Aug 18 here: https://steamcommunity.com/games/221410/announcements/detail/1696055855739350561

If you're familiar with building open source projects, you can even make your own local builds of Proton; the Steam client has support for using those to run games in lieu of the built-in version...

Forty-Bot commented on 2018-08-29 03:21

Proton is built on top of a modified version of wine.

Correct.

This modified version of wine uses a library that is not built in any other version of wine, so proton won't work with other wine versions

vrclient depends on a header file which isn't present. I don't know if there is any additional functionality beyond that which isn't in standard wine.

You're planning to isolate this library (vrclient) so this package can be built with any wine version?

No. As Proton needs a custom version of wine, it currently can only be built with valve's wine patches. If these get merged upstream, then it is possible it could be built with other versions of wine in the future.

Also, once this package is compiled, how do I make Steam Play utilize it?

It would be difficult to replace the built-in version of proton which comes with steam. I will look into it when I've managed to integrate all existing components.

TankMissile commented on 2018-08-29 02:37

@Forty-Bot So let me get this straight. Proton is built on top of a modified version of wine. This modified version of wine uses a library that is not built in any other version of wine, so proton won't work with other wine versions. You're planning to isolate this library (vrclient) so this package can be built with any wine version? I hope that is the case, because I'd really like to test this out with wine-staging. Also, once this package is compiled, how do I make Steam Play utilize it?

benneti commented on 2018-08-28 07:28

According to https://github.com/ValveSoftware/Proton/blob/proton_3.7/CHANGELOG.md the latest version should work with both python2 and python3

Forty-Bot commented on 2018-08-27 12:06

I'll see if I can. The ./proton seems like the only part written in python; depending on how much needs to be changed, I could just rewrite it...

benneti commented on 2018-08-27 11:58

Wouldn't make it more sense to use python3 with the new version of proton, as this should be possible and is the default python in archlinux