Support for macOS

[Bobík]

Hi, will you support Mac? I played KCD 1 on an MacBook Air M2 in a Wine and it works well from performance point of view, it just is sometimes unstable.

It is sad this platform is ignored, because current Apple Silicon is a beast, especially GPU.

[Sima | Marco]

Hi, its the same engine, so chances are high. Mac support maybe a future goal, but the playerbase is not that really big at the moment.

[Acheg1l]

will give it a try on my M4 Pro in a few hours under Crossover with DX12. I am very confident that the fps will be good.

[Acheg1l]

had the chance to test it right now (no need to wait a few hours). hm well bad luck so far:

[CCommandListFenceSet] WaitForFence(CPU) TIMED OUT: [2, 0, 0] (CurrentValues=[2, 0, 0], Return value: 102)

[Martinta]

Originally posted by Acheg1l:

hm well bad luck so far:

[CCommandListFenceSet] WaitForFence(CPU) TIMED OUT: [2, 0, 0] (CurrentValues=[2, 0, 0], Return value: 102)

To be fair, you did say "in a few hours" and posted this reply 32 minutes later. A few more hours and it might work

[digeridoo]

crosses fingers

[akurate]

Originally posted by Acheg1l:

hm well bad luck so far:

[CCommandListFenceSet] WaitForFence(CPU) TIMED OUT: [2, 0, 0] (CurrentValues=[2, 0, 0], Return value: 102)

Please write here when you have more information. Many of us want to play on MacOS.

Thanks in advance!!!

[SaoiAebi]

yeah same... but so far i only read from one guy who couldn't make the game start... :/

[LordFlinx]

Same issue on a MacMini Pro with M2 chip , using parallels 20.2.0 and MacOS 15.3 - I tested some solutions from the KCD1 game, but so far notthing seems to work. Still looking for a solution.

[Nickk8]

Originally posted by Acheg1l:

hm well bad luck so far:

[CCommandListFenceSet] WaitForFence(CPU) TIMED OUT: [2, 0, 0] (CurrentValues=[2, 0, 0], Return value: 102)

in the kcd.log file I have the same issue as posted by you.
My setup:
- Mac mini M4 pro, 24GB Ram, MacOS 15.3
- Whisky Version 2.3.4 (42)
- Bottle Config:
- Windows Version: Windows 10

some more data from the log file, maybe this is some help for any of you, to come up with ideas on how to get it working:

"
...
...
Loading base cfg files...
Loading config file 'system.cfg' (system.cfg)
Loading config file 'pc.cfg' (engine\config\pc.cfg)
Loading user cfg files...
CVar sys_PakPriority value is 2
Physics initialization
Initializing module CryPhysics ...
Initializing module CryPhysics done, MemUsage=9392Kb
<Localization> Languages available: japanese,english,french,spanish,german,italian,portuguese,russian,korean,chineset,chineses,polish,czech,turkish,ukrainian
<Localization> Audio languages available: german
Renderer initialization
Logging video adapters:
- AMD Compatibility Mode (vendor = 0x1002, device = 0x66af)
- Adapter index: 0
- Dedicated video memory: 16384 MB
- Feature level: D3D 12_1 (SM 6.0)
- Displays connected: yes
- Suitable rendering device: yes
Initializing module CryRenderD3D12 ...
Initializing module CryRenderD3D12 done, MemUsage=852Kb
Creating rendering device...
Rendering Debug Support
- Pix Captures: Disabled
- NVidia Aftermath: Disabled
- Debug Validation: Disabled
- GPU Based Validation: Disabled
- DRED: Disabled
Active GPUs: 1
[CCommandListFenceSet] WaitForFence(CPU) TIMED OUT: [2, 0, 0] (CurrentValues=[2, 0, 0], Return value: 102)"

The last line is repeated hundreds of times until I Force Quit the game.

[KookieBogey]

