PEAK doesnt open

[MCJEModder2026]

Game name

PEAK

Store / launcher

Steam

Compatibility rating you'd give it

Doesn't launch — installer or launcher fails before game loads

What happens

When I attempt to launch it, loading window pops up for a bit, then a terminal that says winedbg or something, then it closes.

In previous version of whisky, PEAK opened but keyboard and mouse input did not work (controller worked fine though)

Steps you took

Tried launching peak with: DX12, DX11, Vulkan

Graphics backend tried

Recommended (auto)

GameDB entry id (if you applied one)

No response

Wine log (relevant excerpt)

Maybe this?
[mvk-info] Created VkInstance for Vulkan version 1.0.334, as requested by app, with the following 3 Vulkan extensions enabled:
	VK_KHR_external_memory_capabilities v1
	VK_KHR_external_semaphore_capabilities v1
	VK_KHR_get_physical_device_properties2 v2
00b4:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\winebth": c0000135

Whisky version

3.7.0

macOS version

Tahoe (macOS 26)

Hardware

m5 air 32gb

Anti-cheat

• This game uses an anti-cheat system (EasyAntiCheat, BattlEye, Vanguard, Denuvo, etc.) that I'm aware of.

Pre-flight checks

• I checked the in-app Game Configurations browser for an existing config.
• I'm running this fork (frankea/Whisky, confirmed via Whisky → About) — not the archived original that the default brew install --cask whisky installs.
• I searched existing issues for this game.
• My issue is written in English.

[niltonperimneto]

Same for me, except with version 4.0.0 beta 1 and I think beta 2 that worked flawlessly with even the keyboard and mouse input stoking

[niltonperimneto]

@MCJEModder2026 have you installed vcruntime2019 through the wine tricks on your bottle?

[MCJEModder2026]

@MCJEModder2026 have you installed vcruntime2019 through the wine tricks on your bottle?

Yes

[niltonperimneto]

It seems that when I installed vcruntime it crashes, however if a new bottle is created it loads without issue

[dappermint]

/duplicate #233

same mechanism: the bundled winetricks pulls a stale vc_redist, so a bottle that had vcrun2019 run through it crashes while a fresh bottle launches fine. tracking it in #233

[github-actions]

Duplicate of #233

[niltonperimneto]

I was further investigating the issue with PEAK using the latest build of Wine provided by @dappermint and this is what I could find:

First of all the game crashes after playing the start screen, but you can add this to be able to rum with DXMT or D3DMetal

-force-d3d11 -force-gfx-direct -screen-fullscreen 0 -screen-width 1280 -screen-height 720

The Game crashes with D3D12 because it seems that D3DMetal/GPTK4 does not implement D3D11on12, at least I could not find any reference to help me on which the Unity 6 Engine relies on to play on D3D12.

In the same Steam Properties window, make sure "Enable the Steam Overlay while in-game" is toggled OFF.

If it still crashes you should open regedit in your bottle and navigate to:
HKEY_CURRENT_USER\Software\LandCrab\PEAK and delete any entries starting with Screenmanager (especially Screenmanager Stereo 3D and Screenmanager Fullscreen mode).

---

What Needs to Be Upstreamed

For this to work smoothly out of the box without manual launch flags, patches are needed in a few projects:

1. Wine / WhiskyWine
   • Implement ID3D10Multithread / ID3D11Multithread on D3D11 devices (dlls/d3d11/device.c):
   Wine's D3D11 device should implement critical section locking for ID3D10Multithread (similar to what DXVK does). This allows multithreaded Unity games to safely run worker threads and background asset cleanup without crashing.
   • Add a proper D3D11On12CreateDevice translation stub:
   More modern games (especially Unity 6 and Unreal Engine 5.4+) are beginning to call D3D11On12CreateDevice. A functional shim that wraps D3D12 queues would allow these engines to boot in native DX12 mode.

2. Apple / Game Porting Toolkit (D3DMetal)
   • A bug report / feedback report should be submitted to Apple requesting D3D11On12 support in D3DMetal. GPTK 4 added Metal 4 support for DX12, but because Unity 6 games probe D3D11On12 before starting the DX12 pipeline, Unity 6 DX12 remains blocked on macOS until Apple provides that interface.

3. Whisky / GameDB
   • We can add a default GameDB profile for PEAK (AppID: 3527290) that automatically sets forceD3D11 = true, metal4Enabled = false, blockInjectedOverlays = true, and appends -force-gfx-direct so users don't need to manually configure Steam launch options.

