Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support 32-bit prefixes #919

Open
wants to merge 2 commits into
base: proton_3.16
Choose a base branch
from
Open

Conversation

mat8913
Copy link

@mat8913 mat8913 commented Aug 29, 2018

64-bit prefixes will still be created by default, this just allows Proton to use preexisting 32-bit prefixes.

Fixes #449.

64-bit prefixes will still be created by default, this just allows
Proton to use preexisting 32-bit prefixes.
@tingvarsson
Copy link

What are the use cases for a 32bit prefix?

@Elkasitu
Copy link
Contributor

Elkasitu commented Aug 29, 2018

IIRC some "old" games (such as fallout 1 and fallout 2 just as an example) don't run well or at all in a 64bit prefix because the libs / frameworks required to execute them were originally created for 32bit OS and the 64bit version of these libs don't install properly on wine, or something along those lines.

@tingvarsson
Copy link

Both fallout 1 and 2 works for me on 64bit. However GOG and wine-staging if that matters for those specific games.

@ahallrq
Copy link

ahallrq commented Aug 30, 2018

@tingvarsson .NET is another good reason. Some games use it and the workarounds for installing it into 64bit prefixes can be a bit of a pain.

@Ruedii
Copy link

Ruedii commented Sep 1, 2018

It would be better to just create a proper install script.

.Net now installs better on Wine64 due to Microsoft releasing the necessary 64bit/32bit universal installers for .Net. (available at their .Net developer website.) It might be desirable to create scripts, or request from Microsoft the right to distribute a custom runtime installer.

Microsoft is really trying to push .Net and getting .Net based games dependent on Windows-Specific .Net routines running out of box on Steam Play (and thus on the next generation of Steam Machines) will be a big plus for that.

This is still a temporary solution. A more permanent solution is a more complete form of wine-mono that can run almost anything that runs on .Net.

@Thinkaboutmin Thinkaboutmin mentioned this pull request Sep 6, 2018
2 tasks
@Zero86Sk
Copy link

i beleave WMP10 and WMV codecs are usable only under wine32 prefixes

@elgabo86
Copy link

The Sandbox Evolution (‎466940,F2P) can't connect on network in a 64bit prefix

@Arucard1983
Copy link

@tingvarsson .NET is another good reason. Some games use it and the workarounds for installing it into 64bit prefixes can be a bit of a pain.

Specially with 32-bit games that use the 32-bit .NET framework, unless someone fix the Wine's WOW64 to make such libraries to work.

@Rabcor Rabcor mentioned this pull request Nov 3, 2018
2 tasks
@mat8913 mat8913 changed the base branch from proton_3.7 to proton_3.16 November 7, 2018 16:19
@mat8913
Copy link
Author

mat8913 commented Nov 8, 2018

I've updated the pull request for proton_3.16

@nsivov
Copy link
Contributor

nsivov commented Nov 17, 2018

I believe fixing remaining issues with 64-bit prefixes instead is preferable.

@ghost
Copy link

ghost commented Mar 1, 2019

I believe fixing remaining issues with 64-bit prefixes instead is preferable.

Why? There are a magnitude more problems with 64-bit prefixes than there is with maintaining code for 32-bit prefixes (judging from this PR doesn't seem like a lot.) Example: some games are currently broken because Winetricks can't install quartz in a 64-bit prefix. The fact that problems like these keep cropping up is why Winetricks suggests you try a 32-bit prefix if installing something in a 64-bit prefix doesn't work.

@Tank-Missile
Copy link

Could this be updated to work with the current version of Proton? I tried every trick in the book to get a 32-bit prefix working on my own, but I had no success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet