game-porting-toolkit.md

How to install game-porting-toolkit (aka proton for macOS)

You also might wanna just use Whisky which does this automatically

This guide works on macOS 13.4+ using Command Line Tools for XCode 15 Beta!

What is this?

In the recent WWDC, Apple announced and released the "game porting toolkit", which upon further inspection this is just a modified version of CrossOver's fork of wine which is a "compatibility layer" that allows you to run Windows applications on macOS and Linux.

Why would I want this?

Playing Windows games on MacOS

How?

First, install homebrew which is an amazing macOS package manager, which is weirdly enough what Apple themselves have used for distrobution of this program

brew tap apple/homebrew-apple

This adds apple's offical "repository" for their "forumula" (package), which includes the game-porting-toolkit

AArch64 (ARM, Apple's chips, not x86_64/Intel)

Make sure that rosetta2 is installed

/usr/sbin/softwareupdate --install-rosetta --agree-to-license

homebrew to inside Rosetta

arch -x86_64 zsh
cd /usr/local && mkdir homebrew
curl -L github.com/Homebrew/brew/tarball/master | tar xz --strip 1 -C homebrew

arch -x86_64 /usr/local/homebrew/bin/brew tap apple/homebrew-apple
arch -x86_64 /usr/local/homebrew/bin/brew install game-porting-toolkit

Now, you can install the game-porting-toolkit

Warning: This will take a LONG TIME, and will use up a LOT of system resources because it needs to compile a really large project (LLVM)

brew install game-porting-toolkit

Then, go to this url (on apple.com) to download the actual toolkit, place it somewhere memorable.

How do I use it?

First, you need to create a "wine prefix" for your game.

To do this,

WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg

Where you would replace my-game-prefix with whatever you want you want it to be.

You should now change (in the window that pops up) the windows version to "windows 10"

Press ok, and then install your game into my-game-prefix

Finally, to install apple's game porting toolkit, use

ditto [REPLACE THIS WITH WHEREVER YOU PUT THE GAME PORTING TOOLKIT]/lib/ `brew --prefix game-porting-toolkit`/lib/

and finally, to run the executable,

[REPLACE THIS WITH WHEREVER YOU PUT THE GAME PORTING TOOLKIT]/gameportingtoolkit ~/my-game-prefix 'C:\\Program Files\\MyGame\\MyGame.exe'

or, for without the debug GUI

[REPLACE THIS WITH WHEREVER YOU PUT THE GAME PORTING TOOLKIT]/gameportingtoolkit-no-hud ~/my-game-prefix 'C:\\Program Files\\MyGame\\MyGame.exe'

Integration into Steam

TODO

I\m stuck in Sonoma, Was in Monterey earlier and updated for the toolkit, turns out that Xcode 15 isn't really working well with Sonoma so I need to revert back to Ventura, is there a possibility to downgrade to Ventura by any chance?

it keeps telling me that Git is Unavailable after I paste " % arch -x86_64 zsh
% cd /usr/local && mkdir homebrew
% curl -L github.com/Homebrew/brew/tarball/master | tar xz --strip 1 -C homebrew

arch -x86_64 /usr/local/homebrew/bin/brew install game-porting-toolkit "

@adad1223
@Kickunio

I had the same issue. I kept on getting stuck on installing brew svn.

Finally figured out that there were two cellar folders there were somehow created.

Navigated to the usr/local folder. There will be a folder called cellar, you will delete that.
Then, go to your usr/local/homebrew folder and move the cellar folder that is there to usr/local.

After that, I installed svn will 0 issues.

Hi all, I patched the Subversion formula in the Homebrew core yesterday: Homebrew/homebrew-core#133091. It should work fine now (after a brew update).

However, the reason we ran into issues is that the initial steps are NOT the way you are supposed to install Homebrew, and you can't benefit from pre-built binaries with that configuration (pre-built binaries can only be installed if homebrew is properly installed in /usr/local).

Based on several internet tutorials, I figured the definitive way to safely deal with the issue:

1. Delete the custom homebrew folder from /usr/local entirely (if you never created it, great, keep it this way).
2. While in x86_64 mode, run the regular homebrew installation script : /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" and wait for it to install. It will auto-setup everything in /usr/local.
3. While in x86_64 mode, run every homebrew command using /usr/local/bin/brew instead of brew, like this : /usr/local/bin/brew -v install apple/apple/game-porting-toolkit

For later use, you can edit your ~/.zshrc file and add the following line to create an alias and quickly access x64 homebrew:
alias intelbrew='arch -x86_64 /usr/local/bin/brew' (replace intelbrew with anything you like).

Then, you can call the x64 version of homebrew even while running the terminal session in arm mode, by just calling intelbrew <commands> (or the alias you choose earlier).

I run arch -x86_64 /usr/local/homebrew/bin/brew install svn this commend but freeze at
patching file 'Lib/distutils/command/install.py'
==> ./configure --prefix=/usr/local/homebrew/Cellar/python@3.11/3.11.3 --enable-
==> make
What should I do, anyone could help me?

Im on the blank screen with Steam as well. Included the logs I found, havent tried anything aside from reinstalling freetype.

Wine debugger output

0338: thread_get_state failed on Apple Silicon - faking zero debug registers
[2023-06-09 00:33:36] Background update loop checking for update. . .
[2023-06-09 00:33:36] Checking for available updates...
[2023-06-09 00:33:36] Downloading manifest: http://media.steampowered.com/client
/steam_client_win32
[2023-06-09 00:33:36] Manifest download: send request
[2023-06-09 00:33:36] Manifest download: waiting for download to finish
[2023-06-09 00:33:36] Manifest download: finished
[2023-06-09 00:33:36] Download skipped by HTTP 304 Not Modified
[2023-06-09 00:33:36] Nothing to do
[2023-06-09 00:33:54] Background update loop checking for update. . .
[2023-06-09 00:33:54] Downloading manifest: http://media.steampowered.com/client
/steam_client_win32
[2023-06-09 00:33:54] Manifest download: send request
[2023-06-09 00:33:54] Manifest download: waiting for download to finish
[2023-06-09 00:33:54] Manifest download: finished
[2023-06-09 00:33:54] Download skipped by HTTP 304 Not Modified
[2023-06-09 00:33:54] Nothing to do
01a4:fixme:thread:get_thread_times not implemented on this platform
011c:fixme:imm:ImeSetActiveContext (0xbb6ddb0, 1): stub

Program Error Details

Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000005bf6ed8).
Register dump:
 rip:0000000005bf6ed8 rsp:000000000021e640 rbp:0000229417a3d8c8 eflags:00000206 (   - --  I   - -P- )
 rax:000000000021e668 rbx:0000000000000000 rcx:0000310cbce2334c rdx:0000000007d5c680
 rsi:00000000073de9b0 rdi:000009d905b21b40  r8:0000000000000011  r9:00000000ff000000 r10:0000000000550000
 r11:0000229417a7e408 r12:0000000000000000 r13:0000000000000000 r14:000000000021e668 r15:000000000021e700