If someone finds something different from me feel free to share it would be valuable

[dappermint]

thanks for digging into this. the crash after the start screen is a different bug from the one this issue was closed for (that one was the winetricks payload), so please open a new game-compatibility issue for it, with the wine log from a DX12 attempt attached. i will try to reproduce here too, but attach the log anyway since our setups differ.

on the two wine items:

wine's d3d11 already implements ID3D10Multithread, see dlls/d3d11/device.c. on the default backend the d3d11 in the bottle is D3DMetal's dll rather than wine's, so wine's copy is not in the path at all. i cannot check from source whether Apple's dll honours it.

no wine release ships d3d11on12.dll, so a missing D3D11On12CreateDevice would be a gap in every wine, not in D3DMetal. before anyone writes a shim, confirm that PEAK calls it. a run with WINEDEBUG=+loaddll that shows d3d11on12.dll being requested, or a crash log with it on the stack, would settle that. without one it is a guess, and unity's own D3D12 backend does not go through 11on12 as far as i know.

gamedb: happy to take an entry for 3527290. of the settings you listed, forceD3D11 is the only one the gamedb schema has. metal4Enabled is a bottle setting the gamedb cannot set yet, blockInjectedOverlays does not exist in whisky, and there is no launch-argument field, so -force-gfx-direct stays a steam launch option that the entry can only describe in its workaround text. does the game run with -force-d3d11 alone, or are -force-gfx-direct and the windowed flags also required? then i know how much the entry can fix on its own.

the keyboard and mouse problem from the first report is unity 6 calling EnableMouseInPointer, which the 3.1.1 engine stubs and wine 11.3 onward implements, so the newer runtime covers that one.

[dappermint]

reproduced on my side, and it does not crash here.

setup: the native mac steam client downloaded PEAK build 25090101 (v2.4.b) into a shared library folder, and i launched it through the compat tool lane on runtime 4.6.4 with the recommended backend, which is D3DMetal for both d3d11 and d3d12. no launch flags, no overlay, fresh prefs. it reached the airport lobby and ran until i quit it. the D3D12 answer is in unity.s own log:

[D3D12 Device Filter] Feature Level: 12.2
d3d12: could not load DirectML.dll.
d3d12: failed to create D3D11On12 device (0x887a0004).
GfxDevice: creating device client; kGfxThreadingModeClientWorkerJobs
Direct3D:
    Version:  Direct3D 11.0 [level 11.1]

you were right that unity 6 wants D3D11On12 during D3D12 init. apple's d3d11.dll exports it, as a six byte stub that returns DXGI_ERROR_UNSUPPORTED, and unity treats that as "no D3D12" and drops to D3D11 by itself. that is why -force-d3d11 changes nothing here: the game lands on D3D11 either way. unityplayer.dll takes D3D11On12CreateDevice as a static import from d3d11.dll, so a shim would have to live inside apple's d3d11 and wrap a D3DMetal d3d12 device. wine's own d3d11 is not in the path and could not do it if it were.

the multithread point is real too, and also not a crash: Dedicated video D3D11 device multithread protection failed (error: 0x80004002). Will use software video decoding. apple's d3d11 does not expose ID3D10Multithread, and unity falls back to software video decode.

i could not reproduce the crash after the start screen. differences from your setup that i can see: no steam overlay in my lane, a bottle that never had the stale vcrun2019 payload, and default Screenmanager prefs. if a fresh bottle with the overlay off still crashes for you, please open a new issue with the Player.log from AppData\LocalLow\LandCrab\PEAK and the crash folder from AppData\Local\Temp\LandCrab\PEAK\Crashes. with what i have, a gamedb entry would carry notes only, no settings are needed.

[niltonperimneto]

@dappermint Thank you for digging into this and confirming the behavior on your end!

I spun up a completely fresh Windows 10 bottle, disabled the Steam Overlay, and avoided any Winetricks payloads like vcrun2019. You were exactly right—the game booted flawlessly. My Player.log perfectly matches yours: Unity hits the D3DMetal 0x887a0004 stub, gracefully drops to D3D11, hits the multithread protection warning, cleanly shifts to software video decoding, and continues straight into the lobby without issue. The crashes I was seeing earlier were definitely environmental contamination in my old bottle.