AppleGamingWiki - User contributions [en]

Horizon Forbidden West

2024-09-28T16:21:36Z

Andytizer: /* Instructions */ Updated with PCGW file link

{{Infobox game
|cover = Horizon_Forbidden_West_cover.png
|developers =
{{Infobox game/row/developer|Guerrilla}}
|publishers =
{{Infobox game/row/publisher|PlayStation PC LLC}}
|engines =
{{Infobox game/row/engine|Decima}}
|release dates=
{{Infobox game/row/date|PS4, PS5|February 18, 2022}}
{{Infobox game/row/date|Windows|March 21, 2024}}
|reception =
{{Infobox game/row/reception|Metacritic|horizon-forbidden-west-complete-edition|89}}
{{Infobox game/row/reception|Opencritic|12361/horizon-forbidden-west|88}}
{{Infobox game/row/reception|IGDB|horizon-forbidden-west|86}}
|taxonomy =
{{Infobox game/row/taxonomy/monetization | | ref= One-time game purchase}}
{{Infobox game/row/taxonomy/microtransactions | | ref= }}
{{Infobox game/row/taxonomy/modes | Singleplayer}}
{{Infobox game/row/taxonomy/pacing | Real-time }}
{{Infobox game/row/taxonomy/perspectives | Third-person }}
{{Infobox game/row/taxonomy/controls | Direct control }}
{{Infobox game/row/taxonomy/genres | Action, ARPG, Open world}}
{{Infobox game/row/taxonomy/sports | }}
{{Infobox game/row/taxonomy/vehicles | Robot}}
{{Infobox game/row/taxonomy/art styles | Realistic}}
{{Infobox game/row/taxonomy/themes | Post-apocalyptic, Sci-fi}}
{{Infobox game/row/taxonomy/series | Horizon}}
|steam appid = 1151640
|gogcom id =
|gogcom id side =
|official site= https://www.playstation.com/en-us/horizon/
|hltb =
|igdb =
|strategywiki =
|mobygames =
|wikipedia =
|winehq =
|license =
|pcgamingwiki =
|codeweavers =
|asg =
}}

{{Compatibility/macOS
|native = na
|native notes =
|rosetta 2 = na
|rosetta 2 notes =
|ios-ipados app = na
|ios-ipados app notes =
|crossover = menu
|crossover notes = F16C instructions error. Update: Runs after patch
<ref>{{Refdevice
|user=loginlogin2
|date=2024-06-14
|device=MacBook M1 Pro 16" 2021 16 GB RAM
|os=macOS Sequoia
|method=Crossover 24-GPTK-2
|version=
|resolution=1728x1117
|settings=Very High
|framerate= 25-30
|controller=
|comment=
}}
</ref>
|windows 10 arm = na
|wine = na
|wine notes =
|parallels = na
|parallels notes =
|windows 10 arm = na
|windows 10 arm notes =
|linux arm = na
|linux arm notes =
}}

==Gameplay videos==

===Instructions===