Aww I was so confident this would be playable thru translation on day 1 :(

[Alien4042x]

If you’re testing Kingdom Come: Deliverance II on macOS using Wine, CrossOver, or Game Porting Toolkit, please make sure to provide the Wine logs instead of just the game’s logs. The game’s logs only show what CryEngine sees, but we need to check if Wine or GPTK is handling DirectX 12 properly or if there’s an issue with translation to Vulkan/Metal.

To get useful logs, try running the game with these commands:

For Wine (or Whisky):

WINEDEBUG=+d3d12,+dxgi,+seh,+sync wine KCD2.exe > log.txt 2>&1

This will output all DirectX 12 and DXGI calls from Wine, which can help us understand if the issue is with translation or the game itself.

[Alien4042x]

Originally posted by Nickk8:

Originally posted by Acheg1l:

hm well bad luck so far:

[CCommandListFenceSet] WaitForFence(CPU) TIMED OUT: [2, 0, 0] (CurrentValues=[2, 0, 0], Return value: 102)

in the kcd.log file I have the same issue as posted by you.
My setup:
- Mac mini M4 pro, 24GB Ram, MacOS 15.3
- Whisky Version 2.3.4 (42)
- Bottle Config:
- Windows Version: Windows 10

some more data from the log file, maybe this is some help for any of you, to come up with ideas on how to get it working:

"
...
...
Loading base cfg files...
Loading config file 'system.cfg' (system.cfg)
Loading config file 'pc.cfg' (engine\config\pc.cfg)
Loading user cfg files...
CVar sys_PakPriority value is 2
Physics initialization
Initializing module CryPhysics ...
Initializing module CryPhysics done, MemUsage=9392Kb
<Localization> Languages available: japanese,english,french,spanish,german,italian,portuguese,russian,korean,chineset,chineses,polish,czech,turkish,ukrainian
<Localization> Audio languages available: german
Renderer initialization
Logging video adapters:
- AMD Compatibility Mode (vendor = 0x1002, device = 0x66af)
- Adapter index: 0
- Dedicated video memory: 16384 MB
- Feature level: D3D 12_1 (SM 6.0)
- Displays connected: yes
- Suitable rendering device: yes
Initializing module CryRenderD3D12 ...
Initializing module CryRenderD3D12 done, MemUsage=852Kb
Creating rendering device...
Rendering Debug Support
- Pix Captures: Disabled
- NVidia Aftermath: Disabled
- Debug Validation: Disabled
- GPU Based Validation: Disabled
- DRED: Disabled
Active GPUs: 1
[CCommandListFenceSet] WaitForFence(CPU) TIMED OUT: [2, 0, 0] (CurrentValues=[2, 0, 0], Return value: 102)"

The last line is repeated hundreds of times until I Force Quit the game.

We need wine log not from cryengine. 😉

[David 96 (CZ)]

Originally posted by Alien4042x:

If you’re testing Kingdom Come: Deliverance II on macOS using Wine, CrossOver, or Game Porting Toolkit, please make sure to provide the Wine logs instead of just the game’s logs. The game’s logs only show what CryEngine sees, but we need to check if Wine or GPTK is handling DirectX 12 properly or if there’s an issue with translation to Vulkan/Metal.

To get useful logs, try running the game with these commands:

For Wine (or Whisky):

WINEDEBUG=+d3d12,+dxgi,+seh,+sync wine KCD2.exe > log.txt 2>&1

This will output all DirectX 12 and DXGI calls from Wine, which can help us understand if the issue is with translation or the game itself.

Hi, I’m trying to run KCD2 on Silicon Mac through CrossOver facing the same issue with black screen after launch, where I’m being able to see only the custom cursor from the game. The only possible translation in CrossOver is D3DMetal (GPTK) because only this supports DirectX12 translation. Where do I find helpful logs when using CrossOver with D3DMetal graphics backend that I can post here? Is it the same way as the previously mentioned tutorial for Wine/Whisky? Thanks!

[Alien4042x]

Originally posted by David 96 (CZ):

Originally posted by Alien4042x:

If you’re testing Kingdom Come: Deliverance II on macOS using Wine, CrossOver, or Game Porting Toolkit, please make sure to provide the Wine logs instead of just the game’s logs. The game’s logs only show what CryEngine sees, but we need to check if Wine or GPTK is handling DirectX 12 properly or if there’s an issue with translation to Vulkan/Metal.

To get useful logs, try running the game with these commands:

For Wine (or Whisky):

WINEDEBUG=+d3d12,+dxgi,+seh,+sync wine KCD2.exe > log.txt 2>&1

This will output all DirectX 12 and DXGI calls from Wine, which can help us understand if the issue is with translation or the game itself.

Hi, I’m trying to run KCD2 on Silicon Mac through CrossOver facing the same issue with black screen after launch, where I’m being able to see only the custom cursor from the game. The only possible translation in CrossOver is D3DMetal (GPTK) because only this supports DirectX12 translation. Where do I find helpful logs when using CrossOver with D3DMetal graphics backend that I can post here? Is it the same way as the previously mentioned tutorial for Wine/Whisky? Thanks!

Ten report bude mít stejně kolem 6000 řádků. Já právě nemám teď zbytečný cash navíc nechce se mi do toho investovat jen tak. 😏 Musíš to spustit s příkazem. Najdi to na netu a pak hledat řádky jako “fixme” atd já takhle opravil SP do Grounded. Ale ne všechno jde. Záleží jak ta chyba bude kritická, a jestli tam bude chybět knihovna která bude potřeba speciální úpravu tak se můžeme rozloučit. To bych sám ani nedal. Ale ovladače to nejspíš nebudou co tak sleduji internet. Navíc tu chybu někdo obešel a stejně to spadlo takže proto sázím na to že to grafikou nebude. Klidně mi pak písni na steam až budeš mít ten report.

[David 96 (CZ)]

Originally posted by Alien4042x:

Originally posted by David 96 (CZ):

Hi, I’m trying to run KCD2 on Silicon Mac through CrossOver facing the same issue with black screen after launch, where I’m being able to see only the custom cursor from the game. The only possible translation in CrossOver is D3DMetal (GPTK) because only this supports DirectX12 translation. Where do I find helpful logs when using CrossOver with D3DMetal graphics backend that I can post here? Is it the same way as the previously mentioned tutorial for Wine/Whisky? Thanks!

Ten report bude mít stejně kolem 6000 řádků. Já právě nemám teď zbytečný cash navíc nechce se mi do toho investovat jen tak. 😏 Musíš to spustit s příkazem. Najdi to na netu a pak hledat řádky jako “fixme” atd já takhle opravil SP do Grounded. Ale ne všechno jde. Záleží jak ta chyba bude kritická, a jestli tam bude chybět knihovna která bude potřeba speciální úpravu tak se můžeme rozloučit. To bych sám ani nedal. Ale ovladače to nejspíš nebudou co tak sleduji internet. Navíc tu chybu někdo obešel a stejně to spadlo takže proto sázím na to že to grafikou nebude. Klidně mi pak písni na steam až budeš mít ten report.

Ahoj, tak se mi podařilo vytvořit log, který má ale 200MB čistýho textu, takže ho sem nevložím. :D Hodil jsem ho na Megu ke stažení: https://mega.nz/file/8bIXxK5I#k3WDZwCPIaddFZdk9eLepjFVD1pI6dRxdbcpKGYs2_w Log v podstatě nekonečně nabývá a načítání hry je v nekonečném loopu, kdy se po určitém čase v logu objeví nějaký timeout. (nechal jsem to asi 2 minuty na blackscreenu). Hru jsem nakonec vynuceně vypnul skrz Command+Esc+Option. Log je vytvořený přímo skrz CrossOver pomocí Spustit s možnostmi > Vytvořit log soubor > Wine záznamové kanály: +d3d12,+dxgi,+seh,+sync. Tak snad je to nějak pomůže vnést trochu světla do problému. :D