Stack dump:
0x0000000021e640:  0000229417a3d8c8 000021886bafedbb
0x0000000021e650:  000021886bafedbb 000009d905b21b40
0x0000000021e660:  0000229417a3d680 0000310cbce23340
0x0000000021e670:  000000000021e780 0000229417a3d680
0x0000000021e680:  0000103b68001c81 0000229417a3d8c8
0x0000000021e690:  0000000000000000 000021886bafeddb
0x0000000021e6a0:  000000000021e700 000009d905b21b40
0x0000000021e6b0:  00000000073de9b0 0000000000000000
0x0000000021e6c0:  0000229417a3d6a8 0000000005bf7016
0x0000000021e6d0:  000000000021e780 0000000002beeb1c
0x0000000021e6e0:  0000229417a3d680 0000229417a73f80
0x0000000021e6f0:  000000000c0f5d10 000000000c0f5d40
Backtrace:
=>0 0x00000005bf6ed8 CrashForExceptionInNonABICompliantCodeRange+0x3b4d478() in libcef (0x00229417a3d8c8)
  1 0x00000005bf7016 CrashForExceptionInNonABICompliantCodeRange+0x3b4d5b6() in libcef (0x00229417a3d8c8)
  2 0x0000000568b145 CrashForExceptionInNonABICompliantCodeRange+0x35e16e5() in libcef (0x00229417a3d8c8)
  3 0x0000000568ad0b CrashForExceptionInNonABICompliantCodeRange+0x35e12ab() in libcef (0x0000000c0f4710)
  4 0x0000000568ac74 CrashForExceptionInNonABICompliantCodeRange+0x35e1214() in libcef (0x0000000c280001)
  5 0x00000005f46add CrashForExceptionInNonABICompliantCodeRange+0x3e9d07d() in libcef (0x00000007d99db0)
  6 0x00000005f488e2 CrashForExceptionInNonABICompliantCodeRange+0x3e9ee82() in libcef (0x00000000000008)
  7 0x00000005f8d002 CrashForExceptionInNonABICompliantCodeRange+0x3ee35a2() in libcef (0x00000000000008)
  8 0x00000000e783f8 cef_add_cross_origin_whitelist_entry+0x926a61() in libcef (0x00000000000008)
  9 0x00000002be250c CrashForExceptionInNonABICompliantCodeRange+0xb38aac() in libcef (0x00000080000003)
  10 0x00000002d5ea70 CrashForExceptionInNonABICompliantCodeRange+0xcb5010() in libcef (0x00000080000003)
  11 0x00000002d5cf57 CrashForExceptionInNonABICompliantCodeRange+0xcb34f7() in libcef (0x000000080c2818)
  12 0x000000029f7c20 CrashForExceptionInNonABICompliantCodeRange+0x94e1c0() in libcef (0x000000080c2818)
  13 0x00000002ab48f7 CrashForExceptionInNonABICompliantCodeRange+0xa0ae97() in libcef (0x00000002d5c8cf)
  14 0x00000002ab4656 CrashForExceptionInNonABICompliantCodeRange+0xa0abf6() in libcef (0x7fffffffffffffff)
  15 0x00000002ab73ec CrashForExceptionInNonABICompliantCodeRange+0xa0d98c() in libcef (0x7fffffffffffffff)
  16 0x00000002ab4f58 CrashForExceptionInNonABICompliantCodeRange+0xa0b4f8() in libcef (0x00000000000001)
  17 0x000000029f85fa CrashForExceptionInNonABICompliantCodeRange+0x94eb9a() in libcef (0x0000000021f3e8)
  18 0x00000005f4c270 CrashForExceptionInNonABICompliantCodeRange+0x3ea2810() in libcef (0x0000000021f3e8)
  19 0x000000028f1f6d CrashForExceptionInNonABICompliantCodeRange+0x84850d() in libcef (0x0000000021f580)
  20 0x000000046ae44e CrashForExceptionInNonABICompliantCodeRange+0x26049ee() in libcef (0000000000000000)
  21 0x000000046aea64 CrashForExceptionInNonABICompliantCodeRange+0x2605004() in libcef (0000000000000000)
  22 0x000000028f1686 CrashForExceptionInNonABICompliantCodeRange+0x847c26() in libcef (0000000000000000)
  23 0x0000000296b8cd CrashForExceptionInNonABICompliantCodeRange+0x8c1e6d() in libcef (0000000000000000)
  24 0x00000002915701 CrashForExceptionInNonABICompliantCodeRange+0x86bca1() in libcef (0000000000000000)
  25 0x00000000551137 cef_execute_process+0x57() in libcef (0000000000000000)
  26 0x0000014008d6f9 GetHandleVerifier+0x39ac9() in steamwebhelper (0000000000000000)
  27 0x000001401dc23d GetHandleVerifier+0x18860d() in steamwebhelper (0x0000000021fcd9)
  28 0x000001401de22c GetHandleVerifier+0x18a5fc() in steamwebhelper (0x0000000021fd99)
  29 0x0000014030600a CreateInterface+0x5629a() in steamwebhelper (0000000000000000)
  30 0x0000007b62a889 BaseThreadInitThunk+0x9(unknown=<internal error>, entry=<internal error>, arg=<internal error>) [Z:\private\tmp\game-porting-toolkit-20230608-73988-jjzqru\wine\dlls\kernel32\thread.c:61] in kernel32 (0000000000000000)
  31 0x0000017005b3b8 __wine_pop_frame(unknown=<internal error>, entry=<internal error>, arg=<internal error>) [Z:\private\tmp\game-porting-toolkit-20230608-73988-jjzqru\wine\include\wine\exception.h:275] in ntdll (0000000000000000)
  32 0x0000017005b3b8 RtlUserThreadStart+0x88(entry=[<register RSP not accessible in this frame>, arg=[<register RSP not accessible in this frame>) [Z:\private\tmp\game-porting-toolkit-20230608-73988-jjzqru\wine\dlls\ntdll\thread.c:240] in ntdll (0000000000000000)
0x00000005bf6ed8 libcef+0x56a6ed8: movq	(%rbx),

Thanks for any advice!

@sunjishen That is fully normal, makeing python takes forever. Everything is fine as long as no errors occur.

@theBreadCompany It's not normal, I already waiting for this process for 2 hours......

Someone installed the Epic Games Launcher?

@theBreadCompany It's not normal, I already waiting for this process for 2 hours......

How much time it took ? I am also stuck there for quite long still no success

I run arch -x86_64 /usr/local/homebrew/bin/brew install svn this commend but freeze at patching file 'Lib/distutils/command/install.py' ==> ./configure --prefix=/usr/local/homebrew/Cellar/python@3.11/3.11.3 --enable- ==> make What should I do, anyone could help me?

I encoutered the same issue.
I somehow fixed it by using the following:

brew bundle dump
rm -rf /usr/local/Homebrew/Cellar
brew bundle

Maybe combined with something but I don't remember. You can give it a try.

Steam Installed successfully but stuck while launch

I run arch -x86_64 /usr/local/homebrew/bin/brew install svn this commend but freeze at patching file 'Lib/distutils/command/install.py' ==> ./configure --prefix=/usr/local/homebrew/Cellar/python@3.11/3.11.3 --enable- ==> make What should I do, anyone could help me?

I encoutered the same issue. I somehow fixed it by using the following:

brew bundle dump
rm -rf /usr/local/Homebrew/Cellar
brew bundle

Maybe combined with something but I don't remember. You can give it a try.

Thanks

I got Steam working using with

/Volumes/Game\ Porting\ Toolkit-1.0/gameportingtoolkit ~/my-game-prefix /Users/yourusername/my-game-prefix/drive_c/Program\ Files\ \(x86\)/Steam/steam.exe

Obviously change the paths accordingly

Someone installed the Epic Games Launcher?

yeah but i ran into this error

i have installed all the prerequisites it either needs to be run as admin or it needs access to temp folder i'll update y'all if any solutions work

What to do if
arch -x86_64 zsh
results in an error:
arch: posix_spawnp: zsh: Bad CPU type in executable

What to do if arch -x86_64 zsh results in an error: arch: posix_spawnp: zsh: Bad CPU type in executable

Confirm your system architecture: Open a terminal and run the following command:
arch
It should return x86_64 for a 64-bit system.

Verify the zsh executable: Check if you have a compatible version of zsh installed for your system architecture. If you installed it manually or using package managers, make sure it matches your system architecture. You can check the architecture of the zsh executable by running the following command:
file $(which zsh)

and then please provide the results

To specify the correct architecture when running zsh, you can use the arch command followed by the desired architecture. In your case, you can try running zsh using the x86_64 architecture with the following command:

arch -x86_64 zsh

running arch returns arm64

file $(which zsh) returns /opt/homebrew/bin/zsh: Mach-O 64-bit executable arm64 so I guess this is my problem right? I need zsh that supports x86_64? Or am I not understanding this?

running arch returns arm64

file $(which zsh) returns /opt/homebrew/bin/zsh: Mach-O 64-bit executable arm64 so I guess this is my problem right? I need zsh that supports x86_64? Or am I not understanding this?

The output of file $(which zsh) indicates that the zsh binary you are using is specifically built for the arm64 architecture. This suggests that you are running on an Apple Silicon (M1) Mac.

To execute zsh using the x86_64 architecture, you need to ensure that you have the x86_64 version of zsh installed on your system.

When I try to run the Steam EXE file, I get

Error: No available formula with the name "game-porting-toolkit".

I'm using the x86_64 version of Homebrew, and I've done everything else properly.

I recommend this straight forward guide, as I encountered several issues with freezes like Python, permission handlin in /usr/local and issues with svn. The other guide worked without errors.
https://www.applegamingwiki.com/wiki/Game_Porting_Toolkit

I'm stuck at the first steps:

$ /usr/sbin/softwareupdate --install-rosetta --agree-to-license
By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.
If you do not agree, press CTRL-C and cancel this process immediately.
2023-06-15 16:31:38.312 softwareupdate[47017:8161702] Package Authoring Error: 032-84877: Package reference com.apple.pkg.RosettaUpdateAuto is missing installKBytes attribute
Install of Rosetta 2 finished successfully

and then

$ arch -x86_64 zsh
arch: posix_spawnp: zsh: Bad CPU type in executable

Anyone has run into such problem?

What's odd is that it seems I have Rosetta 2 installed as I can run all Intel/x86 applications...

I'm stuck at the first steps:

$ /usr/sbin/softwareupdate --install-rosetta --agree-to-license
By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.
If you do not agree, press CTRL-C and cancel this process immediately.
2023-06-15 16:31:38.312 softwareupdate[47017:8161702] Package Authoring Error: 032-84877: Package reference com.apple.pkg.RosettaUpdateAuto is missing installKBytes attribute
Install of Rosetta 2 finished successfully

and then

$ arch -x86_64 zsh
arch: posix_spawnp: zsh: Bad CPU type in executable

Anyone has run into such problem?

What's odd is that it seems I have Rosetta 2 installed as I can run all Intel/x86 applications...

you might want to type which brew and make sure your brew path is setup to the x64 version of brew. I suspect that you might have manually installed an arm64 version of zsh via home-brew.

For my case in my .zprofile I had arm64 brew which I commented out to setup for x64 brew:

# arm64 brew
# eval "$(/opt/homebrew/bin/brew shellenv)"

# x64 brew
eval "$(/usr/local/bin/brew shellenv)"

so when you type which brew it should show:
/usr/local/bin/brew

works too slow guys I installed sonoma

Running M2 Max MBP, I installed homebrew via the official homepage. Installed Rosetta per readme. When running arch -x86_64 /usr/local/homebrew/bin/brew tap apple/homebrew-apple I get arch: /usr/local/homebrew/bin/brew isn't executable. If I run arch command it returns with i386. What is happening here?

you might want to type which brew and make sure your brew path is setup to the x64 version of brew. I suspect that you might have manually installed an arm64 version of zsh via home-brew.

You were right @TaiPhamD , thanks!

In case some one wants the code to create a d4 alias in their command zsh shell to launch d4. Add this in your ~/.zshrc:

alias d4='arch -x86_64 zsh -c "eval \"$(/usr/local/bin/brew shellenv)\"; /usr/local/Cellar/game-porting-toolkit/1.0/gameportingtoolkit-no-hud ~/my-game-prefix \"C:\\Program Files (x86)\\Diablo IV\\Diablo IV Launcher.exe\" &"'

then now I can just type d4 in my command line to launch the game

there is also a great tool named Harbor, which can manage the bootles and provides a gui for launching. It requires the brew setup, not like whisky. I do also use the approach with zprofile with aliases, but using Harbor feels like crossover, but with the gaming toolkit, what's pretty neat.

https://github.com/ohaiibuzzle/Harbor

Whisky never worked for me, it's nailed together and works for a group, while there is another, where it doesn't

did anyone fail when creating wine-prefix (running winecfg the first time)?
it is a bit frustrating for me.

• I have MacBook M1 Pro, just installed macOS Sonoma Developer Beta.
• Followed all the instruction up until: WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg. it gave me this error:

wine: created the configuration directory '/Users/.../my-game-prefix'
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
002c:fixme:shell:create_link failed to connect to mount manager
002c:fixme:shell:create_link failed to connect to mount manager
00e4:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet
...
00e4:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet
00e4:err:module:LdrInitializeThunk "comctl32.dll" failed to initialize, aborting
00e4:err:module:LdrInitializeThunk Initializing dlls for L"C:\\windows\\system32\\iexplore.exe" failed, status c0000005
00f0:fixme:module:dlopen_32on64_opengl32 loaded "/usr/local/Cellar/game-porting-toolkit/1.0/lib/wine/x86_32on64-unix/opengl32.dll.so" early @ 0x688a7000
00f0: thread_get_state failed on Apple Silicon - faking zero debug registers
00f8:fixme:module:dlopen_32on64_opengl32 loaded "/usr/local/Cellar/game-porting-toolkit/1.0/lib/wine/x86_32on64-unix/opengl32.dll.so" early @ 0x688a7000
00f8: thread_get_state failed on Apple Silicon - faking zero debug registers
00f8:err:seh:call_stack_handlers invalid frame 000000000062E0A8 (0000000000632000-000000000072FD20)
00f8:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception.
wine: configuration in L"/Users/.../my-game-prefix" has been updated.
0148:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet
...
0148:fixme:unwind:virtual_unwind calling personality routine in system library not supported yet
0148:err:module:LdrInitializeThunk "comctl32.dll" failed to initialize, aborting
0148:err:module:LdrInitializeThunk Initializing dlls for L"C:\\windows\\system32\\winecfg.exe" failed, status c0000005

before I tried to install game-porting-toolkit (before installing macOS Sonoma):

• I have arm brew installed. I'm a web developer, I will not remove my arm brew. so instead, I installed 2 version of brews (i386 & arm64). put this script in my .zprofile:

if [ "$(arch)" = "arm64" ]; then
    eval "$(/opt/homebrew/bin/brew shellenv)"
else
    eval "$(/usr/local/bin/brew shellenv)"
fi

• I have crossover & portingkit installed, I don't know whether they're affecting the game-porting-toolkit or not, listed here just in case

when installing the game-porting-toolkit:

• I ran iTerm 2 with rosetta (in fact, I have 2 copies of iTerm app: universal app & force-checked rosetta)
• I've ensured that the shell is running on i386 mode by running arch command
• everything (before making wine-prefix directory) went smoothly, game-porting-toolkit installation through brew did not give me any error
• I tried to reinstall game-porting-toolkit twice, in the last attempt I cleared the brew cache in case of my cache got corrupted or anything.

any idea?

I managed to solve my issue by entering this command:
WINEPREFIX=~/my-game-prefix arch -x86_64 `brew --prefix game-porting-toolkit`/bin/wine64 winecfg

it's so weird, I ran the rosetta iTerm & ensured that the shell was running on i386 arch. but without arch -x86_64 it simply didn't work no matter what. I don't know what's wrong, but it's fine now. I managed to install steam