{{Fixbox|description=F16C instructions fix|fix=

<ol>
Patch for 1.5.80 game version - [https://community.pcgamingwiki.com/files/file/3114-horizon-forbidden-west-f16c-instructions-fix/ HorizonForbiddenWest_1.5.80_F16Patch]
</ol>
}}

{{References}}

[[Category:Games]]

Ghost of Tsushima Director's Cut

2024-09-28T16:21:02Z

Andytizer: /* F16C instructions fix */ updated with PCGW file link

{{Infobox game
|cover = Ghost_of_Tsushima_Director's_Cut_cover.jpg
|developers =
{{Infobox game/row/developer|Sucker Punch Productions}}
{{Infobox game/row/porter|Nixxes Software|Windows}}
|publishers =
{{Infobox game/row/publisher|PlayStation PC}}
|engines =
|release dates=
{{Infobox game/row/date|PlayStation|August 20, 2021}}
{{Infobox game/row/date|PC|May 16, 2024}}
|reception =
{{Infobox game/row/reception|Metacritic|ghost-of-tsushima-directors-cut|88}}
{{Infobox game/row/reception|OpenCritic|9592/ghost-of-tsushima|84}}
{{Infobox game/row/reception|IGDB|ghost-of-tsushima-directors-cut|92}}
|taxonomy =
{{Infobox game/row/taxonomy/series | }}
|steam appid = 2215430
|steam appid side =
|gogcom id =
|gogcom id side =
|official site= https://www.playstation.com/en-us/games/ghost-of-tsushima/pc
|hltb = 51225
|igdb = ghost-of-tsushima-directors-cut
|mobygames = 169624
|strategywiki = Ghost of Tsushima
|wikipedia = Ghost of Tsushima
|winehq =
|license = commercial
|pcgamingwiki = Ghost_of_Tsushima_Director's_Cut
|codeweavers = ghost-of-tsushima-directors-cut
|asg =
}}

'''General information'''
{{mm}} [https://steamcommunity.com/app/2215430/discussions Steam Community Discussions]
{{mm}} [https://www.ign.com/wikis/ghost-of-tsushima Ghost of Tsushima Guide]
{{mm}} [https://www.reddit.com/r/GhostofTsushima Ghost of Tsushima Subreddit]

{{Compatibility/macOS
|native = na
|native notes =
|rosetta 2 = perfect
|rosetta 2 notes = <ref name=Lynkos></ref>
|ios-ipados app = na
|ios-ipados app notes =
|crossover = Playable
|crossover notes = F16C instructions error. Update: Runs well after patch, there are only problems with faces in cutscenes (it is translation of Rosetta problem, because Windows users don't have this problem, tested personally) and sometimes the armor moves incorrectly.
<ref>{{Refdevice
|user=VladimirProg
|date=2024-09-25
|device=MacBook M1 Pro 16" 2021 16 GB RAM
|os=macOS Sequoia
|method=Crossover 24-GPTK-2 b3
|version=
|resolution=1920x1080
|settings=Low
|framerate=34 with FSR
|controller=
|comment=
}}
</ref>
|wine = perfect
|wine notes = Plays perfectly after applying F16C Patch (see [[#F16C_instructions_fix]]).<ref name=Lynkos>{{Refdevice|user=Lynkos|date=2024-09-26|device=MacBook Pro M3 Max 14" 64 GB RAM|os=macOS 15.0|method=[[Game Porting Toolkit]] 2 Beta 3|version=|store=Steam|resolution=3024x1964|settings=Very High|framerate=~50 FPS|controller=Xbox One Controller|url=|comment=Environment variables include <code>D3DM_SUPPORT_DXR=1</code> and <code>ROSETTA_ADVERTISE_AVX=1</code>}}</ref>
|parallels = unknown
|parallels notes =
|windows 10 arm = na
|windows 10 arm notes =
|linux arm = na
|linux arm notes =
}}

==Availability==
{{Availability}}

==Gameplay videos==
{{#widget:YouTube|id=1Aq4DPgvHbA}}

==Issues fixed==
===F16C instructions fix===
''Error when launching the game [via Steam] that says:''
<blockquote><i>This game requires a CPU that supports F16C instructions.</i></blockquote>
{{Fixbox|description=Use Patch v1053.7.809.1937|ref=<ref>{{Refurl|url=https://www.reddit.com/r/macgaming/comments/1fp9hb0/fully_playable_patch_for_the_game_ghost_of|title=Reddit: "Fully playable patch for the game Ghost Of Tsushima"|date=2024-09-26}}</ref>|fix=
# Download [https://community.pcgamingwiki.com/files/file/3115-ghost-of-tsushima-f16c-instructions-fix/ patch for 1053.7.809.1937 game version] to the directory containing <code>GhostOfTsushima.exe</code><br>e.g. <code>C:\Program Files (x86)\Steam\steamapps\common\Ghost of Tsushima DIRECTOR'S CUT</code>
# Rename the original <code>GhostOfTsushima.exe</code> file to something else<br>e.g. <code>GhostOfTsushima_orig.exe</code>
# Rename the recently downloaded patch to <code>GhostOfTsushima.exe</code>
This patch became available thanks to the support of Andrew Tsai [https://www.youtube.com/@Andytizer YouTube]
}}

{{References}}

[[Category:Games]]

Sideloading App Store games onto iPhone and iPad

2024-09-10T08:49:53Z

Andytizer: Blank

The Witcher 3

2023-06-14T21:02:43Z

Andytizer:

{{Infobox game
|cover = The Witcher 3 Wild Hunt - cover.jpg
|developers =
{{Infobox game/row/developer|CD Projekt Red}}
|publishers =
{{Infobox game/row/publisher|CD Projekt}}
|engines =
{{Infobox game/row/engine|REDengine|name=REDengine 3}}
|release dates=
{{Infobox game/row/date|Windows|May 19, 2015}}
|reception =
{{Infobox game/row/reception|Metacritic|the-witcher-3-wild-hunt|93}}
{{Infobox game/row/reception|OpenCritic|463/the-witcher-3-wild-hunt|92}}
{{Infobox game/row/reception|IGDB|the-witcher-3-wild-hunt|92}}
|taxonomy =
{{Infobox game/row/taxonomy/monetization|expansion pack}}
{{Infobox game/row/taxonomy/series|The Witcher (series)}}
|steam appid = 292030
|steam appid side = 355880, 499450, 378648
|gogcom id = 1495134320
|gogcom id side = 1207664663,1207664643,1427195509,1441620909,1441355562,1427206931,1636895344,1640424747,1430743168
|official site= http://thewitcher.com/witcher3/
|hltb = 10270
|strategywiki =
|mobygames = witcher-3-wild-hunt
|wikipedia = The Witcher 3: Wild Hunt
|winehq = 16884
|license = commercial
|pcgamingwiki = The_Witcher_3:_Wild_Hunt
|codeweavers = the-witcher-3-wild-hunt
}}

'''General information'''
{{mm}} [https://forums.cdprojektred.com/index.php?forums/the-witcher-series.22/ Official Forums]
{{mm}} [https://www.nexusmods.com/witcher3 The Witcher 3 Nexus Mods]
{{GOG.com links|1207664663|the_witcher_3_wild_hunt}}
{{mm}} [https://steamcommunity.com/app/292030/discussions/ Steam Community Discussions]

{{Compatibility/macOS
|native = na
|native notes =
|rosetta 2 = na
|rosetta 2 notes =
|ios-ipados app = na
|ios-ipados app notes =
|crossover = Playable
|crossover notes = 1 or 2 type of enemies are invisible but they are very easy to kill.<ref>{{Refurl|url=https://github.com/doitsujin/dxvk/issues/582|title=Render issue with The Witcher 3 Wild Hunt · Issue #582 · doitsujin/dxvk · GitHub|date=2022-07-16|snippet=err: D3D11Device::CreateGeometryShaderWithStreamOutput: Not implemented. Sirens are one of the enemies in Witcher 3 that rely on Stream Output which DXVK currently can't implement.}}</ref>
|wine = Playable
|wine notes = A few enemies are invisible and a few have bugged textures. Most notably the Hounds of the Wild Hunt are invisible in the first quest you meet them, the rotfiends are invisible in Velen and the sirens are invisible in Skellige. Skellige also has a lot of places in the coastline where the game becomes very glitchy.<ref>{{Refdevice|user=Exerra|date=2022-12-28|device=Mac Mini M1 2020 8GB RAM|os=macOS 12.2|method=PortingKit|version=1.32|store=GOG|resolution=1920x1080|settings=Medium|framerate=|controller=Xbox Series S|url=|title=Test|comment=NVIDIA Hairworks must be turned off, game crashes if the graphics quality is higher than the Medium preset and every postprocessing item can be turned on and still have the game be smooth (except motion blur). When using PortingKit the game does not exit when the button has been pressed in-game, it only closes the window. To exit fully, either go to PortingKit and kill all processes using the PortingKit GUI, or go to Activity Monitor and kill all the wine processes. If the game does not launch (wine process starts, then quits automatically) restart your computer and try again.}}</ref>
|parallels = Perfect
|parallels notes =
|windows 10 arm = na
|windows 10 arm notes =
|linux arm = na
|linux arm notes =
}}

==Availability==
{{Availability}}

==Gameplay videos==
{{#widget:YouTube|id=G2f-uQ4NzSw}} {{#widget:YouTube|id=xpp7Vv8o8PQ}}

==Notes==
DirectX 12 mode can be activated using the launch command: <code>--launcher-skip</code>
{{References}}

Game Porting Toolkit

2023-06-14T19:14:34Z

Andytizer: /* My game won’t run because it requires Mono, .NET, or the MSVCRT runtime */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

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 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. This is a 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
*If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/$USER/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in Terminal (e.g. SHIFT+ CMD + G -> ~/Library/Application Support/heroic/tools/wine/Wine-crossover-wine-22.1.0).
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/$USER/my-game-prefix</code>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/$USER/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/$USER/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors, or alternatively stop mirroring the screen.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== Nothing loads after a crash ===
Try closing all Wine threads:
<pre>killall -9 wineserver && killall -9 wine64-preloader</pre>

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
For the example of VC Redistributable, download the x64 version here: https://aka.ms/vs/17/release/vc_redist.x64.exe

<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 vc_redist.x64.exe
</pre>

Generic commands:

<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

===AVX===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

AVX requirement can be bypassed in some games, e.g Dying Light 2.

{{Fixbox|description=AVX Fix for Dying Light 2|ref=<ref>Reference</ref>|fix=
There is a workaround in Dying Light 2 which is to simply remove/rename the "runtime_dx11.dll"

#Right click on DL2 on steam
#Manage
#Local files
#Navigate to "ph\work\bin\x64"
#Rename "runtime_dx11.dll" to "runtime_dx11.dll.bak"
#Start the game

If for some reason you need the "runtime_dx11.dll" back, just remove the ".bak" or verify game files integrity in steam
}}

== Game compatibility list ==
{{ii}} '''Total number of games: '''{{#cargo_query:tables=Compatibility_macOS|fields=COUNT(*)|group by=_pageNamespace|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'}}
{{mm}} ''This list was last refreshed on '''{{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}'''. [{{fullurl:{{FULLPAGENAMEE}}|action=purge}} Purge] the page to refresh it.''
{{#cargo_query:
tables=Compatibility_macOS
|fields=Compatibility_macOS._pageName, Compatibility_macOS.wine
|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs'
|limit=500
|offset=0
|format=template
|intro={{ListOfGames/intro}}
|template=ListOfGames/row
|outro=</table></div>
}}
{{#cargo_query:
tables=Compatibility_macOS
|fields=Compatibility_macOS._pageName, Compatibility_macOS.wine
|where= Compatibility_macOS.wine='unplayable' OR Compatibility_macOS.wine='menu'
|limit=500
|offset=0
|format=template
|intro={{ListOfGames/intro}}
|template=ListOfGames/row
|outro=</table></div>
}}

Old list - this should be made into individual wiki articles in order to populate the automated list above, which tracks all game compatibility methods using Wine.

Working games:
* [[AnimA: Reign of Darkness]]
* [[Astroneer]]
* [[Assassins Creed 3 Remastered]]
* [[Atomic Heart]]
* [[ARK: Survival Evolved]] - (~50 fps on low settings)
* [[Batman: Arkham Knight]] - launches with steam
* [[Blood: Fresh Supply]]
* [[Bloodstained: Ritual of the Night]]
* [[Brick Rigs]]
* [[Genshin Impact]] 3.7 (m2max with 4k 60fps stable)
* [[Chasm: The Rift]] (It works but you can't change any video options as it will crash. You have to manually edit the config file.)
* [[Control]] (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* [[Crysis Remastered]]
* [[Cultic]]
* [[Cuphead]]
* [[Cyberpunk 2077]]
* [[Dead Space Remake]]
* [[Deep Rock Galactic]]
* [[Deceive Inc.]] - works well if launched without EAC
* [[Derail Valley]] (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* [[Diablo IV]] [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* [[Dread Templar]]
* [[Duke Nukem 3D HRP (eduke32)]]
* [[Dying Light 2]] (needs AVX fix above)
* [[Dyson Sphere Program]] (some objects and main character weren't visible before)
* [[Elden Ring]]
* [[Final Fantasy VII Remake Intergrade]] (~50 FPS on High settings at 1080p with M1 Pro)
* [[Five Nights At Freddy's Security Breach]]
* [[Friends vs. Friends]]
* [[Gloomwood]]
* [[God of War]] (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* [[Going Medieval]]
* [[Guilty Gear Strive]]
* [[Grand Theft Auto V]]
* [[Green Hell]]
* [[Halo 3]] (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* [[Halo Reach]] (MCC)
* [[HI-Fi RUSH]]
* [[Hogwarts Legacy]] - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* [[Hatsune Miku: Project DIVA Mega Mix+]] - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* [[Infinity Racer XD]]
* [[Kena: Bridge of Spirits]]
* [[Metal Gear Solid V: The Phantom Pain]]
* [[Outer Wilds]] (through steam)
* [[Overwatch 2]]
* [[QUBE 2]]
* [[People Playground]]
* [[PowerSlave Exhumed]]
* [[Prodeus]]
* [[Project Warlock]]
* [[Ready or Not]]
* [[Risk of Rain 2]] (does not require `-disable-gpu-skinning` like Crossover 22)
* [[Scarlet Nexus]]
* [[Sonic GT]]
* [[Sonic illusions]]
* [[Sonic Omens]]
* [[Sonic Project '06]]
* [[Spider-Man (2018)]]
* [[Spider-Man Miles Morales]] - ''requires Windows ver fix''
* [[SpongeBob SquarePants: The Cosmic Shake]]
* [[StarCraft: Remastered]] - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* [[Tetris Effect: Connected]] - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* [[V Rising]]
* [[Warframe]] - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* [[WRATH: Aeon of Ruin]]
* [[Vampyr]] - 25-30fps on Ultra settings, tested on M1 MBA (!DX11 game!)
* [[Tell Me Why]] - On maxed out settings, runs around 35-45fps on base M1 MBA (!DX11 game!)

Not working well:
* [[Horizon Zero Dawn]] - slowdown issues
* [[Genshin Impact]] - Launches, but stuck when calling menu using esc
* [[CarX Drift Racing Online]] - Game freezes after launch.

Not working yet:
* [[Apex Legends]] (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** [[Need for Speed Heat]]
** [[Need for Speed Unbound]]
** [[Tom Clancy's The Division 2]]
* [[Among Us]]
* [[Assassins Creed Odyssey]]
* [[Assassins Creed Valhalla]]
* [[BeamNG.Drive]] - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* [[Company of Heroes 3]]
* [[Death Stranding]]
* [[Doom (2016)]] - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* [[F1 20]] - Crash on launch (DX11 version running through GPTK is slower compared to Crossover 21)
* [[F1 21]] - Crash on launch
* [[F1 22]] - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* [[Grand Theft Auto IV]] - Rockstar games launcher crashes on launch, cracked version should work fine
* [[Halo Infinite]] - Crash on launch
* [[Hitman 3]] - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* [[Microsoft Flight Simulator 2020]] (Steam) - Crash on launch
* [[Monster Hunter Rise]] - DX12 Game, it launches but window goes dark after compiling shaders.
* [[Monster Hunter World]] - Black Screen on Launch
* [[New World]] - Game loaded but couldn't connect to server due to Easy Anti Cheat
* [[Payday 2]]
* [[Red Dead Redemption 2]]
* [[Rogue Company]] - anti-cheat conflict.
* [[s&box]] - crashes right on launch. (it should be DX11)
* [[Sea of Thieves]] - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* [[Saints Row IV: Re-Elected]] - Launches, but crashes when trying to load into game
* [[Slime Rancher 2]] - Launches, but can't into game from main menu
* [[Sonic Frontiers]] - AVX Requirement
* [[SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated]] - Crashes when loading
* [[Teardown]] - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* [[The Elder Scrolls V: Skyrim Special Edition]] - the launcher gives a "The program skyrimselauncher.exe has encountered a serious problem" message, not allowing us to get into the game
* [[theHunter: Call of the Wild]] - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* [[The Joy of Creation: Story Mode]] - Crash on launch
* All DX9 games (as this toolkit supports DX11 & DX12 only)
** [[30XX]] - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** [[Battleblock Theater]] - Black screen -> crash on launch
** [[Black Mesa]] - Starts to load to main menu at first but then crashes
** [[Castle Crashers]] - Black screen -> crash on launch
** [[Killing Floor 1]] - Crash on launch
** [[Left 4 Dead 2]] - Black screen -> crash on launch
** [[Lego Batman: The Videogame]] - Black screen -> crash on launch
** [[Lego Batman 2: DC Super Heros]] - Black screen -> crash on launch
** [[Lego Batman 3: Beyond Gotham]] - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** [[Mega Man Zero/ZX Legacy Collection]] - "Failed to create d3d9 device" -> crash on launch
** [[Sonic Mania]] - Crash on launch
** [[Space Engineers]] - Gets to first loading screen then crashes
** [[StarCraft II]] -> "Failed to initialize DirectX" error
** [[Star Wars: The Old Republic]]
** [[Battlefield 2]] - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}
[[Category:Lists]]

Game Porting Toolkit

2023-06-12T17:18:28Z

Andytizer: /* Steam crashes straight after opening */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

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 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. This is a 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
*If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/$USER/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in Terminal (e.g. SHIFT+ CMD + G -> ~/Library/Application Support/heroic/tools/wine/Wine-crossover-wine-22.1.0).
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/$USER/my-game-prefix</code>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/$USER/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/$USER/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors, or alternatively stop mirroring the screen.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== Nothing loads after a crash ===
Try closing all Wine threads:
<pre>killall -9 wineserver && killall -9 wine64-preloader</pre>

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

===AVX===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

AVX requirement can be bypassed in some games, e.g Dying Light 2.

{{Fixbox|description=AVX Fix for Dying Light 2|ref=<ref>Reference</ref>|fix=
There is a workaround in Dying Light 2 which is to simply remove the "runtime_dx11.dll"

#Right click on DL2 on steam
#Manage
#Local files
#Navigate to "ph\work\bin\x64"
#Delete "runtime_dx11.dll"
#Start the game

If for some reason you need the "runtime_dx11.dll" back, just verify integrity of game files in Steam
}}

== Game compatibility list ==
{{ii}} '''Total number of games: '''{{#cargo_query:tables=Compatibility_macOS|fields=COUNT(*)|group by=_pageNamespace|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'}}
{{mm}} ''This list was last refreshed on '''{{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}'''. [{{fullurl:{{FULLPAGENAMEE}}|action=purge}} Purge] the page to refresh it.''
{{#cargo_query:
tables=Compatibility_macOS
|fields=Compatibility_macOS._pageName, Compatibility_macOS.wine
|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'
|limit=500
|offset=0
|format=template
|intro={{ListOfGames/intro}}
|template=ListOfGames/row
|outro=</table></div>
}}

Old list - this should be made into individual wiki articles in order to populate the automated list above, which tracks all game compatibility methods using Wine.

Working games:
* [[AnimA: Reign of Darkness]]
* [[Astroneer]]
* [[Assassins Creed 3 Remastered]]
* [[Batman: Arkham Knight]] - launches with steam
* [[Bloodstained: Ritual of the Night]]
* [[Brick Rigs]]
* [[Genshin Impact]] 3.7 (m2max with 4k 60fps stable)
* [[Control]] (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* [[Crysis Remastered]]
* [[Cultic]]
* [[Cuphead]]
* [[Cyberpunk 2077]]
* [[Deep Rock Galactic]]
* [[Deceive Inc.]] - works well if launched without EAC
* [[Derail Valley]] (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* [[Diablo IV]] [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* [[Dread Templar]]
* [[Dying Light 2]] (needs AVX fix above)
* [[Dyson Sphere Program]] (some objects and main character weren't visible before)
* [[Elden Ring]]
* [[Final Fantasy VII Remake Intergrade]] (~50 FPS on High settings at 1080p with M1 Pro)
* [[Five Nights At Freddy's Security Breach]]
* [[Friends vs. Friends]]
* [[Gloomwood]]
* [[God of War]] (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* [[Going Medieval]]
* [[Guilty Gear Strive]]
* [[Grand Theft Auto V]]
* [[Green Hell]]
* [[Halo 3]] (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* [[Halo Reach]] (MCC)
* [[HI-Fi RUSH]]
* [[Hogwarts Legacy]] - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* [[Hatsune Miku: Project DIVA Mega Mix+]] - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* [[Infinity Racer XD]]
* [[Kena: Bridge of Spirits]]
* [[Metal Gear Solid V: The Phantom Pain]]
* [[Outer Wilds]] (through steam)
* [[Overwatch 2]]
* [[QUBE 2]]
* [[People Playground]]
* [[Prodeus]]
* [[Ready or Not]]
* [[Risk of Rain 2]] (does not require `-disable-gpu-skinning` like Crossover 22)
* [[Scarlet Nexus]]
* [[Sonic GT]]
* [[Sonic illusions]]
* [[Sonic Omens]]
* [[Sonic Project '06]]
* [[Spider-Man (2018)]]
* [[Spider-Man Miles Morales]] - ''requires Windows ver fix''
* [[SpongeBob SquarePants: The Cosmic Shake]]
* [[StarCraft: Remastered]] - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* [[Tetris Effect: Connected]] - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* [[V Rising]]
* [[Warframe]] - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* [[WRATH: Aeon of Ruin]]

Not working well:
* [[Horizon Zero Dawn]] - slowdown issues
* [[Genshin Impact]] - Launches, but stuck when calling menu using esc
* [[CarX Drift Racing Online]] - Game freezes after launch.

Not working yet:
* [[Apex Legends]] (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** [[Need for Speed Heat]]
** [[Need for Speed Unbound]]
** [[Tom Clancy's The Division 2]]
* [[Among Us]]
* [[Assassins Creed Odyssey]]
* [[Assassins Creed Valhalla]]
* [[BeamNG.Drive]] - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* [[Company of Heroes 3]]
* [[Death Stranding]]
* [[Doom (2016)]] - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* [[F1 20]] - Crash on launch (DX11 version running through GPTK is slower compared to Crossover 21)
* [[F1 21]] - Crash on launch
* [[F1 22]] - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* [[Grand Theft Auto IV]] - Rockstar games launcher crashes on launch, cracked version should work fine
* [[Halo Infinite]] - Crash on launch
* [[Hitman 3]] - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* [[Microsoft Flight Simulator 2020]] (Steam) - Crash on launch
* [[Monster Hunter Rise]] - DX12 Game, it launches but window goes dark after compiling shaders.
* [[Monster Hunter World]] - Black Screen on Launch
* [[New World]] - Game loaded but couldn't connect to server due to Easy Anti Cheat
* [[Payday 2]]
* [[Red Dead Redemption 2]]
* [[Rogue Company]] - anti-cheat conflict.
* [[s&box]] - crashes right on launch. (it should be DX11)
* [[Sea of Thieves]] - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* [[Saints Row IV: Re-Elected]] - Launches, but crashes when trying to load into game
* [[Slime Rancher 2]] - Launches, but can't into game from main menu
* [[Sonic Frontiers]] - AVX Requirement
* [[SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated]] - Crashes when loading
* [[Teardown]] - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* [[The Elder Scrolls V: Skyrim Special Edition]] - the launcher gives a "The program skyrimselauncher.exe has encountered a serious problem" message, not allowing us to get into the game
* [[theHunter: Call of the Wild]] - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* [[The Joy of Creation: Story Mode]] - Crash on launch
* All DX9 games (as this toolkit only supports DX11 & DX12)
** [[30XX]] - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** [[Battleblock Theater]] - Black screen -> crash on launch
** [[Black Mesa]] - Starts to load to main menu at first but then crashes
** [[Castle Crashers]] - Black screen -> crash on launch
** [[Killing Floor 1]] - Crash on launch
** [[Left 4 Dead 2]] - Black screen -> crash on launch
** [[Lego Batman: The Videogame]] - Black screen -> crash on launch
** [[Lego Batman 2: DC Super Heros]] - Black screen -> crash on launch
** [[Lego Batman 3: Beyond Gotham]] - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** [[Mega Man Zero/ZX Legacy Collection]] - "Failed to create d3d9 device" -> crash on launch
** [[Sonic Mania]] - Crash on launch
** [[StarCraft II]] -> "Failed to initialize DirectX" error
** [[Star Wars: The Old Republic]]
** [[Battlefield 2]] - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}
[[Category:Lists]]

Topic:Xjuvoa571ms7a4y4

2023-06-12T16:24:14Z

Andytizer (talk | contribs) commented on "Max Payne 3" (It's because it's 32-bit.)

Final Fantasy VII Remake Intergrade

2023-06-12T12:29:09Z

Andytizer:

{{Compatibility/macOS
|native = na
|native notes =
|rosetta 2 = na
|rosetta 2 notes =
|ios-ipados app = na
|ios-ipados app notes =
|crossover = perfect
|crossover notes = Playable.<ref>{{Refurl|url=https://applesilicongames.com/games/7Qfpb3wd8Rwoc1hxybT7qj/final-fantasy-vii|title=Final Fantasy VII on Apple Silicon Games|date=2021-04-12|snippet=}}</ref>
|wine = perfect
|wine notes = Steam version does not launch, only the Epic version works.
|parallels = perfect
|parallels notes = Playable.<ref>{{Refdevice|user=BeelzeBu|date=2021-04-15|device=MacBook Air M1 2020 8 GB RAM|os=macOS Big Sur Version 11.3 Beta (20E5231a) |method=CrossOver nightly 2120210414|version=|store=Steam|resolution=1680x1050|settings=High graphics|framerate=Approximately 15-25 FPS with rare frame drops, it does only have those frame rates|controller=|url=|title=|comment=}}</ref>
|windows 10 arm = na
|windows 10 arm notes =
|linux arm = na
|linux arm notes =
}}

{{References}}

[[Category:Games]]

Final Fantasy VII

2023-06-11T19:35:29Z

Andytizer: Andytizer moved page Final Fantasy VII to Final Fantasy VII Remake Intergrade

#REDIRECT [[Final Fantasy VII Remake Intergrade]]

Final Fantasy VII Remake Intergrade

2023-06-11T19:35:29Z

Andytizer: Andytizer moved page Final Fantasy VII to Final Fantasy VII Remake Intergrade

{{Compatibility/macOS
|native = na
|native notes =
|rosetta 2 = na
|rosetta 2 notes =
|ios-ipados app = na
|ios-ipados app notes =
|crossover = perfect
|crossover notes = Playable.<ref>{{Refurl|url=https://applesilicongames.com/games/7Qfpb3wd8Rwoc1hxybT7qj/final-fantasy-vii|title=Final Fantasy VII on Apple Silicon Games|date=2021-04-12|snippet=}}</ref>
|wine = unknown
|wine notes =
|parallels = perfect
|parallels notes = Playable.<ref>{{Refdevice|user=BeelzeBu|date=2021-04-15|device=MacBook Air M1 2020 8 GB RAM|os=macOS Big Sur Version 11.3 Beta (20E5231a) |method=CrossOver nightly 2120210414|version=|store=Steam|resolution=1680x1050|settings=High graphics|framerate=Approximately 15-25 FPS with rare frame drops, it does only have those frame rates|controller=|url=|title=|comment=}}</ref>
|windows 10 arm = na
|windows 10 arm notes =
|linux arm = na
|linux arm notes =
}}

{{References}}

[[Category:Games]]

Game Porting Toolkit

2023-06-11T14:55:02Z

Andytizer: /* Epic and GOG.com support with the Heroic Games Launcher */ Removed reference to OpenInTerminal

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

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 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
*If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/$USER/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in Terminal (e.g. SHIFT+ CMD + G -> ~/Library/Application Support/heroic/tools/wine/Wine-crossover-wine-22.1.0).
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/$USER/my-game-prefix</code>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/$USER/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/$USER/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== Nothing loads after a crash ===
Try closing all Wine threads:
<pre>killall -9 wineserver && killall -9 wine64-preloader</pre>

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

===AVX===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

AVX requirement can be bypassed in some games, e.g Dying Light 2.

{{Fixbox|description=AVX Fix for Dying Light 2|ref=<ref>Reference</ref>|fix=
There is a workaround in Dying Light 2 which is to simply remove the "runtime_dx11.dll"

#Right click on DL2 on steam
#Manage
#Local files
#Navigate to "ph\work\bin\x64"
#Delete "runtime_dx11.dll"
#Start the game

If for some reason you need the "runtime_dx11.dll" back, just verify integrity of game files in Steam
}}

== Game compatibility list ==
{{ii}} '''Total number of games: '''{{#cargo_query:tables=Compatibility_macOS|fields=COUNT(*)|group by=_pageNamespace|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'}}
{{mm}} ''This list was last refreshed on '''{{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}'''. [{{fullurl:{{FULLPAGENAMEE}}|action=purge}} Purge] the page to refresh it.''
{{#cargo_query:
tables=Compatibility_macOS
|fields=Compatibility_macOS._pageName, Compatibility_macOS.wine
|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'
|limit=500
|offset=0
|format=template
|intro={{ListOfGames/intro}}
|template=ListOfGames/row
|outro=</table></div>
}}

Old list - this should be made into individual wiki articles in order to populate the automated list above, which tracks all game compatibility methods using Wine.

Working games:
* [[AnimA: Reign of Darkness]]
* [[Astroneer]]
* [[Assassins Creed 3 Remastered]]
* [[Batman: Arkham Knight]] - launches with steam
* [[Bloodstained: Ritual of the Night]]
* [[Brick Rigs]]
* [[Genshin Impact]] 3.7 (m2max with 4k 60fps stable)
* [[Control]] (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* [[Crysis Remastered]]
* [[Cultic]]
* [[Cuphead]]
* [[Cyberpunk 2077]]
* [[Deep Rock Galactic]]
* [[Deceive Inc.]] - works well if launched without EAC
* [[Derail Valley]] (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* [[Diablo IV]] [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* [[Dread Templar]]
* [[Dying Light 2]] (needs AVX fix above)
* [[Dyson Sphere Program]] (some objects and main character weren't visible before)
* [[Elden Ring]]
* [[Final Fantasy VII Remake Intergrade]] (~50 FPS on High settings at 1080p with M1 Pro)
* [[Five Nights At Freddy's Security Breach]]
* [[Friends vs. Friends]]
* [[Gloomwood]]
* [[God of War]] (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* [[Going Medieval]]
* [[Guilty Gear Strive]]
* [[Grand Theft Auto V]]
* [[Green Hell]]
* [[Halo 3]] (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* [[Halo Reach]] (MCC)
* [[HI-Fi RUSH]]
* [[Hogwarts Legacy]] - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* [[Hatsune Miku: Project DIVA Mega Mix+]] - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* [[Infinity Racer XD]]
* [[Kena: Bridge of Spirits]]
* [[Metal Gear Solid V: The Phantom Pain]]
* [[Overwatch 2]]
* [[QUBE 2]]
* [[People Playground]]
* [[Prodeus]]
* [[Ready or Not]]
* [[Risk of Rain 2]] (does not require `-disable-gpu-skinning` like Crossover 22)
* [[Scarlet Nexus]]
* [[Sonic GT]]
* [[Sonic illusions]]
* [[Sonic Omens]]
* [[Sonic Project '06]]
* [[Spider-Man (2018)]]
* [[Spider-Man Miles Morales]] - ''requires Windows ver fix''
* [[SpongeBob SquarePants: The Cosmic Shake]]
* [[StarCraft: Remastered]] - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* [[Tetris Effect: Connected]] - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* [[V Rising]]
* [[Warframe]] - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* [[WRATH: Aeon of Ruin]]

Not working well:
* [[Horizon Zero Dawn]] - slowdown issues
* [[Genshin Impact]] - Launches, but stuck when calling menu using esc

Not working yet:
* [[Apex Legends]] (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** [[Need for Speed Heat]]
** [[Need for Speed Unbound]]
** [[Tom Clancy's The Division 2]]
* [[Among Us]]
* [[Assassins Creed Odyssey]]
* [[Assassins Creed Valhalla]]
* [[BeamNG.Drive]] - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* [[Company of Heroes 3]]
* [[Death Stranding]]
* [[Doom (2016)]] - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* [[F1 20]] - Crash on launch (DX11 version running through GPTK is slower compared to Crossover 21)
* [[F1 21]] - Crash on launch
* [[F1 22]] - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* [[Grand Theft Auto IV]] - Rockstar games launcher crashes on launch, cracked version should work fine
* [[Halo Infinite]] - Crash on launch
* [[Hitman 3]] - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* [[Microsoft Flight Simulator 2020]] (Steam) - Crash on launch
* [[Monster Hunter Rise]] - DX12 Game, it launches but window goes dark after compiling shaders.
* [[Monster Hunter World]] - Black Screen on Launch
* [[New World]] - Game loaded but couldn't connect to server due to Easy Anti Cheat
* [[Payday 2]]
* [[Red Dead Redemption 2]]
* [[Rogue Company]] - anti-cheat conflict.
* [[s&box]] - crashes right on launch. (it should be DX11)
* [[Sea of Thieves]] - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* [[Saints Row IV: Re-Elected]] - Launches, but crashes when trying to load into game
* [[Slime Rancher 2]] - Launches, but can't into game from main menu
* [[Sonic Frontiers]] - AVX Requirement
* [[SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated]] - Crashes when loading
* [[Teardown]] - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* [[The Elder Scrolls V: Skyrim Special Edition]] - the launcher gives a "The program teardown.exe has encountered a serious problem" message, not allowing us to get into the game
* [[theHunter: Call of the Wild]] - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* [[The Joy of Creation: Story Mode]] - Crash on launch
* All DX9 games (duh, this is dx 11 & 12 only)
** [[30XX]] - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** [[Battleblock Theater]] - Black screen -> crash on launch
** [[Black Mesa]] - Starts to load to main menu at first but then crashes
** [[Castle Crashers]] - Black screen -> crash on launch
** [[Killing Floor 1]] - Crash on launch
** [[Left 4 Dead 2]] - Black screen -> crash on launch
** [[Lego Batman: The Videogame]] - Black screen -> crash on launch
** [[Lego Batman 2: DC Super Heros]] - Black screen -> crash on launch
** [[Lego Batman 3: Beyond Gotham]] - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** [[Mega Man Zero/ZX Legacy Collection]] - "Failed to create d3d9 device" -> crash on launch
** [[Sonic Mania]] - Crash on launch
** [[StarCraft II]] -> "Failed to initialize DirectX" error
** [[Star Wars: The Old Republic]]
** [[Battlefield 2]] - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}
[[Category:Lists]]

Game Porting Toolkit

2023-06-11T14:41:59Z

Andytizer: We are now referring to this as GTPK

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

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 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
*If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/$USER/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/$USER/my-game-prefix</code>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/$USER/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/$USER/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== Nothing loads after a crash ===
Try closing all Wine threads:
<pre>killall -9 wineserver && killall -9 wine64-preloader</pre>

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

===AVX===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

AVX requirement can be bypassed in some games, e.g Dying Light 2.

{{Fixbox|description=AVX Fix for Dying Light 2|ref=<ref>Reference</ref>|fix=
There is a workaround in Dying Light 2 which is to simply remove the "runtime_dx11.dll"

#Right click on DL2 on steam
#Manage
#Local files
#Navigate to "ph\work\bin\x64"
#Delete "runtime_dx11.dll"
#Start the game

If for some reason you need the "runtime_dx11.dll" back, just verify integrity of game files in Steam
}}

== Game compatibility list ==
{{ii}} '''Total number of games: '''{{#cargo_query:tables=Compatibility_macOS|fields=COUNT(*)|group by=_pageNamespace|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'}}
{{mm}} ''This list was last refreshed on '''{{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}'''. [{{fullurl:{{FULLPAGENAMEE}}|action=purge}} Purge] the page to refresh it.''
{{#cargo_query:
tables=Compatibility_macOS
|fields=Compatibility_macOS._pageName, Compatibility_macOS.wine
|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'
|limit=500
|offset=0
|format=template
|intro={{ListOfGames/intro}}
|template=ListOfGames/row
|outro=</table></div>
}}

Old list - this should be made into individual wiki articles in order to populate the automated list above, which tracks all game compatibility methods using Wine.

Working games:
* [[AnimA: Reign of Darkness]]
* [[Astroneer]]
* [[Assassins Creed 3 Remastered]]
* [[Batman: Arkham Knight]] - launches with steam
* [[Bloodstained: Ritual of the Night]]
* [[Brick Rigs]]
* [[Genshin Impact]] 3.7 (m2max with 4k 60fps stable)
* [[Control]] (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* [[Crysis Remastered]]
* [[Cultic]]
* [[Cuphead]]
* [[Cyberpunk 2077]]
* [[Deep Rock Galactic]]
* [[Deceive Inc.]] - works well if launched without EAC
* [[Derail Valley]] (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* [[Diablo IV]] [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* [[Dread Templar]]
* [[Dying Light 2]] (needs AVX fix above)
* [[Dyson Sphere Program]] (some objects and main character weren't visible before)
* [[Elden Ring]]
* [[Final Fantasy VII Remake Intergrade]] (~50 FPS on High settings at 1080p with M1 Pro)
* [[Five Nights At Freddy's Security Breach]]
* [[Friends vs. Friends]]
* [[Gloomwood]]
* [[God of War]] (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* [[Going Medieval]]
* [[Guilty Gear Strive]]
* [[Grand Theft Auto V]]
* [[Green Hell]]
* [[Halo 3]] (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* [[Halo Reach]] (MCC)
* [[HI-Fi RUSH]]
* [[Hogwarts Legacy]] - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* [[Hatsune Miku: Project DIVA Mega Mix+]] - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* [[Infinity Racer XD]]
* [[Kena: Bridge of Spirits]]
* [[Metal Gear Solid V: The Phantom Pain]]
* [[Overwatch 2]]
* [[QUBE 2]]
* [[People Playground]]
* [[Prodeus]]
* [[Ready or Not]]
* [[Risk of Rain 2]] (does not require `-disable-gpu-skinning` like Crossover 22)
* [[Scarlet Nexus]]
* [[Sonic GT]]
* [[Sonic illusions]]
* [[Sonic Omens]]
* [[Sonic Project '06]]
* [[Spider-Man (2018)]]
* [[Spider-Man Miles Morales]] - ''requires Windows ver fix''
* [[SpongeBob SquarePants: The Cosmic Shake]]
* [[StarCraft: Remastered]] - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* [[Tetris Effect: Connected]] - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* [[V Rising]]
* [[Warframe]] - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* [[WRATH: Aeon of Ruin]]

Not working well:
* [[Horizon Zero Dawn]] - slowdown issues
* [[Genshin Impact]] - Launches, but stuck when calling menu using esc

Not working yet:
* [[Apex Legends]] (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** [[Need for Speed Heat]]
** [[Need for Speed Unbound]]
** [[Tom Clancy's The Division 2]]
* [[Among Us]]
* [[Assassins Creed Odyssey]]
* [[Assassins Creed Valhalla]]
* [[BeamNG.Drive]] - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* [[Company of Heroes 3]]
* [[Death Stranding]]
* [[Doom (2016)]] - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* [[F1 20]] - Crash on launch (DX11 version running through GPTK is slower compared to Crossover 21)
* [[F1 21]] - Crash on launch
* [[F1 22]] - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* [[Grand Theft Auto IV]] - Rockstar games launcher crashes on launch, cracked version should work fine
* [[Halo Infinite]] - Crash on launch
* [[Hitman 3]] - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* [[Microsoft Flight Simulator 2020]] (Steam) - Crash on launch
* [[Monster Hunter Rise]] - DX12 Game, it launches but window goes dark after compiling shaders.
* [[Monster Hunter World]] - Black Screen on Launch
* [[New World]] - Game loaded but couldn't connect to server due to Easy Anti Cheat
* [[Payday 2]]
* [[Red Dead Redemption 2]]
* [[Rogue Company]] - anti-cheat conflict.
* [[s&box]] - crashes right on launch. (it should be DX11)
* [[Sea of Thieves]] - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* [[Saints Row IV: Re-Elected]] - Launches, but crashes when trying to load into game
* [[Slime Rancher 2]] - Launches, but can't into game from main menu
* [[Sonic Frontiers]] - AVX Requirement
* [[SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated]] - Crashes when loading
* [[Teardown]] - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* [[The Elder Scrolls V: Skyrim Special Edition]] - the launcher gives a "The program teardown.exe has encountered a serious problem" message, not allowing us to get into the game
* [[theHunter: Call of the Wild]] - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* [[The Joy of Creation: Story Mode]] - Crash on launch
* All DX9 games (duh, this is dx 11 & 12 only)
** [[30XX]] - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** [[Battleblock Theater]] - Black screen -> crash on launch
** [[Black Mesa]] - Starts to load to main menu at first but then crashes
** [[Castle Crashers]] - Black screen -> crash on launch
** [[Killing Floor 1]] - Crash on launch
** [[Left 4 Dead 2]] - Black screen -> crash on launch
** [[Lego Batman: The Videogame]] - Black screen -> crash on launch
** [[Lego Batman 2: DC Super Heros]] - Black screen -> crash on launch
** [[Lego Batman 3: Beyond Gotham]] - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** [[Mega Man Zero/ZX Legacy Collection]] - "Failed to create d3d9 device" -> crash on launch
** [[Sonic Mania]] - Crash on launch
** [[StarCraft II]] -> "Failed to initialize DirectX" error
** [[Star Wars: The Old Republic]]
** [[Battlefield 2]] - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}
[[Category:Lists]]

Control

2023-06-11T08:18:21Z

Andytizer: Game Porting Toolkit

{{Infobox game
|cover = Control cover.png
|developers =
{{Infobox game/row/developer|Remedy Entertainment}}
{{Infobox game/row/developer|Mi'pu'mi Games|ref=<ref>{{Refurl|url=https://www.mipumi.com/games/control/|title=Control - Mi'pu'mi Games|date=2022-10-05}}</ref>}}
{{Infobox game/row/developer|General Arcade|GOG.com|ref=<ref>{{Refurl|url=https://generalarcade.com/project/control-ultimate-edition/|title=CONTROL: Ultimate Edition|date=2022-08-16}}</ref>}}
|publishers =
{{Infobox game/row/publisher|505 Games}}
|engines =
{{Infobox game/row/engine|Northlight}}
|official site= https://controlgame.com
|reception =
{{Infobox game/row/reception|Metacritic|control|85}}
{{Infobox game/row/reception|Opencritic|7858/control|84}}
{{Infobox game/row/reception|IGDB|control|83}}
|taxonomy =
{{Infobox game/row/taxonomy/monetization | One-time game purchase, Expansion pack }}
{{Infobox game/row/taxonomy/microtransactions | None }}
{{Infobox game/row/taxonomy/modes | Singleplayer }}
{{Infobox game/row/taxonomy/pacing | Real-time }}
{{Infobox game/row/taxonomy/perspectives | Third-person }}
{{Infobox game/row/taxonomy/controls | Direct control }}
{{Infobox game/row/taxonomy/genres | Action }}
{{Infobox game/row/taxonomy/art styles | Realistic }}
{{Infobox game/row/taxonomy/themes | Sci-fi, North America }}
{{Infobox game/row/taxonomy/series | Control }}
|steam appid = 870780
|steam appid side =
|gogcom id = 2049187585
|hltb = 57507
|lutris = control
|strategywiki = Control
|mobygames = Control
|wikipedia = Control (video game)
|winehq =
|license = commercial
|pcgamingwiki = Control
|codeweavers = Control
|asg = Mvi9Wtjy29rF1KY1YW2Fbr/control
}}

{{Introduction
|release history =
|current state =
}}

==Availability==
{{Availability}}

{{Compatibility/macOS
|native = na
|native notes =
|rosetta 2 = na
|rosetta 2 notes =
|ios-ipados app = na
|ios-ipados app notes =
|crossover = runs
|crossover notes = Major graphical issues (Fixed in Crossover 22 Beta)(black screen).<ref>{{Refdevice|user=Andytizer|date=2021-05-07|device=MacBook Air M1 2020 8 GB RAM|os=macOS 11.3.1|method=CrossOver Nightly 2021-05-04|version=|store=GOG|resolution=|settings=|framerate=|controller=|url=|title=|comment=Black screen but good framerates}}</ref> Unplayable.<ref>{{Refurl|url=https://applesilicongames.com/games/Mvi9Wtjy29rF1KY1YW2Fbr/control|title=Control on Apple Silicon Games|date=2021-04-12|snippet=Crashes on "Press Return to continue" screen.}}</ref>
|wine = perfect
|wine notes = [[Game Porting Toolkit]] - the game must be run from Terminal, you must cd into the Control folder otherwise it'll complain of missing Data folder. Change the Control_DX12.exe to Control.exe and launch.
|parallels = playable
|parallels notes = Low framerates on M1 Mac but playable, make sure to launch DirectX 11 exe.<ref>{{Refdevice|user=Andytizer|date=2021-05-01|device=MacBook Air M1 2020 8 GB RAM|os=macOS 11.3.1|method=Windows ARM Build 21370 on Parallels 16.5|version=|store=GOG|resolution=|settings=|framerate=|controller=|url=|title=|comment=}}</ref>Unplayable.<ref>{{Refdevice|user=BringBackTron and Jhelzei|date=2021-04-20|device=MacBook Pro M1 2020 8GB RAM|os=macOS 11.3 Beta 8|method=Windows ARM Build 21359 on Parallels 16.5|version=|store=|resolution=1280x800|settings=Low|framerate=|controller=|url=|title=|comment=Stable FPS, unplayable due to crashing when combat starts}}</ref>Great framerates on medium settings with M1 Max.<ref>{{Refdevice|user=Captcool|date=2022-04-14|device=MacBook Pro M1 Max 32-Core GPU 64 GB|os=macOS 12.3.1|method=Parallels 17.1.2 + Windows 11 21H2 Build 22000.613|version=|resolution=1920x1080|settings=Medium|framerate=40|controller=|url=|title=|comment=}}</ref>
|windows 10 arm = na
|windows 10 arm notes =
|linux arm = na
|linux arm notes =
}}

==Screenshots==
<gallery>
Control_m1max.jpg|Control Parallels + Win11
</gallery>

{{References}}

[[Category:Games]]

Game Porting Toolkit

2023-06-11T07:03:54Z

Andytizer: /* = Nothing loads after a crash */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
*If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/$USER/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/$USER/my-game-prefix</code>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/$USER/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/$USER/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== Nothing loads after a crash ===
Try closing all Wine threads:
<pre>killall -9 wineserver && killall -9 wine64-preloader</pre>

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

===AVX===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

AVX requirement can be bypassed in some games, e.g Dying Light 2.

{{Fixbox|description=AVX Fix for Dying Light 2|ref=<ref>Reference</ref>|fix=
There is a workaround in Dying Light 2 which is to simply remove the "runtime_dx11.dll"

#Right click on DL2 on steam
#Manage
#Local files
#Navigate to "ph\work\bin\x64"
#Delete "runtime_dx11.dll"
#Start the game

If for some reason you need the "runtime_dx11.dll" back, just verify integrity of game files in Steam
}}

== Game compatibility list ==
{{ii}} '''Total number of games: '''{{#cargo_query:tables=Compatibility_macOS|fields=COUNT(*)|group by=_pageNamespace|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'}}
{{mm}} ''This list was last refreshed on '''{{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}'''. [{{fullurl:{{FULLPAGENAMEE}}|action=purge}} Purge] the page to refresh it.''
{{#cargo_query:
tables=Compatibility_macOS
|fields=Compatibility_macOS._pageName, Compatibility_macOS.wine
|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'
|limit=500
|offset=0
|format=template
|intro={{ListOfGames/intro}}
|template=ListOfGames/row
|outro=</table></div>
}}

Old list - this should be made into individual wiki articles in order to populate the automated list above, which tracks all game compatibility methods using Wine.

Working games:
* [[Astroneer]]
* [[Assassins Creed 3 Remastered]]
* [[Batman: Arkham Knight]] - launches with steam
* [[Bloodstained: Ritual of the Night]]
* [[Brick Rigs]]
* [[Genshin Impact]] 3.7 (m2max with 4k 60fps stable)
* [[Control]] (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* [[Crysis Remastered]]
* [[Cultic]]
* [[Cuphead]]
* [[Cyberpunk 2077]]
* [[Deep Rock Galactic]]
* [[Deceive Inc.]] - works well if launched without EAC
* [[Derail Valley]] (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* [[Diablo IV]] [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* [[Dread Templar]]
* [[Dying Light 2]] (needs AVX fix above)
* [[Dyson Sphere Program]] (some objects and main character weren't visible before)
* [[Elden Ring]]
* [[Final Fantasy VII Remake Intergrade]] (~50 FPS on High settings at 1080p with M1 Pro)
* [[Friends vs. Friends]]
* [[Gloomwood]]
* [[God of War]] (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* [[Going Medieval]]
* [[Guilty Gear Strive]]
* [[Grand Theft Auto V]]
* [[Green Hell]]
* [[Halo 3]] (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* [[Halo Reach]] (MCC)
* [[HI-Fi RUSH]]
* [[Hogwarts Legacy]] - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* [[Hatsune Miku: Project DIVA Mega Mix+]] - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* [[Kena: Bridge of Spirits]]
* [[Metal Gear Solid V: The Phantom Pain]]
* [[Overwatch 2]]
* [[QUBE 2]]
* [[People Playground]]
* [[Prodeus]]
* [[Ready or Not]]
* [[Risk of Rain 2]] (does not require `-disable-gpu-skinning` like Crossover 22)
* [[Scarlet Nexus]]
* [[Sonic GT]]
* [[Sonic illusions]]
* [[Sonic Omens]]
* [[Sonic P-06]]
* [[Spider-Man (2018)]]
* [[Spider-Man Miles Morales]] - ''requires Windows ver fix''
* [[SpongeBob SquarePants: The Cosmic Shake]]
* [[StarCraft: Remastered]] - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* [[Tetris Effect: Connected]] - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* [[V Rising]]
* [[Warframe]] - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* [[WRATH: Aeon of Ruin]]

Not working well:
* [[Horizon Zero Dawn]] - slowdown issues
* [[Genshin Impact]] - Launches, but stuck when calling menu using esc

Not working yet:
* [[Apex Legends]] (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** [[Need for Speed Heat]]
** [[Need for Speed Unbound]]
** [[Tom Clancy's The Division 2]]
* [[Among Us]]
* [[Assassins Creed Odyssey]]
* [[Assassins Creed Valhalla]]
* [[BeamNG.Drive]] - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* [[Company of Heroes 3]]
* [[Death Stranding]]
* [[Doom (2016)]] - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* [[F1 20]] - Crash on launch (DX11 version running through GPT is slower compared to Crossover 21)
* [[F1 21]] - Crash on launch
* [[F1 22]] - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* [[Grand Theft Auto IV]] - Rockstar games launcher crashes on launch, cracked version should work fine
* [[Halo Infinite]] - Crash on launch
* [[Hitman 3]] - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* [[Microsoft Flight Simulator 2020]] (Steam) - Crash on launch
* [[Monster Hunter Rise]] - DX12 Game, it launches but window goes dark after compiling shaders.
* [[Monster Hunter World]] - Black Screen on Launch
* [[New World]] - Game loaded but couldn't connect to server due to Easy Anti Cheat
* [[Payday 2]]
* [[Red Dead Redemption 2]]
* [[Rogue Company]] - anti-cheat conflict.
* [[s&box]] - crashes right on launch. (it should be DX11)
* [[Sea of Thieves]] - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* [[Saints Row IV: Re-Elected]] - Launches, but crashes when trying to load into game
* [[Slime Rancher 2]] - Launches, but can't into game from main menu
* [[SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated]] - Crashes when loading
* [[Teardown]] - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* [[The Elder Scrolls V: Skyrim Special Edition]] - the launcher gives a "The program teardown.exe has encountered a serious problem" message, not allowing us to get into the game
* [[theHunter: Call of the Wild]] - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* All DX9 games (duh, this is dx 11 & 12 only)
** [[30XX]] - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** [[Battleblock Theater]] - Black screen -> crash on launch
** [[Black Mesa]] - Starts to load to main menu at first but then crashes
** [[Castle Crashers]] - Black screen -> crash on launch
** [[Killing Floor 1]] - Crash on launch
** [[Left 4 Dead 2]] - Black screen -> crash on launch
** [[Lego Batman: The Videogame]] - Black screen -> crash on launch
** [[Lego Batman 2: DC Super Heros]] - Black screen -> crash on launch
** [[Lego Batman 3: Beyond Gotham]] - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** [[Mega Man Zero/ZX Legacy Collection]] - "Failed to create d3d9 device" -> crash on launch
** [[Sonic Mania]] - Crash on launch
** [[StarCraft II]] -> "Failed to initialize DirectX" error
** [[Star Wars: The Old Republic]]
** [[Battlefield 2]] - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}
[[Category:Lists]]

Game Porting Toolkit

2023-06-11T06:54:15Z

Andytizer: /* Troubleshooting */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
*If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/$USER/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/$USER/my-game-prefix</code>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/$USER/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/$USER/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== Nothing loads after a crash ==
Try closing all Wine threads:
<pre>killall -9 wineserver && killall -9 wine64-preloader</pre>

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

===AVX===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

AVX requirement can be bypassed in some games, e.g Dying Light 2.

{{Fixbox|description=AVX Fix for Dying Light 2|ref=<ref>Reference</ref>|fix=
There is a workaround in Dying Light 2 which is to simply remove the "runtime_dx11.dll"

#Right click on DL2 on steam
#Manage
#Local files
#Navigate to "ph\work\bin\x64"
#Delete "runtime_dx11.dll"
#Start the game

If for some reason you need the "runtime_dx11.dll" back, just verify integrity of game files in Steam
}}

== Game compatibility list ==
{{ii}} '''Total number of games: '''{{#cargo_query:tables=Compatibility_macOS|fields=COUNT(*)|group by=_pageNamespace|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'}}
{{mm}} ''This list was last refreshed on '''{{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}'''. [{{fullurl:{{FULLPAGENAMEE}}|action=purge}} Purge] the page to refresh it.''
{{#cargo_query:
tables=Compatibility_macOS
|fields=Compatibility_macOS._pageName, Compatibility_macOS.wine
|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'
|limit=500
|offset=0
|format=template
|intro={{ListOfGames/intro}}
|template=ListOfGames/row
|outro=</table></div>
}}

Old list - this should be made into individual wiki articles in order to populate the automated list above, which tracks all game compatibility methods using Wine.

Working games:
* [[Astroneer]]
* [[Assassins Creed 3 Remastered]]
* [[Batman: Arkham Knight]] - launches with steam
* [[Bloodstained: Ritual of the Night]]
* [[Brick Rigs]]
* [[Genshin Impact]] 3.7 (m2max with 4k 60fps stable)
* [[Control]] (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* [[Crysis Remastered]]
* [[Cultic]]
* [[Cuphead]]
* [[Cyberpunk 2077]]
* [[Deep Rock Galactic]]
* [[Deceive Inc.]] - works well if launched without EAC
* [[Derail Valley]] (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* [[Diablo IV]] [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* [[Dread Templar]]
* [[Dying Light 2]] (needs AVX fix above)
* [[Dyson Sphere Program]] (some objects and main character weren't visible before)
* [[Elden Ring]]
* [[Final Fantasy VII Remake Intergrade]] (~50 FPS on High settings at 1080p with M1 Pro)
* [[Friends vs. Friends]]
* [[Gloomwood]]
* [[God of War]] (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* [[Going Medieval]]
* [[Guilty Gear Strive]]
* [[Grand Theft Auto V]]
* [[Green Hell]]
* [[Halo 3]] (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* [[Halo Reach]] (MCC)
* [[HI-Fi RUSH]]
* [[Hogwarts Legacy]] - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* [[Hatsune Miku: Project DIVA Mega Mix+]] - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* [[Kena: Bridge of Spirits]]
* [[Metal Gear Solid V: The Phantom Pain]]
* [[Overwatch 2]]
* [[QUBE 2]]
* [[People Playground]]
* [[Prodeus]]
* [[Ready or Not]]
* [[Risk of Rain 2]] (does not require `-disable-gpu-skinning` like Crossover 22)
* [[Scarlet Nexus]]
* [[Sonic GT]]
* [[Sonic illusions]]
* [[Sonic Omens]]
* [[Sonic P-06]]
* [[Spider-Man (2018)]]
* [[Spider-Man Miles Morales]] - ''requires Windows ver fix''
* [[SpongeBob SquarePants: The Cosmic Shake]]
* [[StarCraft: Remastered]] - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* [[Tetris Effect: Connected]] - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* [[V Rising]]
* [[Warframe]] - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* [[WRATH: Aeon of Ruin]]

Not working well:
* [[Horizon Zero Dawn]] - slowdown issues
* [[Genshin Impact]] - Launches, but stuck when calling menu using esc

Not working yet:
* [[Apex Legends]] (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** [[Need for Speed Heat]]
** [[Need for Speed Unbound]]
** [[Tom Clancy's The Division 2]]
* [[Among Us]]
* [[Assassins Creed Odyssey]]
* [[Assassins Creed Valhalla]]
* [[BeamNG.Drive]] - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* [[Company of Heroes 3]]
* [[Death Stranding]]
* [[Doom (2016)]] - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* [[F1 20]] - Crash on launch (DX11 version running through GPT is slower compared to Crossover 21)
* [[F1 21]] - Crash on launch
* [[F1 22]] - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* [[Grand Theft Auto IV]] - Rockstar games launcher crashes on launch, cracked version should work fine
* [[Halo Infinite]] - Crash on launch
* [[Hitman 3]] - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* [[Microsoft Flight Simulator 2020]] (Steam) - Crash on launch
* [[Monster Hunter Rise]] - DX12 Game, it launches but window goes dark after compiling shaders.
* [[Monster Hunter World]] - Black Screen on Launch
* [[New World]] - Game loaded but couldn't connect to server due to Easy Anti Cheat
* [[Payday 2]]
* [[Red Dead Redemption 2]]
* [[Rogue Company]] - anti-cheat conflict.
* [[s&box]] - crashes right on launch. (it should be DX11)
* [[Sea of Thieves]] - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* [[Saints Row IV: Re-Elected]] - Launches, but crashes when trying to load into game
* [[Slime Rancher 2]] - Launches, but can't into game from main menu
* [[SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated]] - Crashes when loading
* [[Teardown]] - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* [[The Elder Scrolls V: Skyrim Special Edition]] - the launcher gives a "The program teardown.exe has encountered a serious problem" message, not allowing us to get into the game
* [[theHunter: Call of the Wild]] - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* All DX9 games (duh, this is dx 11 & 12 only)
** [[30XX]] - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** [[Battleblock Theater]] - Black screen -> crash on launch
** [[Black Mesa]] - Starts to load to main menu at first but then crashes
** [[Castle Crashers]] - Black screen -> crash on launch
** [[Killing Floor 1]] - Crash on launch
** [[Left 4 Dead 2]] - Black screen -> crash on launch
** [[Lego Batman: The Videogame]] - Black screen -> crash on launch
** [[Lego Batman 2: DC Super Heros]] - Black screen -> crash on launch
** [[Lego Batman 3: Beyond Gotham]] - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** [[Mega Man Zero/ZX Legacy Collection]] - "Failed to create d3d9 device" -> crash on launch
** [[Sonic Mania]] - Crash on launch
** [[StarCraft II]] -> "Failed to initialize DirectX" error
** [[Star Wars: The Old Republic]]
** [[Battlefield 2]] - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}
[[Category:Lists]]

Game Porting Toolkit

2023-06-11T06:45:04Z

Andytizer: /* Toolkit install instructions */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
*If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/$USER/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/$USER/my-game-prefix</code>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/$USER/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/$USER/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

===AVX===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

AVX requirement can be bypassed in some games, e.g Dying Light 2.

{{Fixbox|description=AVX Fix for Dying Light 2|ref=<ref>Reference</ref>|fix=
There is a workaround in Dying Light 2 which is to simply remove the "runtime_dx11.dll"

#Right click on DL2 on steam
#Manage
#Local files
#Navigate to "ph\work\bin\x64"
#Delete "runtime_dx11.dll"
#Start the game

If for some reason you need the "runtime_dx11.dll" back, just verify integrity of game files in Steam
}}

== Game compatibility list ==
{{ii}} '''Total number of games: '''{{#cargo_query:tables=Compatibility_macOS|fields=COUNT(*)|group by=_pageNamespace|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'}}
{{mm}} ''This list was last refreshed on '''{{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}'''. [{{fullurl:{{FULLPAGENAMEE}}|action=purge}} Purge] the page to refresh it.''
{{#cargo_query:
tables=Compatibility_macOS
|fields=Compatibility_macOS._pageName, Compatibility_macOS.wine
|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'
|limit=500
|offset=0
|format=template
|intro={{ListOfGames/intro}}
|template=ListOfGames/row
|outro=</table></div>
}}

Old list - this should be made into individual wiki articles in order to populate the automated list above, which tracks all game compatibility methods using Wine.

Working games:
* [[Astroneer]]
* [[Assassins Creed 3 Remastered]]
* [[Batman: Arkham Knight]] - launches with steam
* [[Bloodstained: Ritual of the Night]]
* [[Brick Rigs]]
* [[Genshin Impact]] 3.7 (m2max with 4k 60fps stable)
* [[Control]] (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* [[Crysis Remastered]]
* [[Cultic]]
* [[Cuphead]]
* [[Cyberpunk 2077]]
* [[Deep Rock Galactic]]
* [[Deceive Inc.]] - works well if launched without EAC
* [[Derail Valley]] (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* [[Diablo IV]] [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* [[Dread Templar]]
* [[Dying Light 2]] (needs AVX fix above)
* [[Dyson Sphere Program]] (some objects and main character weren't visible before)
* [[Elden Ring]]
* [[Final Fantasy VII Remake Intergrade]] (~50 FPS on High settings at 1080p with M1 Pro)
* [[Friends vs. Friends]]
* [[Gloomwood]]
* [[God of War]] (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* [[Going Medieval]]
* [[Guilty Gear Strive]]
* [[Grand Theft Auto V]]
* [[Green Hell]]
* [[Halo 3]] (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* [[Halo Reach]] (MCC)
* [[HI-Fi RUSH]]
* [[Hogwarts Legacy]] - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* [[Hatsune Miku: Project DIVA Mega Mix+]] - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* [[Kena: Bridge of Spirits]]
* [[Metal Gear Solid V: The Phantom Pain]]
* [[Overwatch 2]]
* [[QUBE 2]]
* [[People Playground]]
* [[Prodeus]]
* [[Ready or Not]]
* [[Risk of Rain 2]] (does not require `-disable-gpu-skinning` like Crossover 22)
* [[Scarlet Nexus]]
* [[Sonic GT]]
* [[Sonic illusions]]
* [[Sonic Omens]]
* [[Sonic P-06]]
* [[Spider-Man (2018)]]
* [[Spider-Man Miles Morales]] - ''requires Windows ver fix''
* [[SpongeBob SquarePants: The Cosmic Shake]]
* [[StarCraft: Remastered]] - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* [[Tetris Effect: Connected]] - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* [[V Rising]]
* [[Warframe]] - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* [[WRATH: Aeon of Ruin]]

Not working well:
* [[Horizon Zero Dawn]] - slowdown issues
* [[Genshin Impact]] - Launches, but stuck when calling menu using esc

Not working yet:
* [[Apex Legends]] (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** [[Need for Speed Heat]]
** [[Need for Speed Unbound]]
** [[Tom Clancy's The Division 2]]
* [[Among Us]]
* [[Assassins Creed Odyssey]]
* [[Assassins Creed Valhalla]]
* [[BeamNG.Drive]] - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* [[Company of Heroes 3]]
* [[Death Stranding]]
* [[Doom (2016)]] - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* [[F1 20]] - Crash on launch (DX11 version running through GPT is slower compared to Crossover 21)
* [[F1 21]] - Crash on launch
* [[F1 22]] - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* [[Grand Theft Auto IV]] - Rockstar games launcher crashes on launch, cracked version should work fine
* [[Halo Infinite]] - Crash on launch
* [[Hitman 3]] - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* [[Microsoft Flight Simulator 2020]] (Steam) - Crash on launch
* [[Monster Hunter Rise]] - DX12 Game, it launches but window goes dark after compiling shaders.
* [[Monster Hunter World]] - Black Screen on Launch
* [[New World]] - Game loaded but couldn't connect to server due to Easy Anti Cheat
* [[Payday 2]]
* [[Red Dead Redemption 2]]
* [[Rogue Company]] - anti-cheat conflict.
* [[s&box]] - crashes right on launch. (it should be DX11)
* [[Sea of Thieves]] - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* [[Saints Row IV: Re-Elected]] - Launches, but crashes when trying to load into game
* [[Slime Rancher 2]] - Launches, but can't into game from main menu
* [[SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated]] - Crashes when loading
* [[Teardown]] - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* [[The Elder Scrolls V: Skyrim Special Edition]] - the launcher gives a "The program teardown.exe has encountered a serious problem" message, not allowing us to get into the game
* [[theHunter: Call of the Wild]] - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* All DX9 games (duh, this is dx 11 & 12 only)
** [[30XX]] - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** [[Battleblock Theater]] - Black screen -> crash on launch
** [[Black Mesa]] - Starts to load to main menu at first but then crashes
** [[Castle Crashers]] - Black screen -> crash on launch
** [[Killing Floor 1]] - Crash on launch
** [[Left 4 Dead 2]] - Black screen -> crash on launch
** [[Lego Batman: The Videogame]] - Black screen -> crash on launch
** [[Lego Batman 2: DC Super Heros]] - Black screen -> crash on launch
** [[Lego Batman 3: Beyond Gotham]] - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** [[Mega Man Zero/ZX Legacy Collection]] - "Failed to create d3d9 device" -> crash on launch
** [[Sonic Mania]] - Crash on launch
** [[StarCraft II]] -> "Failed to initialize DirectX" error
** [[Star Wars: The Old Republic]]
** [[Battlefield 2]] - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}
[[Category:Lists]]

Game Porting Toolkit

2023-06-10T23:20:21Z

Andytizer: /* Game compatibility list */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/$USER/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/$USER/my-game-prefix</code>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/$USER/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/$USER/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== AVX ===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

== Game compatibility list ==
{{ii}} '''Total number of games: '''{{#cargo_query:tables=Compatibility_macOS|fields=COUNT(*)|group by=_pageNamespace|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'}}
{{mm}} ''This list was last refreshed on '''{{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}'''. [{{fullurl:{{FULLPAGENAMEE}}|action=purge}} Purge] the page to refresh it.''
{{#cargo_query:
tables=Compatibility_macOS
|fields=Compatibility_macOS._pageName, Compatibility_macOS.wine
|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'
|limit=500
|offset=0
|format=template
|intro={{ListOfGames/intro}}
|template=ListOfGames/row
|outro=</table></div>
}}

Old list - this should be made into individual wiki articles in order to populate the automated list above, which tracks all game compatibility methods using Wine.

Working games:
* [[Astroneer]]
* [[Assassins Creed 3 Remastered]]
* [[Batman: Arkham Knight]] - launches with steam
* [[Bloodstained: Ritual of the Night]]
* [[Brick Rigs]]
* [[Genshin Impact]] 3.7 (m2max with 4k 60fps stable)
* [[Control]] (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* [[Crysis Remastered]]
* [[Cultic]]
* [[Cuphead]]
* [[Cyberpunk 2077]]
* [[Deep Rock Galactic]]
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* [[Diablo IV]] [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dread Templar
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* Gloomwood
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Grand Theft Auto V
* Green Hell
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* People Playground
* Prodeus
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic GT
* Sonic illusions
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* WRATH: Aeon of Ruin

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc

Not working yet:
* Apex (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Assassins Creed Odyssey
* Assassins Creed Valhalla
* BeamNG.Drive - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* Company of Heroes 3
* Doom (2016) - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* F1 20 - Crash on launch (DX11 version running through GPT is slower compared to Crossover 21)
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* s&box - crashes right on launch. (it should be DX11)
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Saints Row IV: Re-Elected - Launches, but crashes when trying to load into game
* Slime Rancher 2 - Launches, but can't into game from main menu
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* Teardown - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* The Elder Scrolls V: Skyrim Special Edition - the launcher gives a "The program teardown.exe has encountered a serious problem" message, not allowing us to get into the game
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* All DX9 games (duh, this is dx 11 & 12 only)
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Battleblock Theater - Black screen -> crash on launch
** Black Mesa - Starts to load to main menu at first but then crashes
** Castle Crashers - Black screen -> crash on launch
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Lego Batman: The Videogame - Black screen -> crash on launch
** Lego Batman 2: DC Super Heros - Black screen -> crash on launch
** Lego Batman 3: Beyond Gotham - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}
[[Category:Lists]]

Game Porting Toolkit

2023-06-10T23:19:35Z

Andytizer: /* Game compatibility list */ Started articlising

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/$USER/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* Make sure your Game Porting Toolkit Wine Prefix is selected. If you followed Apple's guide this is <code>/Users/$USER/my-game-prefix</code>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/$USER/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/$USER/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== AVX ===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

== Game compatibility list ==
{{ii}} '''Total number of games: '''{{#cargo_query:tables=Compatibility_macOS|fields=COUNT(*)|group by=_pageNamespace|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'}}
{{mm}} ''This list was last refreshed on '''{{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}'''. [{{fullurl:{{FULLPAGENAMEE}}|action=purge}} Purge] the page to refresh it.''
{{#cargo_query:
tables=Compatibility_macOS
|fields=Compatibility_macOS._pageName, Compatibility_macOS.wine
|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'
|limit=500
|offset=0
|format=template
|intro={{ListOfGames/intro}}
|template=ListOfGames/row
|outro=</table></div>
}}

Old list - this should be made into individual wiki articles in order to populate the automated list above, which tracks all game compatibility methods using Wine.

Working games:
* [[Astroneer]]
* [[Assassins Creed 3 Remastered]]
* [[Batman: Arkham Knight]] - launches with steam
* [[Bloodstained: Ritual of the Night]]
* [[Brick Rigs]
* [[Genshin Impact]] 3.7 (m2max with 4k 60fps stable)
* [[Control]] (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* [[Crysis Remastered]]
* [[Cultic]]
* [[Cuphead]]
* [[Cyberpunk 2077]]
* [[Deep Rock Galactic]]
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dread Templar
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* Gloomwood
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Grand Theft Auto V
* Green Hell
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* People Playground
* Prodeus
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic GT
* Sonic illusions
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* WRATH: Aeon of Ruin

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc

Not working yet:
* Apex (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Assassins Creed Odyssey
* Assassins Creed Valhalla
* BeamNG.Drive - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* Company of Heroes 3
* Doom (2016) - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* F1 20 - Crash on launch (DX11 version running through GPT is slower compared to Crossover 21)
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* s&box - crashes right on launch. (it should be DX11)
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Saints Row IV: Re-Elected - Launches, but crashes when trying to load into game
* Slime Rancher 2 - Launches, but can't into game from main menu
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* Teardown - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* The Elder Scrolls V: Skyrim Special Edition - the launcher gives a "The program teardown.exe has encountered a serious problem" message, not allowing us to get into the game
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* All DX9 games (duh, this is dx 11 & 12 only)
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Battleblock Theater - Black screen -> crash on launch
** Black Mesa - Starts to load to main menu at first but then crashes
** Castle Crashers - Black screen -> crash on launch
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Lego Batman: The Videogame - Black screen -> crash on launch
** Lego Batman 2: DC Super Heros - Black screen -> crash on launch
** Lego Batman 3: Beyond Gotham - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}
[[Category:Lists]]

Game Porting Toolkit

2023-06-10T18:17:24Z

Andytizer: /* Game compatibility list */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/[your macOS username]/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/?????/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== AVX ===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

== Game compatibility list ==
{{ii}} '''Total number of games: '''{{#cargo_query:tables=Compatibility_macOS|fields=COUNT(*)|group by=_pageNamespace|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'}}
{{mm}} ''This list was last refreshed on '''{{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}'''. [{{fullurl:{{FULLPAGENAMEE}}|action=purge}} Purge] the page to refresh it.''
{{#cargo_query:
tables=Compatibility_macOS
|fields=Compatibility_macOS._pageName, Compatibility_macOS.wine
|where=Compatibility_macOS.wine='perfect' OR Compatibility_macOS.wine='playable' OR Compatibility_macOS.wine='runs' OR Compatibility_macOS.wine='menu'
|limit=500
|offset=0
|format=template
|intro={{ListOfGames/intro}}
|template=ListOfGames/row
|outro=</table></div>
}}

Old list - this should be made into individual wiki articles in order to populate the automated list above, which tracks all game compatibility methods using Wine.

Working games:
* Astroneer
* Assassins Creed 3 Remastered
* Batman: Arkham Knight - launches with steam
* Bloodstained: Ritual of the Night
* Brick Rigs
* Genshin Impact 3.7 (m2max with 4k 60fps stable)
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Grand Theft Auto V
* Green Hell
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* People Playground
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic GT
* Sonic illusions
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc

Not working yet:
* Apex (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Assassins Creed Odyssey
* Assassins Creed Valhalla
* BeamNG.Drive - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* Company of Heroes 3
* Doom (2016) - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* F1 20 - Crash on launch (DX11 version running through GPT is slower compared to Crossover 21)
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* s&box - crashes right on launch. (it should be DX11)
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Saints Row IV: Re-Elected - Launches, but crashes when trying to load into game
* Slime Rancher 2 - Launches, but can't into game from main menu
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* Teardown - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* The Elder Scrolls V: Skyrim Special Edition - the launcher gives a "The program teardown.exe has encountered a serious problem" message, not allowing us to get into the game
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* All DX9 games (duh, this is dx 11 & 12 only)
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Battleblock Theater - Black screen -> crash on launch
** Black Mesa - Starts to load to main menu at first but then crashes
** Castle Crashers - Black screen -> crash on launch
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Lego Batman: The Videogame - Black screen -> crash on launch
** Lego Batman 2: DC Super Heros - Black screen -> crash on launch
** Lego Batman 3: Beyond Gotham - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}
[[Category:Lists]]

Hatsune Miku: Project DIVA MEGA39

2023-06-10T17:18:42Z

Andytizer: Changed redirect target from Https://www.applegamingwiki.com/wiki/Hatsune Miku: Project DIVA Mega Mix+ to Hatsune Miku: Project DIVA Mega Mix+

#REDIRECT [[Hatsune_Miku:_Project_DIVA_Mega_Mix%2B]]

Hatsune Miku: Project DIVA MEGA39

2023-06-10T17:18:25Z

Andytizer: Redirected page to Https://www.applegamingwiki.com/wiki/Hatsune Miku: Project DIVA Mega Mix+

#REDIRECT [[https://www.applegamingwiki.com/wiki/Hatsune_Miku:_Project_DIVA_Mega_Mix%2B]]

Game Porting Toolkit

2023-06-10T16:52:30Z

Andytizer: /* AVX */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/[your macOS username]/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/?????/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== AVX ===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

== Game compatibility list ==
Working games:
* Astroneer
* Assassins Creed 3 Remastered
* Batman: Arkham Knight - launches with steam
* Bloodstained: Ritual of the Night
* Brick Rigs
* Genshin Impact 3.7 (m2max with 4k 60fps stable)
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Grand Theft Auto V
* Green Hell
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* People Playground
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic GT
* Sonic illusions
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc

Not working yet:
* Apex (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Assassins Creed Odyssey
* Assassins Creed Valhalla
* BeamNG.Drive - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* Company of Heroes 3
* Doom (2016) - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* F1 20 - Crash on launch (DX11 version running through GPT is slower compared to Crossover 21)
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* s&box - crashes right on launch. (it should be DX11)
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Saints Row IV: Re-Elected - Launches, but crashes when trying to load into game
* Slime Rancher 2 - Launches, but can't into game from main menu
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* Teardown - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* The Elder Scrolls V: Skyrim Special Edition - the launcher gives a "The program teardown.exe has encountered a serious problem" message, not allowing us to get into the game
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* All DX9 games (duh, this is dx 11 & 12 only)
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Battleblock Theater - Black screen -> crash on launch
** Black Mesa - Starts to load to main menu at first but then crashes
** Castle Crashers - Black screen -> crash on launch
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Lego Batman: The Videogame - Black screen -> crash on launch
** Lego Batman 2: DC Super Heros - Black screen -> crash on launch
** Lego Batman 3: Beyond Gotham - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-10T16:52:16Z

Andytizer: /* Troubleshooting */ Reformatting

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/[your macOS username]/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
=== Steam login black screen ===
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}

{{Fixbox|description=Alternate Steam launch command|ref=|fix=
Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>
}}

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/?????/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

=== Steam crashes straight after opening ===
{{Fixbox|description=Disconnect external monitors|ref=<ref>Reference</ref>|fix=
Disconnect any external monitors.
}}

=== Battle.net launcher won't re-launch ===
Re-install the launcher to reopen, no other fix at the moment.

===Windows version too old===
{{Fixbox|description=Name|ref=<ref>Reference</ref>|fix=
'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>
}}

=== steamwebhelper.exe crashes ===
This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

=== AVX ===
AVX and AVX2 games are not supported by Apple's arm64 chipset, e.g. Red Dead Redemption 2.

=== Anti-cheat and DRM ===
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.

=== My game won’t run because it requires Mono, .NET, or the MSVCRT runtime ===
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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

=== Controller issues ===
{{Fixbox|description=Steam beta|ref=<ref>Reference</ref>|fix=
Issues may be fixed by enrolling into the Steam beta.
}}

=== My game looks pixelated and the display resolution is limited ===
{{Fixbox|description=Enable Retina mode|ref=|fix=
Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>
}}

== Game compatibility list ==
Working games:
* Astroneer
* Assassins Creed 3 Remastered
* Batman: Arkham Knight - launches with steam
* Bloodstained: Ritual of the Night
* Brick Rigs
* Genshin Impact 3.7 (m2max with 4k 60fps stable)
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Grand Theft Auto V
* Green Hell
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* People Playground
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic GT
* Sonic illusions
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc

Not working yet:
* Apex (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Assassins Creed Odyssey
* Assassins Creed Valhalla
* BeamNG.Drive - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* Company of Heroes 3
* Doom (2016) - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* F1 20 - Crash on launch (DX11 version running through GPT is slower compared to Crossover 21)
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* s&box - crashes right on launch. (it should be DX11)
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Saints Row IV: Re-Elected - Launches, but crashes when trying to load into game
* Slime Rancher 2 - Launches, but can't into game from main menu
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* Teardown - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* The Elder Scrolls V: Skyrim Special Edition - the launcher gives a "The program teardown.exe has encountered a serious problem" message, not allowing us to get into the game
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* All DX9 games (duh, this is dx 11 & 12 only)
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Battleblock Theater - Black screen -> crash on launch
** Black Mesa - Starts to load to main menu at first but then crashes
** Castle Crashers - Black screen -> crash on launch
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Lego Batman: The Videogame - Black screen -> crash on launch
** Lego Batman 2: DC Super Heros - Black screen -> crash on launch
** Lego Batman 3: Beyond Gotham - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-10T16:47:09Z

Andytizer: /* Troubleshooting */ New method to bypass Steam login issue

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/[your macOS username]/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

{{Fixbox|description=Use macOS Steam login|ref=<ref>https://github.com/IsaacMarovitz/Whisky/issues/41#issuecomment-1585640483</ref>|fix=
#Login to Steam macOS.
#From <code>/Users/?????/Library/Application Support/Steam</code>, copy three files/folders: config, registry.vdf, userdata.
#Paste into <code>~/my-game-prefix/drive_c/Program Files (x86)/Steam/</code>
}}

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Astroneer
* Assassins Creed 3 Remastered
* Batman: Arkham Knight - launches with steam
* Bloodstained: Ritual of the Night
* Brick Rigs
* Genshin Impact 3.7 (m2max with 4k 60fps stable)
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Grand Theft Auto V
* Green Hell
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* People Playground
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic GT
* Sonic illusions
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc

Not working yet:
* Apex (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Assassins Creed Odyssey
* Assassins Creed Valhalla
* BeamNG.Drive - Loads into Main Menu but crashes on last step of loading into a level with a "UI Process failed to respond in time" error
* Company of Heroes 3
* Doom (2016) - "FATAL ERROR: wglCreateContextAttribsARB failed" message on launch
* F1 20 - Crash on launch (DX11 version running through GPT is slower compared to Crossover 21)
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* s&box - crashes right on launch. (it should be DX11)
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Saints Row IV: Re-Elected - Launches, but crashes when trying to load into game
* Slime Rancher 2 - Launches, but can't into game from main menu
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* Teardown - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* The Elder Scrolls V: Skyrim Special Edition - the launcher gives a "The program teardown.exe has encountered a serious problem" message, not allowing us to get into the game
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* All DX9 games (duh, this is dx 11 & 12 only)
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Battleblock Theater - Black screen -> crash on launch
** Black Mesa - Starts to load to main menu at first but then crashes
** Castle Crashers - Black screen -> crash on launch
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Lego Batman: The Videogame - Black screen -> crash on launch
** Lego Batman 2: DC Super Heros - Black screen -> crash on launch
** Lego Batman 3: Beyond Gotham - Black screen -> crash on launch (You can switch to DX11 but are currently unable to do so since the game will not launch)
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-10T07:17:50Z

Andytizer: /* Homebrew */ path

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Set the path:
<pre>
(echo; echo 'eval "$(/usr/local/bin/brew shellenv)"') >> /Users/andrewtsai/.zprofile
eval "$(/usr/local/bin/brew shellenv)"
</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Astroneer
* Bloodstained: Ritual of the Night
* Brick Rigs
* Geshin Impact 3.7 (m2max with 4k 60fps stable)
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Grand Theft Auto V
* Green Hell
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; [https://github.com/blueskythlikesclouds/DivaModLoader/releases DivaModLoader] and [https://github.com/Still34/azura-diva/releases DivaNoSpy] recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen: use [https://github.com/nastys/IntroPatch/releases IntroPatch] as a workaround
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* People Playground
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc
* Saints Row IV: Re-Elected - Launches, but crashes when trying to load into game
* Slime Rancher 2 - Launches, but can't into game from main menu

Not working yet:
* Apex (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Batman: Arkham Knight - doesn't launch, freezes steam and makes me force close and reopen steam
* Company of Heroes 3
* F1 20 - Crash on launch (DX11 version running through GPT is slower compared to Crossover 21)
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* s&box - crashes right on launch. (it should be DX11)
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* Teardown - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Black Mesa - Starts to load to main menu at first but then crashes
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-09T21:19:59Z

Andytizer: /* Troubleshooting */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Astroneer
* Bloodstained: Ritual of the Night
* Geshin Impact 3.7 (m2max with 4k 60fps stable)
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Grand Theft Auto V
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* People Playground
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc
* Slime Rancher 2 - Launches, but can't into game from main menu

Not working yet:
* Apex (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Company of Heroes 3
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* Teardown - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Black Mesa - Starts to load to main menu at first but then crashes
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-09T20:55:43Z

Andytizer: /* Game compatibility list */ Hogwarts legacy fix

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Astroneer
* Bloodstained: Ritual of the Night
* Geshin Impact 3.7 (m2max with 4k 60fps stable)
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Grand Theft Auto V
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy - launches fine first time but then won't relaunch - can be fixed by deleting ~/my-game-prefix/drive_c/ProgramData/Hogwarts Legacy - these are the files that are created at first launch that prevent relaunching
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* People Playground
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc
* Slime Rancher 2 - Launches, but can't into game from main menu

Not working yet:
* Apex (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Company of Heroes 3
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* Teardown - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Black Mesa - Starts to load to main menu at first but then crashes
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-09T13:35:51Z

Andytizer: /* Battle.net */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Astroneer
* Bloodstained: Ritual of the Night
* Geshin Impact 3.7 (m2max with 4k 60fps stable)
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* People Playground
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc
* Slime Rancher 2 - Launches, but can't into game from main menu

Not working yet:
* Apex (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Company of Heroes 3
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* Teardown - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Black Mesa - Starts to load to main menu at first but then crashes
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-09T13:17:31Z

Andytizer: /* Battle.net */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Astroneer
* Bloodstained: Ritual of the Night
* Geshin Impact 3.7 (m2max with 4k 60fps stable)
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* People Playground
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc
* Slime Rancher 2 - Launches, but can't into game from main menu

Not working yet:
* Apex (it will stuck because of anti-cheat)
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Company of Heroes 3
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* Teardown - When trying to launch, gives a error, "The program teardown.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience."
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-09T10:26:19Z

Andytizer: Changing the Battle net instructions so that it's the same as everything else to simplify things my-game-prefix

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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. This will create a Wine prefix called <code>my-game-prefix</code> but could be renamed to anything.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net, you can choose to use <code>my-game-prefix</code> or change this to anything else.
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support with the Heroic Games Launcher ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Bloodstained: Ritual of the Night
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* Friends vs. Friends
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* Halo Reach (MCC)
* HI-Fi RUSH
* Hogwarts Legacy
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* V Rising
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues
* Genshin Impact - Launches, but stuck when calling menu using esc

Not working yet:
* Any games that use the EA Launcher
** Need for Speed Heat
** Need for Speed Unbound
** Tom Clancy's The Division 2
* Among Us
* Company of Heroes 3
* F1 21 - Crash on launch
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* New World - Game loaded but couldn't connect to server due to Easy Anti Cheat
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* SpongeBob Squarepants: Battle for Bikini Bottom Rehydrated - Crashes when loading
* theHunter: Call of the Wild - Crash on launch (Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000140b227f8))
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Star Wars: The Old Republic
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-09T00:35:30Z

Andytizer: Added Windows fix to Battle.net

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

If you are running Diablo IV, then you need to run this script to update the Wineprefix to appear as a more recent version of Windows:
<pre>
WINEPREFIX=~/battle-net `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
WINEPREFIX=~/battle-net `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
WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Bloodstained: Ritual of the Night
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* HI-Fi RUSH
* Hogwarts Legacy
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues

Not working yet:
* Among Us
* Company of Heroes 3
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-09T00:27:37Z

Andytizer: /* Toolkit install instructions */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

===Wine prefix ===
A Wine prefix contains a virtual C: drive, similar to a Bottle in [[CrossOver]]. 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.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

Now you are ready to install a launcher or individual Windows games into this Wine prefix, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Bloodstained: Ritual of the Night
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* HI-Fi RUSH
* Hogwarts Legacy
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues

Not working yet:
* Among Us
* Company of Heroes 3
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-08T23:16:40Z

Andytizer: /* Battle.net */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

===Wine prefix ===
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.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

Now you are ready to install a launcher or individual Windows games, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net] and place in your Downloads folder.

Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Bloodstained: Ritual of the Night
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* HI-Fi RUSH
* Hogwarts Legacy
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues

Not working yet:
* Among Us
* Company of Heroes 3
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-08T23:14:23Z

Andytizer: /* Shortcut */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

===Wine prefix ===
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.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

Now you are ready to install a launcher or individual Windows games, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net].

Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.|150px}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Bloodstained: Ritual of the Night
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* HI-Fi RUSH
* Hogwarts Legacy
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues

Not working yet:
* Among Us
* Company of Heroes 3
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

File:Game Porting Toolkit Steam icon.png

2023-06-08T23:13:43Z

Andytizer: Made by user Omsier.

== Summary ==
Made by user Omsier.

Game Porting Toolkit

2023-06-08T23:13:11Z

Andytizer:

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

===Wine prefix ===
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.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

Now you are ready to install a launcher or individual Windows games, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net].

Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
{{Image|Game Porting Toolkit Steam icon.png|Made by user Omsier.}}
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Bloodstained: Ritual of the Night
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* HI-Fi RUSH
* Hogwarts Legacy
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues

Not working yet:
* Among Us
* Company of Heroes 3
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-08T22:21:15Z

Andytizer: /* Toolkit install instructions */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it. *If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

===Wine prefix ===
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.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

Now you are ready to install a launcher or individual Windows games, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net].

Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Bloodstained: Ritual of the Night
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* HI-Fi RUSH
* Hogwarts Legacy
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues

Not working yet:
* Among Us
* Company of Heroes 3
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-08T22:01:53Z

Andytizer: /* Troubleshooting */

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
**If you have an old version Xcode installed, remove it.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

===Wine prefix ===
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.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

Now you are ready to install a launcher or individual Windows games, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net].

Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then login, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, most users should upgrade to macOS Sonoma. You can use the CrossOver workaround to login to Steam but you'll experience constant crashing.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Bloodstained: Ritual of the Night
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* HI-Fi RUSH
* Hogwarts Legacy
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues

Not working yet:
* Among Us
* Company of Heroes 3
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-08T21:59:39Z

Andytizer: Apple internally refers to this as GPT

{{Image|Game Porting Toolkit.png|Released 6th June, 2023 at WWDC23.}}

Game Porting Toolkit is Apple's new translation layer released on 6th June, 2023. Game Porting Toolkit ('''GPT''') combines Wine with Apple's own D3DMetal which supports DirectX 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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. A lot more games work using GPTK, however, games that use anti-cheat or aggressive DRMs generally don't work, along with games that require AVX/AVX 2, e.g. The Last of Us Part I.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
**If you have an old version Xcode installed, remove it.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
Note: if you have ever installed Homebrew before, then it is advised 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>. 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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both ARM64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both ARM64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

===Wine prefix ===
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.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

Now you are ready to install a launcher or individual Windows games, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net].

Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application\ Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
{{Image|GPTK Steam black screen.png|Steam login black screen issue.}}
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, upgrade to macOS Sonoma.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Bloodstained: Ritual of the Night
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)
* Crysis Remastered
* Cuphead
* Cyberpunk 2077
* Deep Rock Galactic
* Deceive Inc. - works well if launched without EAC
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Dyson Sphere Program (some objects and main character weren't visible before)
* Elden Ring
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Going Medieval
* Guilty Gear Strive
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility) [https://www.reddit.com/r/macgaming/comments/143zoos/halo_3_mcc_no_online_eac_m1_pro_game_porting/]
* HI-Fi RUSH
* Hogwarts Legacy
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Metal Gear Solid V: The Phantom Pain
* Overwatch 2
* QUBE 2
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Scarlet Nexus
* Sonic Omens
* Sonic P-06
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* SpongeBob SquarePants: The Cosmic Shake
* StarCraft: Remastered - Game runs fine but opening Option menu the second time will cause game not recognizing any inputs.
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''

Not working well:
* Horizon Zero Dawn - slowdown issues

Not working yet:
* Among Us
* Company of Heroes 3
* F1 22 - Crash on launch ( "Exception": "C0000005 EXCEPTION_ACCESS_VIOLATION at 0000000141bd8687")
* Halo Infinite - Crash on launch
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Microsoft Flight Simulator 2020 (Steam) - Crash on launch
* Monster Hunter Rise - DX12 Game, it launches but window goes dark after compiling shaders.
* Monster Hunter World - Black Screen on Launch
* Red Dead Redemption 2
* Rogue Company - anti-cheat conflict.
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Killing Floor 1 - Crash on launch
** Left 4 Dead 2 - Black screen -> crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch
** Sonic Mania - Crash on launch
** StarCraft II -> "Failed to initialize DirectX" error
** Battlefield 2 - DirectX installation failed, won't launch, see the [https://gist.github.com/chrismwendt/1d01a306cdc8618a06bdfb555743e25c error log]

{{References}}

Game Porting Toolkit

2023-06-08T20:04:39Z

Andytizer: /* Toolkit install instructions */

Game Porting Toolkit

2023-06-08T18:50:46Z

Andytizer:

Game Porting Toolkit

2023-06-08T15:57:11Z

Andytizer: References

Game Porting Toolkit

2023-06-08T14:02:40Z

Andytizer: /* Troubleshooting */

File:GPTK Steam black screen.png

2023-06-08T14:02:13Z

Andytizer:

Game Porting Toolkit

2023-06-08T14:01:18Z

Andytizer:

Game Porting Toolkit

2023-06-08T14:00:26Z

Andytizer:

Game Porting Toolkit

2023-06-08T13:59:46Z

Andytizer: Image

{{Image|Game Porting Toolkit.png}}

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 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
**If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both arm64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both arm64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

===Wine prefix ===
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.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

Now you are ready to install a launcher or individual Windows games, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net].

Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, upgrade to macOS Sonoma.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility)
* Cyberpunk 2077
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Elden Ring
* Overwatch 2
* SpongeBob SquarePants: The Cosmic Shake
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Hogwarts Legacy
* Deep Rock Galactic
* Sonic Omens
* Sonic P-06
* Scarlet Nexus
* Metal Gear Solid V: The Phantom Pain
* Dyson Sphere Program (some objects and main character weren't visible before)
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* HI-Fi RUSH
* QUBE 2
* Deceive Inc. - works well if launched without EAC
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Crysis Remastered
* Cuphead
* Bloodstained: Ritual of the Night
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)

Not working well:
* Horizon Zero Dawn - slowdown issues

Not working yet:
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot be completed.
* Red Dead Redemption 2
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Among Us
* Splitgate - anti-cheat conflict.
* Rogue Company - anti-cheat conflict.
* Tiny Tina's Wonderlands - Intro videos play, dragon animation indicating shader precompilation starts, game freezes, eventually crashes.
* Halo Infinite - Crash on launch
* Street Fighter 6 - Crash on launch
* Company of Heroes 3
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Left 4 Dead 2 - Black screen -> crash on launch
** Killing Floor 1 - Crash on launch
** Sonic Mania - Crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch

File:Game Porting Toolkit.png

2023-06-08T13:59:25Z

Andytizer: Taken from https://developer.apple.com/videos/play/wwdc2023/10123

== Summary ==
Taken from https://developer.apple.com/videos/play/wwdc2023/10123

Game Porting Toolkit

2023-06-08T13:58:54Z

Andytizer:

{{Image|Game Porting Toolkit.png|}}

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 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
**If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both arm64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both arm64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

===Wine prefix ===
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.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

Now you are ready to install a launcher or individual Windows games, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net].

Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, upgrade to macOS Sonoma.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* Halo 3 (MCC - No Online due to Easy Anti-Cheat Compatibility)
* Cyberpunk 2077
* Final Fantasy VII Remake Intergrade (~50 FPS on High settings at 1080p with M1 Pro)
* God of War (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* Elden Ring
* Overwatch 2
* SpongeBob SquarePants: The Cosmic Shake
* Diablo IV [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* Hogwarts Legacy
* Deep Rock Galactic
* Sonic Omens
* Sonic P-06
* Scarlet Nexus
* Metal Gear Solid V: The Phantom Pain
* Dyson Sphere Program (some objects and main character weren't visible before)
* Derail Valley (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* Spider-Man (2018)
* Spider-Man Miles Morales - ''requires Windows ver fix''
* Warframe - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* HI-Fi RUSH
* QUBE 2
* Deceive Inc. - works well if launched without EAC
* Risk of Rain 2 (does not require `-disable-gpu-skinning` like Crossover 22)
* Crysis Remastered
* Cuphead
* Bloodstained: Ritual of the Night
* Tetris Effect: Connected - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* Hatsune Miku: Project DIVA Mega Mix+ - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)
* Kena: Bridge of Spirits
* Control (DX12 mode, if downloaded from Heroic, needs to be ran by Terminal)

Not working well:
* Horizon Zero Dawn - slowdown issues

Not working yet:
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot be completed.
* Red Dead Redemption 2
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Among Us
* Splitgate - anti-cheat conflict.
* Rogue Company - anti-cheat conflict.
* Tiny Tina's Wonderlands - Intro videos play, dragon animation indicating shader precompilation starts, game freezes, eventually crashes.
* Halo Infinite - Crash on launch
* Street Fighter 6 - Crash on launch
* Company of Heroes 3
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Left 4 Dead 2 - Black screen -> crash on launch
** Killing Floor 1 - Crash on launch
** Sonic Mania - Crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch

Game Porting Toolkit

2023-06-08T12:32:14Z

Andytizer: /* Game compatibility list */

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 11 and 12<ref>{{Refurl|url=https://mastodon.gamedev.place/@gavkar/110501451404624870|title=Gokhan Avkarogullari: "@yiningkarlli @aras @romainguy…" - Gamedev Mastodon}}</ref>. 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.

== Toolkit install instructions ==
=== Requirements ===
*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].
*macOS Ventura causes large numbers of issues with steamwebhelper.exe crashing so it isn't recommended, use the macOS Sonoma beta.
*Visit [https://developer.apple.com/downloads Apple Developer Downloads site], these files are now free to download use for any logged in Apple account.
**Search for Command Line Tools for Xcode 15 beta and download the dmg file, then install it.
**If you have an old version Xcode installed, remove it.
**Search for Game Porting Toolkit and download it. Open the dmg file and then run the pkg.

=== Homebrew ===
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.

Open Terminal (search in Spotlight on macOS).

Install Rosetta:
<pre>softwareupdate --install-rosetta</pre>

Enter an x86_64 shell to continue the following steps in a Rosetta environment. All subsequent commands should be run within this shell.
<pre>arch -x86_64 zsh</pre>

Install the x86_64 version of Homebrew if you don't already have it.
<pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre>

Make sure the brew command is on your path:
<pre>which brew</pre>

If this command does not print <code>/usr/local/bin/brew</code>, you should use this command:
<pre>export PATH=/usr/local/bin:${PATH}</pre>

{{Fixbox|description=Optionally retain both arm64 and x86 versions of Brew|ref=|collapsed=yes|fix=
(Optional) If you want to have both arm64 and x86 versions of Brew installed, begin by editing your <code>.zshrc</code> file:
<pre>nano ~/.zshrc</pre>

Scroll down (by using the arrow keys or Control + V) to the bottom of the file, and paste the following script:
<pre>
if [ "$(arch)" = "arm64" ]; then
eval "$(/opt/homebrew/bin/brew shellenv)"
else
eval "$(/usr/local/bin/brew shellenv)"
fi
</pre>

You may now restart your terminal and use the following command to return to an x86_64 shell:
<pre>arch -x86_64 zsh</pre>
Your shell will now select the right installation of Brew, depending on your architecture.
}}

=== Build ===
Run this command to download Apple tap:
<pre>brew tap apple/apple http://github.com/apple/homebrew-apple</pre>

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.
<pre>brew -v install apple/apple/game-porting-toolkit</pre>

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.'''
<pre>brew update brew -v install apple/apple/game-porting-toolkit</pre>

===Wine prefix ===
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.
<pre>WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to Windows 10.
*Choose Apply and then OK to exit winecfg.

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.

=== Preparing the toolkit ===
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.
<pre>ditto /Volumes/Game\ Porting\ Toolkit-1.0/lib/ `brew --prefix game-porting-toolkit`/lib/</pre>

Put the 3 scripts from the Game Porting Toolkit DMG into here <code>/usr/local/bin</code> using this command:
<pre>cp /Volumes/Game\ Porting\ Toolkit*/gameportingtoolkit* /usr/local/bin</pre>

Now you are ready to install a launcher or individual Windows games, see below.

== Steam ==
Download the [https://cdn.cloudflare.steamstatic.com/client/installer/SteamSetup.exe Windows version of Steam] and place in your Downloads folder.

'''Install Steam'''
<pre>gameportingtoolkit ~/my-game-prefix ~/Downloads/SteamSetup.exe</pre>

'''Run Steam'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)/Steam/steam.exe'</pre>

'''Log into Steam'''

A common issue is that Steam will present with a blank black window.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

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.

== Battle.net ==
Download the [https://download.battle.net/en-gb/?platform=windows Windows version of Battle.net].

Make a new Wineprefix for Battle.net - we will refer to this as battle-net from now:
<pre>WINEPREFIX=~/battle-net `brew --prefix game-porting-toolkit`/bin/wine64 winecfg</pre>
*A “Wine configuration” window should appear on your screen.
*Change the version of Windows to <code>Windows 10</code>.
*Choose Apply and then OK to exit winecfg.

'''Run Battle.net launcher'''
<pre>gameportingtoolkit ~/battle-net ~/Downloads/Battle.net-Setup.exe</pre>

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.

Start individual game without the launcher using this command:
<pre>arch -x86_64 gameportingtoolkit-no-hud ~/battle-net 'C:\Program Files (x86)\Diablo IV\Diablo IV Launcher.exe'</pre>

== Epic and GOG.com support ==
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.

* Install the [https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases native macOS Heroic Games Launcher] or from Homebrew.
* Open Heroic, and log into your Epic Games and/or GOG.com account.
* 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.
** At the time of writing this, the newest numbered version of Wine-Crossover is <code>Wine-Crossover-Wine-22.1.0</code>
* Press the folder icon that appears after installing it to open the directory containing Heroic's Wine installations.
* Right-click on the version of Wine you just installed and press "Show Package Contents".
* Open this directory in the Terminal.
** If you have "OpenInTerminal" this is one button, otherwise press "Show Path Bar" and navigate where it says with "cd".
** It should be something like <code>cd ~/Library/Application Support/heroic/tools/wine/Wine-crossover-wine-22.1.0</code>.
* <pre>cd Contents/MacOS</pre>
* Remove the existing Wine: <pre>rm wine</pre>
* Create a symlink to Game Porting Toolkit's Wine:
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit`/bin/wine64 wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine/bin/wine64 wine</pre>
* <pre>cd ../Resources</pre>
* Remove the existing Wine: <pre>rm -rfv wine</pre>
* Create a symlink to Game Porting Toolkit's Wine
** If using Game Porting Toolkit Wineprefix: <pre>ln -s `/usr/local/bin/brew --prefix game-porting-toolkit` wine</pre>
** If using Whisky: <pre>ln -s /Applications/Whisky.app/Contents/Resources/Libraries/Wine wine</pre>
* We are now done with Terminal. Install any games you want to try playing.
* Select the game you want to play, and press the settings button in the top-right.
* Make sure the version of Wine you just downloaded and modified is selected.
* 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>.
* 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>
* Close the settings and try running the game.

== Commands ==
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.

'''A. Standard launching'''
<pre>gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

This launches the given Windows game binary with a visible extended Metal Performance HUD and filters logging to output from the Game Porting Toolkit.

'''B. Launching without a HUD'''
<pre>gameportingtoolkit-no-hud ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

'''C. Launching with Wine ESYNC disabled'''
<pre>gameportingtoolkit-no-esync ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'</pre>

To enter Winecfg:
<pre>gameportingtoolkit ~/my-game-prefix winecfg</pre>

== Shortcut ==
You can make a shortcut for Steam for example by using macOS built-in Automator app.
*Open Automator.
*Select New Application.
*In the 2nd column select Run Shell Script.
*Copy and paste this code into the box:
<pre>
#!/bin/zsh

export PATH="/usr/local/bin:${PATH}"

arch -x86_64 gameportingtoolkit ~/my-game-prefix 'C:\Program Files (x86)\Steam\steam.exe'
</pre>
*Save the shortcut somewhere e.g. Applications.
*Above shortcut can be customised to any Wineprefix or game.
*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.

== Logging ==
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.

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.

== Troubleshooting ==
'''Steam login black screen'''

Close the Terminal window and then reopen and retry the command, repeat several times.

Alternate way of launching Steam (after installing):
<pre>
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'
</pre>

If still not working then try using [[CrossOver]] and create a Steam bottle, then redirect this WINEPREFIX to that bottle:
<pre>
WINEPREFIX="/Users/[username]/Library/Application Support/CrossOver/Bottles/Steam/"
</pre>

'''Steam crashes straight after opening'''

Disconnect any external monitors.

'''Battle.net launcher won't re-launch'''

Re-install the launcher to reopen, no other fix at the moment.

'''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.
<pre>
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
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
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wineserver -k
</pre>

'''steamwebhelper.exe crashes'''

This is caused by Steam being run through macOS Ventura or below, upgrade to macOS Sonoma.

'''My game won't run and crashes with an invalid instruction'''

AVX and AVX2 games are not supported by Apple's arm64 chipset.

'''My game won't run because its anti-cheat or DRM software is incompatible with Wine translation.'''

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.

'''My game won’t run because it requires Mono, .NET, or the MSVCRT runtime.'''

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:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 <some-installer.exe>
</pre>

And .MSI packages can be installed by launching the Windows uninstaller application and choosing to install a downloaded .msi package:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 uninstaller
</pre>

'''Controller issues'''

Issues may be fixed by enrolling into the Steam beta.

'''My game looks pixelated and the display resolution is limited'''

Enable Retina (high resolution) mode:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'Y' /f
</pre>
Some games will not run with Retina mode enabled. To disable it:
<pre>
WINEPREFIX=~/my-game-prefix `brew --prefix game-porting-toolkit`/bin/wine64 reg add 'HKEY_CURRENT_USER\Software\Wine\Mac Driver' /v RetinaMode /t REG_SZ /d 'N' /f
</pre>

== Game compatibility list ==
Working games:
* [[Halo 3]] (MCC - No Online due to Easy Anti-Cheat Compatibility)
* [[Cyberpunk 2077]]
* [[Final Fantasy VII: Remake Intergrade]] (~50 FPS on High settings at 1080p with M1 Pro)
* [[God of War]] (Works somewhat well on M1 Pro (16gb), wouldn't recommend lesser hardware.)
* [[Elden Ring]]
* [[SpongeBob SquarePants: The Cosmic Shake]]
* [[Diablo IV]] [https://www.reddit.com/r/macgaming/comments/14307be/comment/jn7dxzo/?utm_source=reddit&utm_medium=web2x&context=3 ]
* [[Hogwarts Legacy]]
* [[Deep Rock Galactic]]
* [[Sonic Omens]]
* [[Sonic P-06]]
* [[Scarlet Nexus]]
* [[Metal Gear Solid V: The Phantom Pain]]
* [[Dyson Sphere Program]] (some objects and main character weren't visible before)
* [[Derail Valley]] (awesome performance, no missing manuals - in-game objects for train operation - like on CrossOver)
* [[Marvel's Spider-Man Remastered]]
* [[Marvel's Spider-Man: Miles Morales]] - ''requires Windows ver fix''
* [[Warframe]] - ''To get installer/launcher working add dwrite (disabled) to library overrides in winecfg''
* [[Hi-Fi RUSH]]
* [[QUBE 2]]
* [[Deceive Inc.]] - works well if launched without EAC
* [[Risk of Rain 2]] (does not require `-disable-gpu-skinning` like Crossover 22)
* [[Crysis Remastered]]
* [[Cuphead]]
* [[Bloodstained: Ritual of the Night]]
* [[Tetris Effect: Connected]] - Game window likes to be uncooperative; really doesn't like retina mode, works otherwise
* [[Hatsune Miku: Project DIVA Mega Mix+]] - works with Retina mode; DivaModLoader and DivaNoSpy recommended; run Steam with WINEDEBUG=-all WINEESYNC=0 WINEDLLOVERRIDES="dinput8.dll=n,b"; may randomly crash at the title screen (just restart and try again until it works)

Not working well:
* [[Horizon Zero Dawn]] - slowdown issues

Not working yet:
* Sea of Thieves - Launches, but the prompt to sign into an xbox live account appears blank and cannot be completed.
* Red Dead Redemption 2
* Hitman 3 - launcher works, crash at 0x0000014136dddd hitman3+0x136dddd: int $3
* Among Us
* Tiny Tina's Wonderlands - Intro videos play, dragon animation indicating shader precompilation starts, game freezes, eventually crashes.
* Halo Infinite - Crash on launch
* Street Fighter 6 - Crash on launch
* Company of Heroes 3
* Many (all?) DX9 games
** 30XX - "Failed to create D3D device" -> crash on launch; this is a rare 64-bit DX9 game
** Left 4 Dead 2 - Black screen -> crash on launch
** Killing Floor 1 - Crash on launch
** Sonic Mania - Crash on launch
** Mega Man Zero/ZX Legacy Collection - "Failed to create d3d9 device" -> crash on launch