Elden Ring + Seamless Co-op / ERSC
Gold
Steam prefix
ModEngine 2
Randomizer
No esync
Tested with an already-installed Windows game folder copied to the Mac games drive. Steam must be running in the same prefix so ERSC can see Steam API state and Spacewar/AppID 480.
Why this profile existsERSC, Steam networking, ModEngine, and Randomizer need repeatable DLL overrides and a stable prefix.
How it launchesSteam starts first, then ERSC or ModEngine launches from the Elden Ring profile with native winmm and steam_api64.
Known fixesUse the no-capture DirectSound runner and no-esync path for Golden Pot stability.
Read the full Elden Ring ERSC setup, Golden Pot esync fix, and Steam voice capture report.
Clair Obscur: Expedition 33
Playable
AVX
No DXR
MetalFX/DLSS bridge
Tested through GPTK with AVX and D3D12 flags. A Wine C++ runtime assertion can appear from winegstreamer/colorconvert.c; ignoring it allowed the cutscene and game to continue in the tested setup.
Why this profile existsThe game is graphically heavy and sensitive to renderer and driver checks.
How it launchesUse the profile's AVX/no-DXR launch path and enable the game's own upscaling options from in-game settings.
TroubleshootingIf a NVIDIA driver prompt appears, it is the Windows game seeing a compatibility-reported GPU. On Apple Silicon, do not install NVIDIA drivers.
See Clair Obscur DLSS and MetalFX notes.
God of War Ragnarök
Partial
PSPC runtime
GameInput stub
MetalFX
Tested with the PlayStation PC runtime installer run inside the game prefix. Launch work focused on the missing runtime path, GameInput/API stubs, and D3D12 behavior under GPTK.
Why this profile existsThe game has extra PlayStation PC runtime expectations that a basic Wine prefix does not provide.
How it launchesInstall the PSPC runtime first, then launch the game executable with the profile-specific compatibility flags.
TroubleshootingIf it exits early, check logs for missing API/runtime messages before changing graphics flags.
See God of War Ragnarök launch notes.
Steam For Windows
Dependency
Library app
Web runtime sensitive
Steam is both a standalone app profile and a dependency for games that need Steam APIs. Downloads, Steam Web Runtime updates, Spacewar/AppID 480 setup, and Steam-managed games should stay in the Steam prefix.
Why this profile existsMany Windows games check Steam state even when their game files are copied locally.
How it launchesStart Steam from the library, or use Install Spacewar once when a co-op workflow needs AppID 480 initialized.
TroubleshootingFor webhelper or content unavailable issues, repair Steam compatibility and check the Steam logs.
See Steam setup and Steam troubleshooting.
Planned: REFramework / RE Engine Games
Planned
D3D12Hook
D3DMetal research
Tester reports needed
REFramework support is not currently marked tested. It is on the roadmap as a dedicated compatibility track because REFramework's D3D12 hooks can run into Wine/D3DMetal-specific behavior.
Why this profile would existResident Evil / RE Engine games need repeatable REFramework file placement, DLL overrides, and launch logs.
Next stepCollect game version, REFramework build, runner, launch flags, and restart behavior from testers.
See the REFramework support plan.