https://www.applegamingwiki.com/w/api.php?action=feedcontributions&feedformat=atom&user=John1111AppleGamingWiki - User contributions [en]2026-04-28T07:03:33ZUser contributionsMediaWiki 1.35.7https://www.applegamingwiki.com/w/index.php?title=User:Desireebaldwin&diff=7879User:Desireebaldwin2023-06-19T10:58:41Z<p>John1111: no spam bozo</p>
<hr />
<div>No spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=Game_Porting_Toolkit&diff=7586Game Porting Toolkit2023-06-08T07:51:33Z<p>John1111: /* Game compatibility list */</p>
<hr />
<div>Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPTK''') combines Wine with Apple's own D3DMetal which supports DirectX 9-12. This is less user-friendly method of installing Windows games on Apple Silicon Macs compared to [[CrossOver]] or [[Parallels]], however it unlocks the ability to play many DirectX 12 games. Many more games not work using GPTK, however games that use anti-cheat or aggressive DRM generally don't worker do games that require AVX/AVX 2, e.g. The Last of Us Part I.<br />
<br />
== Toolkit install instructions ==<br />
=== Requirements ===<br />
*macOS Sonoma should be used, currently it is in beta. You can download the pkg installer from [https://mrmacintosh.com/macos-sonoma-full-installer-database-download-directly-from-apple/ Mr Macintosh blog].<br />
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.<br />
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.<br />
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.<br />
**If you have an old version Xcode installed, remove it.<br />
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.<br />
<br />
=== Homebrew ===<br />
Note: if you have ever installed Homebrew before, then it is advisable to remove arm64 Homebrew as this can interfere with this build process. Either use a Homebrew uninstall script or delete the folder <code>/opt/homebrew/bin</code>. Otherwise, if you prefer to keep both arm64 and x86 versions of brew installed, you may add a "brew-switcher" to your <code>.zshrc</code> file to allow either version to be used depending on the active architecture. You may follow the steps at the end of this section after installing Brew to achieve this.<br />
<br />
Open Terminal (search in Spotlight on macOS).<br />
<br />
Install Rosetta:<br />
<pre>softwareupdate --install-rosetta</pre><br />
<br />
Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.<br />
<pre>arch -x86_64 zsh</pre><br />
<br />
Install the x86_64 version of Homebrew if you don't already have it.<br />
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre><br />
<br />
Make sure the brew command is on your path:<br />
<pre>which brew</pre><br />
<br />
If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:<br />
<pre>export PATH=/usr/local/bin:${PATH}</pre><br />
<br />
(Optional) If you want to have both arm64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:<br />
<pre>nano ~/.zshrc</pre><br />
<br />
Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:<br />
<pre><br />
if [ "$(arch)" = "arm64" ]; then<br />
eval "$(/opt/homebrew/bin/brew shellenv)"<br />
else<br />
eval "$(/usr/local/bin/brew shellenv)"<br />
fi<br />
</pre><br />
<br />
You may now restart your terminal and use the following command to return to an x86_64 shell:<br />
<pre>arch -x86_64 zsh</pre><br />
Your shell will now select the right installation of Brew, depending on your architecture.<br />
<br />
=== Build ===<br />
Run this command to download Apple tap:<br />
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre><br />
<br />
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer. It can take over 1 hour to complete depending on the speed of your Mac.<br />
<pre>brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
If during installation you see an error such as '''“Error: game-porting-toolkit: unknown or unsupported macOS version: :dunno”, your version of Homebrew doesn’t have macOS Sonoma support. Update to the latest version of Homebrew and try again.'''<br />
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
===Wine prefix ===<br />
A Wine prefix contains a virtual C: drive. You will install the toolkit and your game into this virtual C: drive. Run the following command to create a new Wine prefix named my-game-prefix in your home directory.<br />
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to Windows 10.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
If the “Wine configuration” window does not appear, and no new icon appears in the Dock, verify that you have correctly installed the x86_64 version of Homebrew as well as the game-porting-toolkit formula.<br />
<br />
=== Preparing the toolkit ===<br />
Make sure the Game Porting Toolkit dmg downloaded earlier is mounted at /Volumes/Game Porting Toolkit-1.0. Use this script to copy the Game Porting Toolkit library directory into Wine’s library directory.<br />
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre><br />
<br />
Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:<br />
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre><br />
<br />
Now you are ready to install a launcher or individual Windows games, see below.<br />
<br />
== Steam ==<br />
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.<br />
<br />
'''Install Steam'''<br />
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre><br />
<br />
'''Run Steam'''<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre><br />
<br />
'''Log into Steam'''<br />
<br />
A common issue is that Steam will present with a blank black window.<br />
<br />
Alternate way of launching Steam (after installing):<br />
<pre><br />
MTL_HUD_ENABLED=1 WINEESYNC=1 WINEPREFIX=~/my-game-prefix /usr/local/Cellar/game-porting-toolkit/1.0/bin/wine64 'C:\Program Files (x86)\Steam\steam.exe'<br />
</pre><br />
<br />
If this continues then close the Terminal window and then re-open and try again, repeat until the login screen opens. Now you should be able to download and launch Windows games through Steam.<br />
<br />
== Battle.net ==<br />
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net].<br />
<br />
Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:<br />
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to <code>Windows 10</code>.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
'''Run Battle.net launcher'''<br />
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre><br />
<br />
Be aware that there is an issue launching Battle.net once installed, the only current way to re-login is to 'install' the launcher again. <br />
<br />
Start individual game without the launcher using this command:<br />
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre><br />
<br />
== Epic and GOG.com support ==<br />
This is particularly useful because '''as it currently stands, the real Epic Games Launcher fails to install under the Game Porting Toolkit'''. Heroic supports Epic and GOG.com games.<br />
<br />
* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.<br />
* Open Heroic, and log into your Epic Games and/or GOG.com account.<br />
* Go to the "Wine Manager" and install a '''numbered''' version of Wine, such that it won't auto update- we are going to modify it.<br />
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code><br />
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.<br />
* Right-click on the version of Wine you just installed and press "Show Package Contents".<br />
* Open this directory in the Terminal.<br />
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".<br />
** It should be something like <code>cd ~/Library/Application Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.<br />
* <pre>cd Contents/MacOS</pre><br />
* Remove the existing Wine: <pre>rm wine</pre><br />
* Create a symlink to Game Porting Toolkit's Wine: <br />
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre><br />
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre><br />
* <pre>cd ../Resources</pre><br />
* Remove the existing Wine: <pre>rm -rfv wine</pre><br />
* Create a symlink to Game Porting Toolkit's Wine<br />
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre><br />
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre><br />
* We are now done with Terminal. Install any games you want to try playing.<br />
* Select the game you want to play, and press the settings button in the top-right.<br />
* Make sure the version of Wine you just downloaded and modified is selected.<br />
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/you/my-game-prefix</code>.<br />
* If you Open the "Other" section you can also add any environment variables you want like <code>WINEESYNC=1"</code> and <code>"MTL_HUD_ENABLED=1"</code><br />
* Close the settings and try running the game.<br />
<br />
== Commands ==<br />
Installing individual exe games: open your Wine prefix’s virtual C: drive in Finder (open ~/my-game-prefix/drive_c) and copy your game into an appropriate subdirectory.<br />
<br />
'''A. Standard launching'''<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.<br />
<br />
'''B. Launching without a HUD'''<br />
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
'''C. Launching with Wine ESYNC disabled'''<br />
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
To enter Winecfg:<br />
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre><br />
<br />
== Shortcut ==<br />
You can make a shortcut for Steam for example by using macOS built-in Automator app.<br />
*Open Automator.<br />
*Select New Application.<br />
*In the 2nd column select Run Shell Script.<br />
*Copy and paste this code into the box:<br />
<pre><br />
#!/bin/zsh<br />
<br />
export PATH="/usr/local/bin:${PATH}"<br />
<br />
arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'<br />
</pre><br />
*Save the shortcut somewhere e.g. Applications.<br />
*Above shortcut can be customised to any Wineprefix or game.<br />
*Add an icon by selecting the shortcut, pressing {{key|cmd|I}} to Get Info, then dragging and dropping a PNG file onto the top left of the window.<br />
<br />
== Logging ==<br />
The provided bin/gameportingtoolkit* scripts can be copied onto your path to facilitate different forms of logging and launching. You can run these scripts from any shell; you don’t need to switch to the Rosetta environment first.<br />
<br />
Logging output will appear in the Terminal window in which you launch your game as well as the system log, which can be viewed with the Console app found in Applications ▸ Utilities. Log messages from the Game Porting Toolkit are prefixed with D3DM. By default the gameportingtoolkit* scripts will filter to just the D3DM-prefixed messages.<br />
<br />
== Troubleshooting ==<br />
'''Steam login black screen'''<br />
<br />
Close the Terminal window and then reopen and retry the command, repeat several times.<br />
<br />
Alternate way of launching Steam (after installing):<br />
<pre><br />
MTL_HUD_ENABLED=1 WINEESYNC=1 WINEPREFIX=<path to the Wine bottle you set up> /usr/local/Cellar/game-porting-toolkit/1.0/bin/wine64 'C:\Program Files (x86)/Steam/steam.exe'<br />
</pre><br />
<br />
If still not working then try using [[CrossOver]] and create a Steam bottle, then redirect this WINEPREFIX to that bottle:<br />
<pre><br />
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/" <br />
</pre><br />
<br />
'''Steam crashes straight after opening'''<br />
<br />
Disconnect any external monitors.<br />
<br />
'''Battle.net launcher won't re-launch'''<br />
<br />
Re-install the launcher to reopen, no other fix at the moment.<br />
<br />
'''My game won’t run because it thinks the version of Windows is too old. Some games detect specific minimum versions of Windows and need to be updated.''' Use this script to update your wineprefix with build 19042 which should work for most games e.g. Spider-Man Remastered.<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuild /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuildNumber /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k<br />
</pre><br />
<br />
'''steamwebhelper.exe crashes'''<br />
<br />
This is caused by Steam being run through macOS Ventura or below, upgrade to macOS Sonoma.<br />
<br />
'''My game won't run and crashes with an invalid instruction'''<br />
<br />
AVX and AVX2 games are not supported by Apple's arm64 chipset.<br />
<br />
'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''<br />
<br />
Likely there will be no fixes for any games that use anti-cheat, e.g. Easy Anti Cheat. Some games have workarounds e.g. Elden Ring. Other games that use say Denuvo may also be incompatible until that DRM is removed by the game's developer.<br />
<br />
'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''<br />
<br />
The game porting toolkit’s evaluation environment does not pre-install these runtime support packages. If your game makes use of one of these packages, consider searching for and downloading appropriate installers (.exe or .msi) and installing them to your evaluation environment. Additional runtime installers can be run on your environment by just launching the installer and following its installation instructions:<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe><br />
</pre><br />
<br />
And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller<br />
</pre><br />
<br />
'''Controller issues'''<br />
<br />
Issues may be fixed by enrolling into the Steam beta.<br />
<br />
== Game compatibility list ==<br />
Working games:<br />
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility)<br />
* Cyberpunk 2077<br />
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)<br />
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)<br />
* Elden Ring<br />
* SpongeBob SquarePants: The Cosmic Shake<br />
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]<br />
* Hogwarts Legacy<br />
* Deep Rock Galactic<br />
* Sonic Omens<br />
* Sonic P-06<br />
* Scarlet Nexus<br />
* Metal Gear Solid V: The Phantom Pain<br />
* Dyson Sphere Program (some objects and main character weren't visible before)<br />
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)<br />
* Spider-Man (2018)<br />
* Spider-Man Miles Morales - ''requires Windows ver fix''<br />
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''<br />
* HI-Fi RUSH<br />
* QUBE 2<br />
* Deceive Inc. - works well if launched without EAC<br />
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)<br />
* Crysis Remastered<br />
* Cuphead<br />
* Bloodstained: Ritual of the Night<br />
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise<br />
<br />
Not working well:<br />
* Horizon Zero Dawn - slowdown issues<br />
<br />
Not working yet:<br />
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3<br />
* Among Us<br />
* Tiny Tina's Wonderlands - Intro videos play, dragon animation indicating shader precompilation starts, game freezes, eventually crashes.<br />
* Halo Infinite - Crash on launch<br />
* Street Fighter 6 - Crash on launch<br />
* Company of Heroes 3<br />
* Many (all?) DX9 games<br />
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game<br />
** Left 4 Dead 2 - Black screen -> crash on launch<br />
** Killing Floor 1 - Crash on launch<br />
** Sonic Mania - Crash on launch<br />
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch</div>John1111https://www.applegamingwiki.com/w/index.php?title=Game_Porting_Toolkit&diff=7585Game Porting Toolkit2023-06-08T07:45:36Z<p>John1111: /* Game compatibility list */</p>
<hr />
<div>Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPTK''') combines Wine with Apple's own D3DMetal which supports DirectX 9-12. This is less user-friendly method of installing Windows games on Apple Silicon Macs compared to [[CrossOver]] or [[Parallels]], however it unlocks the ability to play many DirectX 12 games. Many more games not work using GPTK, however games that use anti-cheat or aggressive DRM generally don't worker do games that require AVX/AVX 2, e.g. The Last of Us Part I.<br />
<br />
== Toolkit install instructions ==<br />
=== Requirements ===<br />
*macOS Sonoma should be used, currently it is in beta. You can download the pkg installer from [https://mrmacintosh.com/macos-sonoma-full-installer-database-download-directly-from-apple/ Mr Macintosh blog].<br />
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.<br />
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.<br />
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.<br />
**If you have an old version Xcode installed, remove it.<br />
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.<br />
<br />
=== Homebrew ===<br />
Note: if you have ever installed Homebrew before, then it is advisable to remove arm64 Homebrew as this can interfere with this build process. Either use a Homebrew uninstall script or delete the folder <code>/opt/homebrew/bin</code>. Otherwise, if you prefer to keep both arm64 and x86 versions of brew installed, you may add a "brew-switcher" to your <code>.zshrc</code> file to allow either version to be used depending on the active architecture. You may follow the steps at the end of this section after installing Brew to achieve this.<br />
<br />
Open Terminal (search in Spotlight on macOS).<br />
<br />
Install Rosetta:<br />
<pre>softwareupdate --install-rosetta</pre><br />
<br />
Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.<br />
<pre>arch -x86_64 zsh</pre><br />
<br />
Install the x86_64 version of Homebrew if you don't already have it.<br />
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre><br />
<br />
Make sure the brew command is on your path:<br />
<pre>which brew</pre><br />
<br />
If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:<br />
<pre>export PATH=/usr/local/bin:${PATH}</pre><br />
<br />
(Optional) If you want to have both arm64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:<br />
<pre>nano ~/.zshrc</pre><br />
<br />
Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:<br />
<pre><br />
if [ "$(arch)" = "arm64" ]; then<br />
eval "$(/opt/homebrew/bin/brew shellenv)"<br />
else<br />
eval "$(/usr/local/bin/brew shellenv)"<br />
fi<br />
</pre><br />
<br />
You may now restart your terminal and use the following command to return to an x86_64 shell:<br />
<pre>arch -x86_64 zsh</pre><br />
Your shell will now select the right installation of Brew, depending on your architecture.<br />
<br />
=== Build ===<br />
Run this command to download Apple tap:<br />
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre><br />
<br />
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer. It can take over 1 hour to complete depending on the speed of your Mac.<br />
<pre>brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
If during installation you see an error such as '''“Error: game-porting-toolkit: unknown or unsupported macOS version: :dunno”, your version of Homebrew doesn’t have macOS Sonoma support. Update to the latest version of Homebrew and try again.'''<br />
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
===Wine prefix ===<br />
A Wine prefix contains a virtual C: drive. You will install the toolkit and your game into this virtual C: drive. Run the following command to create a new Wine prefix named my-game-prefix in your home directory.<br />
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to Windows 10.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
If the “Wine configuration” window does not appear, and no new icon appears in the Dock, verify that you have correctly installed the x86_64 version of Homebrew as well as the game-porting-toolkit formula.<br />
<br />
=== Preparing the toolkit ===<br />
Make sure the Game Porting Toolkit dmg downloaded earlier is mounted at /Volumes/Game Porting Toolkit-1.0. Use this script to copy the Game Porting Toolkit library directory into Wine’s library directory.<br />
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre><br />
<br />
Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:<br />
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre><br />
<br />
Now you are ready to install a launcher or individual Windows games, see below.<br />
<br />
== Steam ==<br />
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.<br />
<br />
'''Install Steam'''<br />
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre><br />
<br />
'''Run Steam'''<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre><br />
<br />
'''Log into Steam'''<br />
<br />
A common issue is that Steam will present with a blank black window.<br />
<br />
Alternate way of launching Steam (after installing):<br />
<pre><br />
MTL_HUD_ENABLED=1 WINEESYNC=1 WINEPREFIX=~/my-game-prefix /usr/local/Cellar/game-porting-toolkit/1.0/bin/wine64 'C:\Program Files (x86)\Steam\steam.exe'<br />
</pre><br />
<br />
If this continues then close the Terminal window and then re-open and try again, repeat until the login screen opens. Now you should be able to download and launch Windows games through Steam.<br />
<br />
== Battle.net ==<br />
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net].<br />
<br />
Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:<br />
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to <code>Windows 10</code>.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
'''Run Battle.net launcher'''<br />
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre><br />
<br />
Be aware that there is an issue launching Battle.net once installed, the only current way to re-login is to 'install' the launcher again. <br />
<br />
Start individual game without the launcher using this command:<br />
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre><br />
<br />
== Epic and GOG.com support ==<br />
This is particularly useful because '''as it currently stands, the real Epic Games Launcher fails to install under the Game Porting Toolkit'''. Heroic supports Epic and GOG.com games.<br />
<br />
* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.<br />
* Open Heroic, and log into your Epic Games and/or GOG.com account.<br />
* Go to the "Wine Manager" and install a '''numbered''' version of Wine, such that it won't auto update- we are going to modify it.<br />
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code><br />
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.<br />
* Right-click on the version of Wine you just installed and press "Show Package Contents".<br />
* Open this directory in the Terminal.<br />
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".<br />
** It should be something like <code>cd ~/Library/Application Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.<br />
* <pre>cd Contents/MacOS</pre><br />
* Remove the existing Wine: <pre>rm wine</pre><br />
* Create a symlink to Game Porting Toolkit's Wine: <br />
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre><br />
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre><br />
* <pre>cd ../Resources</pre><br />
* Remove the existing Wine: <pre>rm -rfv wine</pre><br />
* Create a symlink to Game Porting Toolkit's Wine<br />
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre><br />
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre><br />
* We are now done with Terminal. Install any games you want to try playing.<br />
* Select the game you want to play, and press the settings button in the top-right.<br />
* Make sure the version of Wine you just downloaded and modified is selected.<br />
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/you/my-game-prefix</code>.<br />
* If you Open the "Other" section you can also add any environment variables you want like <code>WINEESYNC=1"</code> and <code>"MTL_HUD_ENABLED=1"</code><br />
* Close the settings and try running the game.<br />
<br />
== Commands ==<br />
Installing individual exe games: open your Wine prefix’s virtual C: drive in Finder (open ~/my-game-prefix/drive_c) and copy your game into an appropriate subdirectory.<br />
<br />
'''A. Standard launching'''<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.<br />
<br />
'''B. Launching without a HUD'''<br />
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
'''C. Launching with Wine ESYNC disabled'''<br />
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
To enter Winecfg:<br />
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre><br />
<br />
== Shortcut ==<br />
You can make a shortcut for Steam for example by using macOS built-in Automator app.<br />
*Open Automator.<br />
*Select New Application.<br />
*In the 2nd column select Run Shell Script.<br />
*Copy and paste this code into the box:<br />
<pre><br />
#!/bin/zsh<br />
<br />
export PATH="/usr/local/bin:${PATH}"<br />
<br />
arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'<br />
</pre><br />
*Save the shortcut somewhere e.g. Applications.<br />
*Above shortcut can be customised to any Wineprefix or game.<br />
*Add an icon by selecting the shortcut, pressing {{key|cmd|I}} to Get Info, then dragging and dropping a PNG file onto the top left of the window.<br />
<br />
== Logging ==<br />
The provided bin/gameportingtoolkit* scripts can be copied onto your path to facilitate different forms of logging and launching. You can run these scripts from any shell; you don’t need to switch to the Rosetta environment first.<br />
<br />
Logging output will appear in the Terminal window in which you launch your game as well as the system log, which can be viewed with the Console app found in Applications ▸ Utilities. Log messages from the Game Porting Toolkit are prefixed with D3DM. By default the gameportingtoolkit* scripts will filter to just the D3DM-prefixed messages.<br />
<br />
== Troubleshooting ==<br />
'''Steam login black screen'''<br />
<br />
Close the Terminal window and then reopen and retry the command, repeat several times.<br />
<br />
Alternate way of launching Steam (after installing):<br />
<pre><br />
MTL_HUD_ENABLED=1 WINEESYNC=1 WINEPREFIX=<path to the Wine bottle you set up> /usr/local/Cellar/game-porting-toolkit/1.0/bin/wine64 'C:\Program Files (x86)/Steam/steam.exe'<br />
</pre><br />
<br />
If still not working then try using [[CrossOver]] and create a Steam bottle, then redirect this WINEPREFIX to that bottle:<br />
<pre><br />
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/" <br />
</pre><br />
<br />
'''Steam crashes straight after opening'''<br />
<br />
Disconnect any external monitors.<br />
<br />
'''Battle.net launcher won't re-launch'''<br />
<br />
Re-install the launcher to reopen, no other fix at the moment.<br />
<br />
'''My game won’t run because it thinks the version of Windows is too old. Some games detect specific minimum versions of Windows and need to be updated.''' Use this script to update your wineprefix with build 19042 which should work for most games e.g. Spider-Man Remastered.<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuild /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuildNumber /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k<br />
</pre><br />
<br />
'''steamwebhelper.exe crashes'''<br />
<br />
This is caused by Steam being run through macOS Ventura or below, upgrade to macOS Sonoma.<br />
<br />
'''My game won't run and crashes with an invalid instruction'''<br />
<br />
AVX and AVX2 games are not supported by Apple's arm64 chipset.<br />
<br />
'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''<br />
<br />
Likely there will be no fixes for any games that use anti-cheat, e.g. Easy Anti Cheat. Some games have workarounds e.g. Elden Ring. Other games that use say Denuvo may also be incompatible until that DRM is removed by the game's developer.<br />
<br />
'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''<br />
<br />
The game porting toolkit’s evaluation environment does not pre-install these runtime support packages. If your game makes use of one of these packages, consider searching for and downloading appropriate installers (.exe or .msi) and installing them to your evaluation environment. Additional runtime installers can be run on your environment by just launching the installer and following its installation instructions:<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe><br />
</pre><br />
<br />
And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller<br />
</pre><br />
<br />
'''Controller issues'''<br />
<br />
Issues may be fixed by enrolling into the Steam beta.<br />
<br />
== Game compatibility list ==<br />
Working games:<br />
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility)<br />
* Cyberpunk 2077<br />
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)<br />
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)<br />
* Elden Ring<br />
* SpongeBob SquarePants: The Cosmic Shake<br />
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]<br />
* Hogwarts Legacy<br />
* Deep Rock Galactic<br />
* Sonic Omens<br />
* Sonic P-06<br />
* Scarlet Nexus<br />
* Metal Gear Solid V: The Phantom Pain<br />
* Dyson Sphere Program (some objects and main character weren't visible before)<br />
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)<br />
* Spider-Man (2018)<br />
* Spider-Man Miles Morales - ''requires Windows ver fix''<br />
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''<br />
* HI-Fi RUSH<br />
* QUBE 2<br />
* Deceive Inc. - works well if launched without EAC<br />
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)<br />
* Crysis Remastered<br />
* Cuphead<br />
* Bloodstained: Ritual of the Night<br />
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise<br />
<br />
Not working well:<br />
* Horizon Zero Dawn - slowdown issues<br />
<br />
Not working yet:<br />
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3<br />
* Among Us<br />
* Tiny Tina's Wonderlands - Intro videos play, dragon animation indicating shader precompilation starts, game freezes, eventually crashes.<br />
* Halo Infinite - Crash on launch<br />
* Street Fighter 6 - Crash on launch<br />
* Many (all?) DX9 games<br />
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game<br />
** Left 4 Dead 2 - Black screen -> crash on launch<br />
** Killing Floor 1 - Crash on launch<br />
** Sonic Mania - Crash on launch<br />
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch</div>John1111https://www.applegamingwiki.com/w/index.php?title=Game_Porting_Toolkit&diff=7584Game Porting Toolkit2023-06-08T07:44:53Z<p>John1111: /* Game compatibility list */</p>
<hr />
<div>Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPTK''') combines Wine with Apple's own D3DMetal which supports DirectX 9-12. This is less user-friendly method of installing Windows games on Apple Silicon Macs compared to [[CrossOver]] or [[Parallels]], however it unlocks the ability to play many DirectX 12 games. Many more games not work using GPTK, however games that use anti-cheat or aggressive DRM generally don't worker do games that require AVX/AVX 2, e.g. The Last of Us Part I.<br />
<br />
== Toolkit install instructions ==<br />
=== Requirements ===<br />
*macOS Sonoma should be used, currently it is in beta. You can download the pkg installer from [https://mrmacintosh.com/macos-sonoma-full-installer-database-download-directly-from-apple/ Mr Macintosh blog].<br />
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.<br />
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.<br />
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.<br />
**If you have an old version Xcode installed, remove it.<br />
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.<br />
<br />
=== Homebrew ===<br />
Note: if you have ever installed Homebrew before, then it is advisable to remove arm64 Homebrew as this can interfere with this build process. Either use a Homebrew uninstall script or delete the folder <code>/opt/homebrew/bin</code>. Otherwise, if you prefer to keep both arm64 and x86 versions of brew installed, you may add a "brew-switcher" to your <code>.zshrc</code> file to allow either version to be used depending on the active architecture. You may follow the steps at the end of this section after installing Brew to achieve this.<br />
<br />
Open Terminal (search in Spotlight on macOS).<br />
<br />
Install Rosetta:<br />
<pre>softwareupdate --install-rosetta</pre><br />
<br />
Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.<br />
<pre>arch -x86_64 zsh</pre><br />
<br />
Install the x86_64 version of Homebrew if you don't already have it.<br />
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre><br />
<br />
Make sure the brew command is on your path:<br />
<pre>which brew</pre><br />
<br />
If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:<br />
<pre>export PATH=/usr/local/bin:${PATH}</pre><br />
<br />
(Optional) If you want to have both arm64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:<br />
<pre>nano ~/.zshrc</pre><br />
<br />
Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:<br />
<pre><br />
if [ "$(arch)" = "arm64" ]; then<br />
eval "$(/opt/homebrew/bin/brew shellenv)"<br />
else<br />
eval "$(/usr/local/bin/brew shellenv)"<br />
fi<br />
</pre><br />
<br />
You may now restart your terminal and use the following command to return to an x86_64 shell:<br />
<pre>arch -x86_64 zsh</pre><br />
Your shell will now select the right installation of Brew, depending on your architecture.<br />
<br />
=== Build ===<br />
Run this command to download Apple tap:<br />
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre><br />
<br />
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer. It can take over 1 hour to complete depending on the speed of your Mac.<br />
<pre>brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
If during installation you see an error such as '''“Error: game-porting-toolkit: unknown or unsupported macOS version: :dunno”, your version of Homebrew doesn’t have macOS Sonoma support. Update to the latest version of Homebrew and try again.'''<br />
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
===Wine prefix ===<br />
A Wine prefix contains a virtual C: drive. You will install the toolkit and your game into this virtual C: drive. Run the following command to create a new Wine prefix named my-game-prefix in your home directory.<br />
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to Windows 10.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
If the “Wine configuration” window does not appear, and no new icon appears in the Dock, verify that you have correctly installed the x86_64 version of Homebrew as well as the game-porting-toolkit formula.<br />
<br />
=== Preparing the toolkit ===<br />
Make sure the Game Porting Toolkit dmg downloaded earlier is mounted at /Volumes/Game Porting Toolkit-1.0. Use this script to copy the Game Porting Toolkit library directory into Wine’s library directory.<br />
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre><br />
<br />
Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:<br />
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre><br />
<br />
Now you are ready to install a launcher or individual Windows games, see below.<br />
<br />
== Steam ==<br />
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.<br />
<br />
'''Install Steam'''<br />
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre><br />
<br />
'''Run Steam'''<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre><br />
<br />
'''Log into Steam'''<br />
<br />
A common issue is that Steam will present with a blank black window.<br />
<br />
Alternate way of launching Steam (after installing):<br />
<pre><br />
MTL_HUD_ENABLED=1 WINEESYNC=1 WINEPREFIX=~/my-game-prefix /usr/local/Cellar/game-porting-toolkit/1.0/bin/wine64 'C:\Program Files (x86)\Steam\steam.exe'<br />
</pre><br />
<br />
If this continues then close the Terminal window and then re-open and try again, repeat until the login screen opens. Now you should be able to download and launch Windows games through Steam.<br />
<br />
== Battle.net ==<br />
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net].<br />
<br />
Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:<br />
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to <code>Windows 10</code>.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
'''Run Battle.net launcher'''<br />
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre><br />
<br />
Be aware that there is an issue launching Battle.net once installed, the only current way to re-login is to 'install' the launcher again. <br />
<br />
Start individual game without the launcher using this command:<br />
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre><br />
<br />
== Epic and GOG.com support ==<br />
This is particularly useful because '''as it currently stands, the real Epic Games Launcher fails to install under the Game Porting Toolkit'''. Heroic supports Epic and GOG.com games.<br />
<br />
* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.<br />
* Open Heroic, and log into your Epic Games and/or GOG.com account.<br />
* Go to the "Wine Manager" and install a '''numbered''' version of Wine, such that it won't auto update- we are going to modify it.<br />
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code><br />
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.<br />
* Right-click on the version of Wine you just installed and press "Show Package Contents".<br />
* Open this directory in the Terminal.<br />
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".<br />
** It should be something like <code>cd ~/Library/Application Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.<br />
* <pre>cd Contents/MacOS</pre><br />
* Remove the existing Wine: <pre>rm wine</pre><br />
* Create a symlink to Game Porting Toolkit's Wine: <br />
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre><br />
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre><br />
* <pre>cd ../Resources</pre><br />
* Remove the existing Wine: <pre>rm -rfv wine</pre><br />
* Create a symlink to Game Porting Toolkit's Wine<br />
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre><br />
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre><br />
* We are now done with Terminal. Install any games you want to try playing.<br />
* Select the game you want to play, and press the settings button in the top-right.<br />
* Make sure the version of Wine you just downloaded and modified is selected.<br />
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/you/my-game-prefix</code>.<br />
* If you Open the "Other" section you can also add any environment variables you want like <code>WINEESYNC=1"</code> and <code>"MTL_HUD_ENABLED=1"</code><br />
* Close the settings and try running the game.<br />
<br />
== Commands ==<br />
Installing individual exe games: open your Wine prefix’s virtual C: drive in Finder (open ~/my-game-prefix/drive_c) and copy your game into an appropriate subdirectory.<br />
<br />
'''A. Standard launching'''<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.<br />
<br />
'''B. Launching without a HUD'''<br />
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
'''C. Launching with Wine ESYNC disabled'''<br />
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
To enter Winecfg:<br />
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre><br />
<br />
== Shortcut ==<br />
You can make a shortcut for Steam for example by using macOS built-in Automator app.<br />
*Open Automator.<br />
*Select New Application.<br />
*In the 2nd column select Run Shell Script.<br />
*Copy and paste this code into the box:<br />
<pre><br />
#!/bin/zsh<br />
<br />
export PATH="/usr/local/bin:${PATH}"<br />
<br />
arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'<br />
</pre><br />
*Save the shortcut somewhere e.g. Applications.<br />
*Above shortcut can be customised to any Wineprefix or game.<br />
*Add an icon by selecting the shortcut, pressing {{key|cmd|I}} to Get Info, then dragging and dropping a PNG file onto the top left of the window.<br />
<br />
== Logging ==<br />
The provided bin/gameportingtoolkit* scripts can be copied onto your path to facilitate different forms of logging and launching. You can run these scripts from any shell; you don’t need to switch to the Rosetta environment first.<br />
<br />
Logging output will appear in the Terminal window in which you launch your game as well as the system log, which can be viewed with the Console app found in Applications ▸ Utilities. Log messages from the Game Porting Toolkit are prefixed with D3DM. By default the gameportingtoolkit* scripts will filter to just the D3DM-prefixed messages.<br />
<br />
== Troubleshooting ==<br />
'''Steam login black screen'''<br />
<br />
Close the Terminal window and then reopen and retry the command, repeat several times.<br />
<br />
Alternate way of launching Steam (after installing):<br />
<pre><br />
MTL_HUD_ENABLED=1 WINEESYNC=1 WINEPREFIX=<path to the Wine bottle you set up> /usr/local/Cellar/game-porting-toolkit/1.0/bin/wine64 'C:\Program Files (x86)/Steam/steam.exe'<br />
</pre><br />
<br />
If still not working then try using [[CrossOver]] and create a Steam bottle, then redirect this WINEPREFIX to that bottle:<br />
<pre><br />
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/" <br />
</pre><br />
<br />
'''Steam crashes straight after opening'''<br />
<br />
Disconnect any external monitors.<br />
<br />
'''Battle.net launcher won't re-launch'''<br />
<br />
Re-install the launcher to reopen, no other fix at the moment.<br />
<br />
'''My game won’t run because it thinks the version of Windows is too old. Some games detect specific minimum versions of Windows and need to be updated.''' Use this script to update your wineprefix with build 19042 which should work for most games e.g. Spider-Man Remastered.<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuild /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuildNumber /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k<br />
</pre><br />
<br />
'''steamwebhelper.exe crashes'''<br />
<br />
This is caused by Steam being run through macOS Ventura or below, upgrade to macOS Sonoma.<br />
<br />
'''My game won't run and crashes with an invalid instruction'''<br />
<br />
AVX and AVX2 games are not supported by Apple's arm64 chipset.<br />
<br />
'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''<br />
<br />
Likely there will be no fixes for any games that use anti-cheat, e.g. Easy Anti Cheat. Some games have workarounds e.g. Elden Ring. Other games that use say Denuvo may also be incompatible until that DRM is removed by the game's developer.<br />
<br />
'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''<br />
<br />
The game porting toolkit’s evaluation environment does not pre-install these runtime support packages. If your game makes use of one of these packages, consider searching for and downloading appropriate installers (.exe or .msi) and installing them to your evaluation environment. Additional runtime installers can be run on your environment by just launching the installer and following its installation instructions:<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe><br />
</pre><br />
<br />
And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller<br />
</pre><br />
<br />
'''Controller issues'''<br />
<br />
Issues may be fixed by enrolling into the Steam beta.<br />
<br />
== Game compatibility list ==<br />
Working games:<br />
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility)<br />
* Cyberpunk 2077<br />
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)<br />
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)<br />
* Elden Ring<br />
* SpongeBob SquarePants: The Cosmic Shake<br />
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]<br />
* Hogwarts Legacy<br />
* Deep Rock Galactic<br />
* Sonic Omens<br />
* Sonic P-06<br />
* Scarlet Nexus<br />
* Metal Gear Solid V: The Phantom Pain<br />
* Dyson Sphere Program (some objects and main character weren't visible before)<br />
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)<br />
* Spider-Man (2018)<br />
* Spider-Man Miles Morales - ''requires Windows ver fix''<br />
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''<br />
* HI-Fi RUSH<br />
* QUBE 2<br />
* Deceive Inc. - works well if launched without EAC<br />
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)<br />
* Crysis Remastered<br />
* Cuphead<br />
* Bloodstained: Ritual of the Night<br />
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise<br />
<br />
Not working well:<br />
* Horizon Zero Dawn - slowdown issues<br />
<br />
Not working yet:<br />
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3<br />
* Among Us<br />
* Tiny Tina's Wonderlands - Intro videos play, dragon animation indicating shader precompilation starts, game freezes, eventually crashes.<br />
* Halo Infinite - Crash on launch<br />
* Many (all?) DX9 games<br />
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game<br />
** Left 4 Dead 2 - Black screen -> crash on launch<br />
** Killing Floor 1 - Crash on launch<br />
** Sonic Mania - Crash on launch<br />
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch<br />
** Street Fighter 6 - Crash on launch</div>John1111https://www.applegamingwiki.com/w/index.php?title=Game_Porting_Toolkit&diff=7517Game Porting Toolkit2023-06-07T16:24:24Z<p>John1111: </p>
<hr />
<div>Stub page for Game Porting Toolkit - Apple.<br />
<br />
Download Game Porting Toolkit here (requires appleId): https://developer.apple.com/download/all/?q=game%20porting%20toolkit<br />
<br />
Working games:<br />
* Cyberpunk 2077<br />
* Elden Ring<br />
* SpongeBob SquarePants: The Cosmic Shake<br />
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]<br />
* Hogwarts Legacy - ''requires Windows ver fix'' [https://www.reddit.com/r/macgaming/comments/14342uz/comment/jn7w2qh/?utm_source=reddit&utm_medium=web2x&context=3 ]<br />
* Deep Rock Galactic<br />
* Sonic Omens<br />
* Spider-Man (2018)<br />
* Spider-Man Miles Morales - ''requires Windows ver fix''<br />
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''<br />
* Deep Rock Galactic<br />
* HI-Fi RUSH<br />
<br />
Not working so well:<br />
* Horizon Zero Dawn - slowdown issues<br />
<br />
<br />
=== Toolkit Installation ===<br />
<br />
Requires:<br />
<br />
*macOS Sonoma<br />
*Ensure the Command Line Tools for Xcode 15 beta are installed. Visit https://developer.apple.com/downloads to download these tools.<br />
*If you have an old version Xcode installed, remove it<br />
*Command Line Tools Beta 15 must be installed: https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_for_Xcode_15_beta/Command_Line_Tools_for_Xcode_15_beta.dmg<br />
<br />
Install Rosetta:<br />
<br />
<pre>softwareupdate --install-rosetta</pre><br />
<br />
Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.<br />
<pre>arch -x86_64 zsh</pre><br />
<br />
Install the x86_64 version of Homebrew if you don't already have it.<br />
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre><br />
<br />
Make sure the brew command is on your path:<br />
<pre>which brew</pre><br />
<br />
If this command does not print /usr/local/bin/brew, you must either modify your PATH to put /usr/local/bin first, or fully specify the path to brew in the subsequent commands.<br />
<br />
Tap the Apple Homebrew tap, which can be found at https://github.com/apple:<br />
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre><br />
<br />
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer.<br />
<pre>brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
If during installation you see an error such as “Error: game-porting-toolkit: unknown or unsupported macOS version: :dunno”, your version of Homebrew doesn’t have macOS Sonoma support. Update to the latest version of Homebrew and try again.<br />
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
2. Create a new Wine prefix for your Game Porting Toolkit environment<br />
<br />
A Wine prefix contains a virtual C: drive. You will install the toolkit and your game into this virtual C: drive. Run the following command to create a new Wine prefix named my-game-prefix in your home directory.<br />
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to Windows 10.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
If the “Wine configuration” window does not appear, and no new icon appears in the Dock, verify that you have correctly installed the x86_64 version of Homebrew as well as the game-porting-toolkit formula.<br />
<br />
3. Install the toolkit into the Wine prefix<br />
<br />
The graphics bridge libraries need to be placed inside your Wine prefix in order to finalize your game evaluation environment. These instructions assume you have mounted the Game Porting Toolkit at /Volumes/Game Porting Toolkit-1.0.<br />
*Copy the Game Porting Toolkit library directory into Wine’s library directory.<br />
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre><br />
<br />
<br />
==== Launch your game ====<br />
<br />
Open your Wine prefix’s virtual C: drive in Finder (open ~/my-game-prefix/drive_c) and copy your game into an appropriate subdirectory.<br />
<br />
The provided bin/gameportingtoolkit* scripts can be copied onto your path to facilitate different forms of logging and launching. You can run these scripts from any shell; you don’t need to switch to the Rosetta environment first.<br />
<br />
Put the 3 scripts from the Game Porting Toolkit DMG into here:<br />
<pre>/usr/local/bin</pre><br />
You can use Cmd+Shift+G and enter the path, or you can go to root in Finder and press Cmd+Shift+. and reveal hidden folders.<br />
<br />
A. Standard launching:<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.<br />
<br />
B. Launching without a HUD<br />
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Launches your game without the extended Metal Performance HUD visible.<br />
<br />
C. Launching with Wine ESYNC disabled<br />
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Finally, the no-esync versions of the script disable Wine's ESYNC option, a common compatibility flag. If your game experiences issues with multithreading, or you get an error message about running out of files, you can try launching your game without this Wine environment variable enabled to see if disabling esync clears the problem.<br />
<br />
=== Logging ===<br />
<br />
Logging output will appear in the Terminal window in which you launch your game as well as the system log, which can be viewed with the Console app found in Applications ▸ Utilities. Log messages from the Game Porting Toolkit are prefixed with D3DM. By default the gameportingtoolkit* scripts will filter to just the D3DM-prefixed messages.<br />
<br />
=== Troubleshooting ===<br />
<br />
'''Steam login black screen'''<br />
<br />
Close the Terminal window and then reopen and retry the command, repeat several times.<br />
<br />
Alternate way of launching Steam (after installing):<br />
<pre><br />
MTL_HUD_ENABLED=1 WINEESYNC=1 WINEPREFIX=<path to the Wine bottle you set up> /usr/local/Cellar/game-porting-toolkit/1.0/bin/wine64 'C:\Program Files (x86)/Steam/steam.exe<br />
</pre><br />
<br />
If still not working then try using [[CrossOver]] and create a Steam bottle, then redirect this WINEPREFIX to that bottle:<br />
<pre><br />
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/" <br />
</pre><br />
<br />
'''Battle.net launcher won't re-launch'''<br />
<br />
Re-install the launcher to reopen, no other fix at the moment.<br />
<br />
'''My game won’t run because it thinks the version of Windows is too old. Some games detect specific minimum versions of Windows and need to be updated. Use this script to update your wineprefix with build 19042 which should work for most games e.g. Hogwarts Legacy.'''<br />
<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuild /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuildNumber /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k<br />
</pre><br />
<br />
'''My game won't run and crashes with an invalid instruction'''<br />
<br />
Invalid instruction crashes are often (but not always) caused when Rosetta 2 is unable to translate AVX/AVX2 instructions. You may be able to recompile a version of your game without AVX/AVX2 instructions in order to evaluate its potential on Apple Silicon with the Game Porting Toolkit when you hit this error. When porting your code natively to Apple Silicon, NEON instructions are a high-performance replacement for AVX/AVX2.<br />
<br />
'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''<br />
<br />
You may be able to rebuild a custom version of your game in your Windows development environment with anti-cheat or DRM disabled for your own evaluation purposes. When porting your code natively to Apple Silicon and macOS, contact your anti-cheat or DRM provider—most have native Apple Silicon solutions for your native build.<br />
<br />
<br />
'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''<br />
<br />
The game porting toolkit’s evaluation environment does not pre-install these runtime support packages. If your game makes use of one of these packages, consider searching for and downloading appropriate installers (.exe or .msi) and installing them to your evaluation environment. Additional runtime installers can be run on your environment by just launching the installer and following its installation instructions:<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe><br />
</pre><br />
<br />
And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller<br />
</pre></div>John1111https://www.applegamingwiki.com/w/index.php?title=Game_Porting_Toolkit&diff=7516Game Porting Toolkit2023-06-07T16:23:34Z<p>John1111: </p>
<hr />
<div>Stub page for Game Porting Toolkit - Apple.<br />
<br />
Download Game Porting Toolkit here (requires appleId): https://developer.apple.com/download/all/?q=game%20porting%20toolkit<br />
<br />
Working games:<br />
* Cyberpunk 2077<br />
* Elden Ring<br />
* SpongeBob SquarePants: The Cosmic Shake<br />
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]<br />
* Hogwarts Legacy - ''requires Windows ver fix'' [https://www.reddit.com/r/macgaming/comments/14342uz/comment/jn7w2qh/?utm_source=reddit&utm_medium=web2x&context=3 ]<br />
* Deep Rock Galactic<br />
* Sonic Omens<br />
* Spider-Man (2018)<br />
* Spider-Man Miles Morales - requires Windows ver fix<br />
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''<br />
* Deep Rock Galactic<br />
* HI-Fi RUSH<br />
<br />
Not working so well:<br />
* Horizon Zero Dawn - slowdown issues<br />
<br />
<br />
=== Toolkit Installation ===<br />
<br />
Requires:<br />
<br />
*macOS Sonoma<br />
*Ensure the Command Line Tools for Xcode 15 beta are installed. Visit https://developer.apple.com/downloads to download these tools.<br />
*If you have an old version Xcode installed, remove it<br />
*Command Line Tools Beta 15 must be installed: https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_for_Xcode_15_beta/Command_Line_Tools_for_Xcode_15_beta.dmg<br />
<br />
Install Rosetta:<br />
<br />
<pre>softwareupdate --install-rosetta</pre><br />
<br />
Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.<br />
<pre>arch -x86_64 zsh</pre><br />
<br />
Install the x86_64 version of Homebrew if you don't already have it.<br />
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre><br />
<br />
Make sure the brew command is on your path:<br />
<pre>which brew</pre><br />
<br />
If this command does not print /usr/local/bin/brew, you must either modify your PATH to put /usr/local/bin first, or fully specify the path to brew in the subsequent commands.<br />
<br />
Tap the Apple Homebrew tap, which can be found at https://github.com/apple:<br />
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre><br />
<br />
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer.<br />
<pre>brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
If during installation you see an error such as “Error: game-porting-toolkit: unknown or unsupported macOS version: :dunno”, your version of Homebrew doesn’t have macOS Sonoma support. Update to the latest version of Homebrew and try again.<br />
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
2. Create a new Wine prefix for your Game Porting Toolkit environment<br />
<br />
A Wine prefix contains a virtual C: drive. You will install the toolkit and your game into this virtual C: drive. Run the following command to create a new Wine prefix named my-game-prefix in your home directory.<br />
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to Windows 10.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
If the “Wine configuration” window does not appear, and no new icon appears in the Dock, verify that you have correctly installed the x86_64 version of Homebrew as well as the game-porting-toolkit formula.<br />
<br />
3. Install the toolkit into the Wine prefix<br />
<br />
The graphics bridge libraries need to be placed inside your Wine prefix in order to finalize your game evaluation environment. These instructions assume you have mounted the Game Porting Toolkit at /Volumes/Game Porting Toolkit-1.0.<br />
*Copy the Game Porting Toolkit library directory into Wine’s library directory.<br />
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre><br />
<br />
<br />
==== Launch your game ====<br />
<br />
Open your Wine prefix’s virtual C: drive in Finder (open ~/my-game-prefix/drive_c) and copy your game into an appropriate subdirectory.<br />
<br />
The provided bin/gameportingtoolkit* scripts can be copied onto your path to facilitate different forms of logging and launching. You can run these scripts from any shell; you don’t need to switch to the Rosetta environment first.<br />
<br />
Put the 3 scripts from the Game Porting Toolkit DMG into here:<br />
<pre>/usr/local/bin</pre><br />
You can use Cmd+Shift+G and enter the path, or you can go to root in Finder and press Cmd+Shift+. and reveal hidden folders.<br />
<br />
A. Standard launching:<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.<br />
<br />
B. Launching without a HUD<br />
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Launches your game without the extended Metal Performance HUD visible.<br />
<br />
C. Launching with Wine ESYNC disabled<br />
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Finally, the no-esync versions of the script disable Wine's ESYNC option, a common compatibility flag. If your game experiences issues with multithreading, or you get an error message about running out of files, you can try launching your game without this Wine environment variable enabled to see if disabling esync clears the problem.<br />
<br />
=== Logging ===<br />
<br />
Logging output will appear in the Terminal window in which you launch your game as well as the system log, which can be viewed with the Console app found in Applications ▸ Utilities. Log messages from the Game Porting Toolkit are prefixed with D3DM. By default the gameportingtoolkit* scripts will filter to just the D3DM-prefixed messages.<br />
<br />
=== Troubleshooting ===<br />
<br />
'''Steam login black screen'''<br />
<br />
Close the Terminal window and then reopen and retry the command, repeat several times.<br />
<br />
Alternate way of launching Steam (after installing):<br />
<pre><br />
MTL_HUD_ENABLED=1 WINEESYNC=1 WINEPREFIX=<path to the Wine bottle you set up> /usr/local/Cellar/game-porting-toolkit/1.0/bin/wine64 'C:\Program Files (x86)/Steam/steam.exe<br />
</pre><br />
<br />
If still not working then try using [[CrossOver]] and create a Steam bottle, then redirect this WINEPREFIX to that bottle:<br />
<pre><br />
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/" <br />
</pre><br />
<br />
'''Battle.net launcher won't re-launch'''<br />
<br />
Re-install the launcher to reopen, no other fix at the moment.<br />
<br />
'''My game won’t run because it thinks the version of Windows is too old. Some games detect specific minimum versions of Windows and need to be updated. Use this script to update your wineprefix with build 19042 which should work for most games e.g. Hogwarts Legacy.'''<br />
<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuild /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuildNumber /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k<br />
</pre><br />
<br />
'''My game won't run and crashes with an invalid instruction'''<br />
<br />
Invalid instruction crashes are often (but not always) caused when Rosetta 2 is unable to translate AVX/AVX2 instructions. You may be able to recompile a version of your game without AVX/AVX2 instructions in order to evaluate its potential on Apple Silicon with the Game Porting Toolkit when you hit this error. When porting your code natively to Apple Silicon, NEON instructions are a high-performance replacement for AVX/AVX2.<br />
<br />
'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''<br />
<br />
You may be able to rebuild a custom version of your game in your Windows development environment with anti-cheat or DRM disabled for your own evaluation purposes. When porting your code natively to Apple Silicon and macOS, contact your anti-cheat or DRM provider—most have native Apple Silicon solutions for your native build.<br />
<br />
<br />
'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''<br />
<br />
The game porting toolkit’s evaluation environment does not pre-install these runtime support packages. If your game makes use of one of these packages, consider searching for and downloading appropriate installers (.exe or .msi) and installing them to your evaluation environment. Additional runtime installers can be run on your environment by just launching the installer and following its installation instructions:<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe><br />
</pre?<br />
<br />
And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller<br />
</pre></div>John1111https://www.applegamingwiki.com/w/index.php?title=Game_Porting_Toolkit&diff=7509Game Porting Toolkit2023-06-07T14:00:11Z<p>John1111: </p>
<hr />
<div>Stub page for Game Porting Toolkit - Apple.<br />
<br />
Download Game Porting Toolkit here (requires appleId): https://developer.apple.com/download/all/?q=game%20porting%20toolkit<br />
<br />
Working games:<br />
* Cyberpunk 2077<br />
* Elden Ring<br />
* SpongeBob SquarePants: The Cosmic Shake<br />
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]<br />
* Hogwarts Legacy [https://www.reddit.com/r/macgaming/comments/14342uz/comment/jn7w2qh/?utm_source=reddit&utm_medium=web2x&context=3 ]<br />
* Deep Rock Galactic<br />
* Sonic Omens<br />
* Spider-Man (2018)<br />
* Warframe<br />
* Deep Rock Galactic<br />
<br />
Not working so well:<br />
* Horizon Zero Dawn - slowdown issues<br />
<br />
<br />
=== Toolkit Installation ===<br />
<br />
Requires:<br />
<br />
*macOS Sonoma<br />
*Ensure the Command Line Tools for Xcode 15 beta are installed. Visit https://developer.apple.com/downloads to download these tools.<br />
*If you have an old version Xcode installed, remove it<br />
*Command Line Tools Beta 15 must be installed: https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_for_Xcode_15_beta/Command_Line_Tools_for_Xcode_15_beta.dmg<br />
<br />
Install Rosetta:<br />
<br />
<pre>softwareupdate --install-rosetta</pre><br />
<br />
Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.<br />
<pre>arch -x86_64 zsh</pre><br />
<br />
Install the x86_64 version of Homebrew if you don't already have it.<br />
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre><br />
<br />
Make sure the brew command is on your path:<br />
<pre>which brew</pre><br />
<br />
If this command does not print /usr/local/bin/brew, you must either modify your PATH to put /usr/local/bin first, or fully specify the path to brew in the subsequent commands.<br />
<br />
Tap the Apple Homebrew tap, which can be found at https://github.com/apple:<br />
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre><br />
<br />
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer.<br />
<pre>brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
If during installation you see an error such as “Error: game-porting-toolkit: unknown or unsupported macOS version: :dunno”, your version of Homebrew doesn’t have macOS Sonoma support. Update to the latest version of Homebrew and try again.<br />
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
2. Create a new Wine prefix for your Game Porting Toolkit environment<br />
<br />
A Wine prefix contains a virtual C: drive. You will install the toolkit and your game into this virtual C: drive. Run the following command to create a new Wine prefix named my-game-prefix in your home directory.<br />
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to Windows 10.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
If the “Wine configuration” window does not appear, and no new icon appears in the Dock, verify that you have correctly installed the x86_64 version of Homebrew as well as the game-porting-toolkit formula.<br />
<br />
3. Install the toolkit into the Wine prefix<br />
<br />
The graphics bridge libraries need to be placed inside your Wine prefix in order to finalize your game evaluation environment. These instructions assume you have mounted the Game Porting Toolkit at /Volumes/Game Porting Toolkit-1.0.<br />
*Copy the Game Porting Toolkit library directory into Wine’s library directory.<br />
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre><br />
<br />
<br />
==== Launch your game ====<br />
<br />
Open your Wine prefix’s virtual C: drive in Finder (open ~/my-game-prefix/drive_c) and copy your game into an appropriate subdirectory.<br />
<br />
The provided bin/gameportingtoolkit* scripts can be copied onto your path to facilitate different forms of logging and launching. You can run these scripts from any shell; you don’t need to switch to the Rosetta environment first.<br />
<br />
Put the 3 scripts from the Game Porting Toolkit DMG into here:<br />
<pre>/usr/local/bin</pre><br />
You can use Cmd+Shift+G and enter the path, or you can go to root in Finder and press Cmd+Shift+. and reveal hidden folders.<br />
<br />
A. Standard launching:<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.<br />
<br />
B. Launching without a HUD<br />
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Launches your game without the extended Metal Performance HUD visible.<br />
<br />
C. Launching with Wine ESYNC disabled<br />
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Finally, the no-esync versions of the script disable Wine's ESYNC option, a common compatibility flag. If your game experiences issues with multithreading, or you get an error message about running out of files, you can try launching your game without this Wine environment variable enabled to see if disabling esync clears the problem.<br />
<br />
<br />
<br />
=== Logging ===<br />
<br />
Logging output will appear in the Terminal window in which you launch your game as well as the system log, which can be viewed with the Console app found in Applications ▸ Utilities. Log messages from the Game Porting Toolkit are prefixed with D3DM. By default the gameportingtoolkit* scripts will filter to just the D3DM-prefixed messages.<br />
<br />
<br />
<br />
=== Troubleshooting ===<br />
<br />
'''My game won’t run because it thinks the version of Windows is too old. Some games detect specific minimum versions of Windows and need to be updated. Use this script to update your wineprefix with build 19042 which should work for most games e.g. Hogwarts Legacy.'''<br />
<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuild /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuildNumber /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k<br />
</pre><br />
<br />
'''My game won't run and crashes with an invalid instruction'''<br />
<br />
Invalid instruction crashes are often (but not always) caused when Rosetta 2 is unable to translate AVX/AVX2 instructions. You may be able to recompile a version of your game without AVX/AVX2 instructions in order to evaluate its potential on Apple Silicon with the Game Porting Toolkit when you hit this error. When porting your code natively to Apple Silicon, NEON instructions are a high-performance replacement for AVX/AVX2.<br />
<br />
<br />
'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''<br />
<br />
You may be able to rebuild a custom version of your game in your Windows development environment with anti-cheat or DRM disabled for your own evaluation purposes. When porting your code natively to Apple Silicon and macOS, contact your anti-cheat or DRM provider—most have native Apple Silicon solutions for your native build.<br />
<br />
<br />
<br />
'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''<br />
<br />
The game porting toolkit’s evaluation environment does not pre-install these runtime support packages. If your game makes use of one of these packages, consider searching for and downloading appropriate installers (.exe or .msi) and installing them to your evaluation environment. Additional runtime installers can be run on your environment by just launching the installer and following its installation instructions:<br />
<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe><br />
<br />
And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:<br />
<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller</div>John1111https://www.applegamingwiki.com/w/index.php?title=Game_Porting_Toolkit&diff=7508Game Porting Toolkit2023-06-07T13:58:55Z<p>John1111: </p>
<hr />
<div>Stub page for Game Porting Toolkit - Apple.<br />
<br />
Download Game Porting Toolkit here (requires appleId): https://developer.apple.com/download/all/?q=game%20porting%20toolkit<br />
<br />
Working games:<br />
* Cyberpunk 2077<br />
* Elden Ring<br />
* SpongeBob SquarePants: The Cosmic Shake<br />
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]<br />
* Hogwarts Legacy [https://www.reddit.com/r/macgaming/comments/14342uz/comment/jn7w2qh/?utm_source=reddit&utm_medium=web2x&context=3 ]<br />
* Deep Rock Galactic<br />
* Sonic Omens<br />
* Spider-Man (2018)<br />
* Warframe<br />
<br />
Not working so well:<br />
* Horizon Zero Dawn - slowdown issues<br />
<br />
<br />
=== Toolkit Installation ===<br />
<br />
Requires:<br />
<br />
*macOS Sonoma<br />
*Ensure the Command Line Tools for Xcode 15 beta are installed. Visit https://developer.apple.com/downloads to download these tools.<br />
*If you have an old version Xcode installed, remove it<br />
*Command Line Tools Beta 15 must be installed: https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_for_Xcode_15_beta/Command_Line_Tools_for_Xcode_15_beta.dmg<br />
<br />
Install Rosetta:<br />
<br />
<pre>softwareupdate --install-rosetta</pre><br />
<br />
Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.<br />
<pre>arch -x86_64 zsh</pre><br />
<br />
Install the x86_64 version of Homebrew if you don't already have it.<br />
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre><br />
<br />
Make sure the brew command is on your path:<br />
<pre>which brew</pre><br />
<br />
If this command does not print /usr/local/bin/brew, you must either modify your PATH to put /usr/local/bin first, or fully specify the path to brew in the subsequent commands.<br />
<br />
Tap the Apple Homebrew tap, which can be found at https://github.com/apple:<br />
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre><br />
<br />
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer.<br />
<pre>brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
If during installation you see an error such as “Error: game-porting-toolkit: unknown or unsupported macOS version: :dunno”, your version of Homebrew doesn’t have macOS Sonoma support. Update to the latest version of Homebrew and try again.<br />
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
2. Create a new Wine prefix for your Game Porting Toolkit environment<br />
<br />
A Wine prefix contains a virtual C: drive. You will install the toolkit and your game into this virtual C: drive. Run the following command to create a new Wine prefix named my-game-prefix in your home directory.<br />
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to Windows 10.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
If the “Wine configuration” window does not appear, and no new icon appears in the Dock, verify that you have correctly installed the x86_64 version of Homebrew as well as the game-porting-toolkit formula.<br />
<br />
3. Install the toolkit into the Wine prefix<br />
<br />
The graphics bridge libraries need to be placed inside your Wine prefix in order to finalize your game evaluation environment. These instructions assume you have mounted the Game Porting Toolkit at /Volumes/Game Porting Toolkit-1.0.<br />
*Copy the Game Porting Toolkit library directory into Wine’s library directory.<br />
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre><br />
<br />
<br />
==== Launch your game ====<br />
<br />
Open your Wine prefix’s virtual C: drive in Finder (open ~/my-game-prefix/drive_c) and copy your game into an appropriate subdirectory.<br />
<br />
The provided bin/gameportingtoolkit* scripts can be copied onto your path to facilitate different forms of logging and launching. You can run these scripts from any shell; you don’t need to switch to the Rosetta environment first.<br />
<br />
Put the 3 scripts from the Game Porting Toolkit DMG into here:<br />
<pre>/usr/local/bin</pre><br />
You can use Cmd+Shift+G and enter the path, or you can go to root in Finder and press Cmd+Shift+. and reveal hidden folders.<br />
<br />
A. Standard launching:<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.<br />
<br />
B. Launching without a HUD<br />
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Launches your game without the extended Metal Performance HUD visible.<br />
<br />
C. Launching with Wine ESYNC disabled<br />
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Finally, the no-esync versions of the script disable Wine's ESYNC option, a common compatibility flag. If your game experiences issues with multithreading, or you get an error message about running out of files, you can try launching your game without this Wine environment variable enabled to see if disabling esync clears the problem.<br />
<br />
<br />
<br />
=== Logging ===<br />
<br />
Logging output will appear in the Terminal window in which you launch your game as well as the system log, which can be viewed with the Console app found in Applications ▸ Utilities. Log messages from the Game Porting Toolkit are prefixed with D3DM. By default the gameportingtoolkit* scripts will filter to just the D3DM-prefixed messages.<br />
<br />
<br />
<br />
=== Troubleshooting ===<br />
<br />
'''My game won’t run because it thinks the version of Windows is too old. Some games detect specific minimum versions of Windows and need to be updated. Use this script to update your wineprefix with build 19042 which should work for most games e.g. Hogwarts Legacy.'''<br />
<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuild /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuildNumber /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k<br />
</pre><br />
<br />
'''My game won't run and crashes with an invalid instruction'''<br />
<br />
Invalid instruction crashes are often (but not always) caused when Rosetta 2 is unable to translate AVX/AVX2 instructions. You may be able to recompile a version of your game without AVX/AVX2 instructions in order to evaluate its potential on Apple Silicon with the Game Porting Toolkit when you hit this error. When porting your code natively to Apple Silicon, NEON instructions are a high-performance replacement for AVX/AVX2.<br />
<br />
<br />
'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''<br />
<br />
You may be able to rebuild a custom version of your game in your Windows development environment with anti-cheat or DRM disabled for your own evaluation purposes. When porting your code natively to Apple Silicon and macOS, contact your anti-cheat or DRM provider—most have native Apple Silicon solutions for your native build.<br />
<br />
<br />
<br />
'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''<br />
<br />
The game porting toolkit’s evaluation environment does not pre-install these runtime support packages. If your game makes use of one of these packages, consider searching for and downloading appropriate installers (.exe or .msi) and installing them to your evaluation environment. Additional runtime installers can be run on your environment by just launching the installer and following its installation instructions:<br />
<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe><br />
<br />
And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:<br />
<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller</div>John1111https://www.applegamingwiki.com/w/index.php?title=Game_Porting_Toolkit&diff=7507Game Porting Toolkit2023-06-07T13:55:54Z<p>John1111: </p>
<hr />
<div>Stub page for Game Porting Toolkit - Apple.<br />
<br />
Download Game Porting Toolkit here (requires appleId): https://developer.apple.com/download/all/?q=game%20porting%20toolkit<br />
<br />
Working games:<br />
* Cyberpunk 2077<br />
* Elden Ring<br />
* SpongeBob SquarePants: The Cosmic Shake<br />
* Diablo IV<br />
* Hogwarts Legacy<br />
* Deep Rock Galactic<br />
* Sonic Omens<br />
* Spider-Man (2018)<br />
* Warframe<br />
<br />
Not working so well:<br />
* Horizon Zero Dawn - slowdown issues<br />
<br />
<br />
=== Toolkit Installation ===<br />
<br />
Requires:<br />
<br />
*macOS Sonoma<br />
*Ensure the Command Line Tools for Xcode 15 beta are installed. Visit https://developer.apple.com/downloads to download these tools.<br />
*If you have an old version Xcode installed, remove it<br />
*Command Line Tools Beta 15 must be installed: https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_for_Xcode_15_beta/Command_Line_Tools_for_Xcode_15_beta.dmg<br />
<br />
Install Rosetta:<br />
<br />
<pre>softwareupdate --install-rosetta</pre><br />
<br />
Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.<br />
<pre>arch -x86_64 zsh</pre><br />
<br />
Install the x86_64 version of Homebrew if you don't already have it.<br />
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre><br />
<br />
Make sure the brew command is on your path:<br />
<pre>which brew</pre><br />
<br />
If this command does not print /usr/local/bin/brew, you must either modify your PATH to put /usr/local/bin first, or fully specify the path to brew in the subsequent commands.<br />
<br />
Tap the Apple Homebrew tap, which can be found at https://github.com/apple:<br />
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre><br />
<br />
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer.<br />
<pre>brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
If during installation you see an error such as “Error: game-porting-toolkit: unknown or unsupported macOS version: :dunno”, your version of Homebrew doesn’t have macOS Sonoma support. Update to the latest version of Homebrew and try again.<br />
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
2. Create a new Wine prefix for your Game Porting Toolkit environment<br />
<br />
A Wine prefix contains a virtual C: drive. You will install the toolkit and your game into this virtual C: drive. Run the following command to create a new Wine prefix named my-game-prefix in your home directory.<br />
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to Windows 10.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
If the “Wine configuration” window does not appear, and no new icon appears in the Dock, verify that you have correctly installed the x86_64 version of Homebrew as well as the game-porting-toolkit formula.<br />
<br />
3. Install the toolkit into the Wine prefix<br />
<br />
The graphics bridge libraries need to be placed inside your Wine prefix in order to finalize your game evaluation environment. These instructions assume you have mounted the Game Porting Toolkit at /Volumes/Game Porting Toolkit-1.0.<br />
*Copy the Game Porting Toolkit library directory into Wine’s library directory.<br />
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre><br />
<br />
<br />
==== Launch your game ====<br />
<br />
Open your Wine prefix’s virtual C: drive in Finder (open ~/my-game-prefix/drive_c) and copy your game into an appropriate subdirectory.<br />
<br />
The provided bin/gameportingtoolkit* scripts can be copied onto your path to facilitate different forms of logging and launching. You can run these scripts from any shell; you don’t need to switch to the Rosetta environment first.<br />
<br />
Put the 3 scripts from the Game Porting Toolkit DMG into here:<br />
<pre>/usr/local/bin</pre><br />
You can use Cmd+Shift+G and enter the path, or you can go to root in Finder and press Cmd+Shift+. and reveal hidden folders.<br />
<br />
A. Standard launching:<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.<br />
<br />
B. Launching without a HUD<br />
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Launches your game without the extended Metal Performance HUD visible.<br />
<br />
C. Launching with Wine ESYNC disabled<br />
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Finally, the no-esync versions of the script disable Wine's ESYNC option, a common compatibility flag. If your game experiences issues with multithreading, or you get an error message about running out of files, you can try launching your game without this Wine environment variable enabled to see if disabling esync clears the problem.<br />
<br />
<br />
<br />
=== Logging ===<br />
<br />
Logging output will appear in the Terminal window in which you launch your game as well as the system log, which can be viewed with the Console app found in Applications ▸ Utilities. Log messages from the Game Porting Toolkit are prefixed with D3DM. By default the gameportingtoolkit* scripts will filter to just the D3DM-prefixed messages.<br />
<br />
<br />
<br />
=== Troubleshooting ===<br />
<br />
My game won’t run because it thinks the version of Windows is too old. Some games detect specific minimum versions of Windows and need to be updated. Use this script to update your wineprefix with build 19042 which should work for most games e.g. Hogwarts Legacy.<br />
<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuild /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuildNumber /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k<br />
</pre><br />
<br />
My game won't run and crashes with an invalid instruction<br />
<br />
Invalid instruction crashes are often (but not always) caused when Rosetta 2 is unable to translate AVX/AVX2 instructions. You may be able to recompile a version of your game without AVX/AVX2 instructions in order to evaluate its potential on Apple Silicon with the Game Porting Toolkit when you hit this error. When porting your code natively to Apple Silicon, NEON instructions are a high-performance replacement for AVX/AVX2.<br />
<br />
<br />
My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.<br />
<br />
You may be able to rebuild a custom version of your game in your Windows development environment with anti-cheat or DRM disabled for your own evaluation purposes. When porting your code natively to Apple Silicon and macOS, contact your anti-cheat or DRM provider—most have native Apple Silicon solutions for your native build.<br />
<br />
<br />
<br />
My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.<br />
<br />
The game porting toolkit’s evaluation environment does not pre-install these runtime support packages. If your game makes use of one of these packages, consider searching for and downloading appropriate installers (.exe or .msi) and installing them to your evaluation environment. Additional runtime installers can be run on your environment by just launching the installer and following its installation instructions:<br />
<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe><br />
<br />
And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:<br />
<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller</div>John1111https://www.applegamingwiki.com/w/index.php?title=Game_Porting_Toolkit&diff=7506Game Porting Toolkit2023-06-07T13:03:15Z<p>John1111: </p>
<hr />
<div>Stub page for Game Porting Toolkit - Apple.<br />
<br />
Download Game Porting Toolkit here: https://developer.apple.com/download/all/?q=game%20porting%20toolkit<br />
<br />
<br />
My game won’t run because it thinks the version of Windows is too old. Some games detect specific minimum versions of Windows and need to be updated. Use this script to update your wineprefix with build 19042 which should work for most games e.g. Hogwarts Legacy.<br />
<pre><br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuild /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' /v CurrentBuildNumber /t REG_SZ /d 19042 /f<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k<br />
</pre><br />
<br />
Working games:<br />
* Cyberpunk 2077<br />
* Elden Ring<br />
* SpongeBob SquarePants: The Cosmic Shake<br />
* Diablo IV<br />
* Hogwarts Legacy<br />
* Deep Rock Galactic<br />
* Sonic Omens<br />
* Spider-Man (2018)<br />
* Warframe<br />
<br />
Not working so well:<br />
* Horizon Zero Dawn - slowdown issues<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Requires:<br />
*macOS Sonoma<br />
*Ensure the Command Line Tools for Xcode 15 beta are installed. Visit https://developer.apple.com/downloads to download these tools.<br />
*If you have an old version Xcode installed, remove it<br />
*Command Line Tools Beta 15 must be installed: https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_for_Xcode_15_beta/Command_Line_Tools_for_Xcode_15_beta.dmg<br />
<br />
Install Rosetta:<br />
<pre>softwareupdate --install-rosetta</pre><br />
<br />
Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.<br />
<pre>arch -x86_64 zsh</pre><br />
<br />
Install the x86_64 version of Homebrew if you don't already have it.<br />
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre><br />
<br />
Make sure the brew command is on your path:<br />
<pre>which brew</pre><br />
<br />
If this command does not print /usr/local/bin/brew, you must either modify your PATH to put /usr/local/bin first, or fully specify the path to brew in the subsequent commands.<br />
<br />
Tap the Apple Homebrew tap, which can be found at https://github.com/apple:<br />
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre><br />
<br />
Install the game-porting-toolkit formula. This formula downloads and compiles several large software projects. How long this takes will depend on the speed of your computer.<br />
<pre>brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
If during installation you see an error such as “Error: game-porting-toolkit: unknown or unsupported macOS version: :dunno”, your version of Homebrew doesn’t have macOS Sonoma support. Update to the latest version of Homebrew and try again.<br />
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre><br />
<br />
2. Create a new Wine prefix for your Game Porting Toolkit environment<br />
<br />
A Wine prefix contains a virtual C: drive. You will install the toolkit and your game into this virtual C: drive. Run the following command to create a new Wine prefix named my-game-prefix in your home directory.<br />
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre><br />
*A “Wine configuration” window should appear on your screen.<br />
*Change the version of Windows to Windows 10.<br />
*Choose Apply and then OK to exit winecfg.<br />
<br />
If the “Wine configuration” window does not appear, and no new icon appears in the Dock, verify that you have correctly installed the x86_64 version of Homebrew as well as the game-porting-toolkit formula.<br />
<br />
3. Install the toolkit into the Wine prefix<br />
<br />
The graphics bridge libraries need to be placed inside your Wine prefix in order to finalize your game evaluation environment. These instructions assume you have mounted the Game Porting Toolkit at /Volumes/Game Porting Toolkit-1.0.<br />
*Copy the Game Porting Toolkit library directory into Wine’s library directory.<br />
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre><br />
<br />
Launch your game<br />
<br />
Open your Wine prefix’s virtual C: drive in Finder (open ~/my-game-prefix/drive_c) and copy your game into an appropriate subdirectory.<br />
<br />
The provided bin/gameportingtoolkit* scripts can be copied onto your path to facilitate different forms of logging and launching. You can run these scripts from any shell; you don’t need to switch to the Rosetta environment first.<br />
<br />
Put the 3 scripts from the Game Porting Toolkit DMG into here:<br />
<pre>/usr/local/bin</pre><br />
You can use Cmd+Shift+G and enter the path, or you can go to root in Finder and press Cmd+Shift+. and reveal hidden folders.<br />
<br />
A. Standard launching:<br />
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.<br />
<br />
B. Launching without a HUD<br />
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Launches your game without the extended Metal Performance HUD visible.<br />
<br />
C. Launching with Wine ESYNC disabled<br />
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files\MyGame\MyGame.exe'</pre><br />
<br />
Finally, the no-esync versions of the script disable Wine's ESYNC option, a common compatibility flag. If your game experiences issues with multithreading, or you get an error message about running out of files, you can try launching your game without this Wine environment variable enabled to see if disabling esync clears the problem.<br />
<br />
Logging<br />
<br />
Logging output will appear in the Terminal window in which you launch your game as well as the system log, which can be viewed with the Console app found in Applications ▸ Utilities. Log messages from the Game Porting Toolkit are prefixed with D3DM. By default the gameportingtoolkit* scripts will filter to just the D3DM-prefixed messages.<br />
<br />
Troubleshooting<br />
<br />
My game won't run and crashes with an invalid instruction<br />
<br />
Invalid instruction crashes are often (but not always) caused when Rosetta 2 is unable to translate AVX/AVX2 instructions. You may be able to recompile a version of your game without AVX/AVX2 instructions in order to evaluate its potential on Apple Silicon with the Game Porting Toolkit when you hit this error. When porting your code natively to Apple Silicon, NEON instructions are a high-performance replacement for AVX/AVX2.<br />
<br />
<br />
My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.<br />
<br />
You may be able to rebuild a custom version of your game in your Windows development environment with anti-cheat or DRM disabled for your own evaluation purposes. When porting your code natively to Apple Silicon and macOS, contact your anti-cheat or DRM provider—most have native Apple Silicon solutions for your native build.<br />
<br />
<br />
<br />
My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.<br />
<br />
The game porting toolkit’s evaluation environment does not pre-install these runtime support packages. If your game makes use of one of these packages, consider searching for and downloading appropriate installers (.exe or .msi) and installing them to your evaluation environment. Additional runtime installers can be run on your environment by just launching the installer and following its installation instructions:<br />
<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe><br />
<br />
And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:<br />
<br />
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Desireebaldwin&diff=7483User:Desireebaldwin2023-06-05T20:07:02Z<p>John1111: Replaced content with "No Spam."</p>
<hr />
<div>No Spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=System_Shock_Remake&diff=7475System Shock Remake2023-06-01T17:19:04Z<p>John1111: </p>
<hr />
<div>{{Compatibility/macOS<br />
|crossover = Playable<br />
|crossover notes = Crossover 22 + CXPatcher, see gameplay video.<br />
|parallels = Playable<br />
|parallels notes = Demo works well. Changing setting from ULTRA to LOW brings performance from 25-30 fps to 40-45 fps. Some graphical artifacts (doors don't render correctly but work OK). <ref>{{Refdevice|user=Macrotech|date=2023-02-15|device= MacBook Pro 16 M1 Max 32GB |os=MacOS 13.2.1|method=Parallels|settings=Ultra|framerate=30fps}}</ref><br />
|windows 10 arm = <br />
|windows 10 arm notes =<br />
|linux arm =<br />
|linux arm notes =<br />
}}<br />
<br />
==Gameplay videos==<br />
{{#widget:YouTube|id=boRDd-swlHk}}<br />
<br />
{{References}}<br />
<br />
[[Category:Games]]</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Angie_west&diff=7466User:Angie west2023-05-25T17:54:30Z<p>John1111: Replaced content with "NO SPAM"</p>
<hr />
<div>NO SPAM</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Wilout&diff=7416User:Wilout2023-05-15T13:57:40Z<p>John1111: Replaced content with "NO SPAM. NO. NO. NO. NO. NO."</p>
<hr />
<div>NO SPAM. NO. NO. NO. NO. NO.</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Marian_gardner&diff=7378User:Marian gardner2023-05-01T11:18:33Z<p>John1111: Blanked the page</p>
<hr />
<div></div>John1111https://www.applegamingwiki.com/w/index.php?title=Topic:Xf4ngxnr11m5khi7&topic_revId=xh8cxu4tlw8o6knv&action=single-viewTopic:Xf4ngxnr11m5khi72023-04-30T10:53:13Z<span class="plainlinks"><a href="/wiki/User:John1111" class="mw-userlink" title="User:John1111"><bdi>John1111</bdi></a> <span class="mw-usertoollinks">(<a href="/w/index.php?title=User_talk:John1111&action=edit&redlink=1" class="new mw-usertoollinks-talk" title="User talk:John1111 (page does not exist)">talk</a> | <a href="/wiki/Special:Contributions/John1111" class="mw-usertoollinks-contribs" title="Special:Contributions/John1111">contribs</a>)</span> changed the topic title from "123Movies - Watch Movies Online 123Movies HD" to "<a rel="nofollow" class="external text" href="https://www.applegamingwiki.com/wiki/Topic:Xf4ngxnr11m5khi7">no spam</a>"</span>John1111https://www.applegamingwiki.com/w/index.php?title=User:Idapratt&diff=7373User:Idapratt2023-04-30T10:52:53Z<p>John1111: Replaced content with "no spam."</p>
<hr />
<div>no spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Mcgregor307&diff=7372User:Mcgregor3072023-04-30T10:52:29Z<p>John1111: Replaced content with "no spam."</p>
<hr />
<div>no spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Capricorn039&diff=7371User:Capricorn0392023-04-30T10:49:38Z<p>John1111: Replaced content with "no spam."</p>
<hr />
<div>no spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Elisa_bush&diff=7370User:Elisa bush2023-04-30T10:45:56Z<p>John1111: Replaced content with "no spam."</p>
<hr />
<div>no spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Zoila_klinger&diff=7369User:Zoila klinger2023-04-30T10:45:43Z<p>John1111: Replaced content with "no spam."</p>
<hr />
<div>no spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Danielle524&diff=7368User:Danielle5242023-04-30T10:45:20Z<p>John1111: Replaced content with "no spam."</p>
<hr />
<div>no spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Catherine_shisler&diff=7367User:Catherine shisler2023-04-30T10:43:10Z<p>John1111: Replaced content with "no spam."</p>
<hr />
<div>no spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Davidson039&diff=7366User:Davidson0392023-04-30T10:42:53Z<p>John1111: Replaced content with "no spam."</p>
<hr />
<div>no spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Amy_cannon&diff=7365User:Amy cannon2023-04-30T10:39:04Z<p>John1111: Replaced content with "no spam."</p>
<hr />
<div>no spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Marian_gardner&diff=7364User:Marian gardner2023-04-30T10:38:39Z<p>John1111: Replaced content with "no spam."</p>
<hr />
<div>no spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:Witinces78&diff=7363User:Witinces782023-04-30T10:38:16Z<p>John1111: Replaced content with "no spam."</p>
<hr />
<div>no spam.</div>John1111https://www.applegamingwiki.com/w/index.php?title=System_Shock_Remake&diff=7108System Shock Remake2023-02-13T12:47:52Z<p>John1111: Created page with "{{Compatibility/macOS |crossover = Unplayable |crossover notes = The game demo opens but the intro shows just a few frames and it's extremely slow (<2fps) and..."</p>
<hr />
<div>{{Compatibility/macOS<br />
|crossover = Unplayable<br />
|crossover notes = The game demo opens but the intro shows just a few frames and it's extremely slow (<2fps) and with graphical artefacts in-game. The engine uses DirectX 11. <ref>{{Refdevice|user=john1111|date=2023-02-13|device= MacBook Pro 13 M1 16GB |os=MacOS 13.1|method=Crossover|settings=Low|framerate=2fps}}</ref><br />
|parallels = unknown<br />
|parallels notes =<br />
|windows 10 arm =<br />
|windows 10 arm notes =<br />
|linux arm =<br />
|linux arm notes =<br />
}}<br />
<br />
{{References}}<br />
<br />
[[Category:Games]]</div>John1111https://www.applegamingwiki.com/w/index.php?title=User:John1111&diff=6821User:John11112022-12-28T10:03:58Z<p>John1111: Created page with "Everything is tested on an M1 Pro."</p>
<hr />
<div>Everything is tested on an M1 Pro.</div>John1111https://www.applegamingwiki.com/w/index.php?title=Dwarf_Fortress&diff=6820Dwarf Fortress2022-12-28T10:02:41Z<p>John1111: Tested, perfect</p>
<hr />
<div><br />
{{Compatibility/macOS<br />
|crossover = Perfect<br />
|crossover notes = Works perfectly, no graphical issues.<br />
|parallels = unknown<br />
|parallels notes = <br />
}}</div>John1111