Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

Dr.Muramasa kind of answered this last week for both Linux and Mac emulation - "That issue is because of some changes unity has done to their platform. Some things to try and fix it has been done but those are not a 100% guaranteed fix"

The 1.8A version code is 6000.0.59f2 the game has been updated to Unity 6 (released in late 2025). This update is the primary cause of the current compatibility issues with KegWorks and other Wine-based wrappers on macOS.

Googling finds some suggestions, though maybe best waiting for 1.8B and keeping in mind Windows is the only official supported platform at the moment:

Why it isn't working

  • Input Bug: There is a documented "input bug" in recent Unity versions (including Unity 6) that specifically affects macOS users, causing the game to stop picking up keyboard or mouse commands shortly after launch.
  • Unity 6 Requirements: Unity 6 builds (6000.x) have stricter requirements for DirectX 12 and Vulkan. Older KegWorks engines may not support the necessary translation layers for these newer engine features.
  • KegWorks Obsolescence: KegWorks development has slowed down, and many users have migrated to Sikarugir or CrossOver for better support of the latest Unity 6 features on Apple Silicon. 

Recommended Solutions

  1. Update the Engine: In KegWorks Winery, you must use at least WS12WineCX24.0.7 or higher. Unity 6 games generally require the latest Crossover-based (CX) engines to handle the updated graphics calls.
  2. Toggle DXVK: Ensure DXVK is enabled in your bottle settings. Unity 6 heavily relies on modern Vulkan features that require this layer to function on macOS.
  3. Switch to Sikarugir: If KegWorks continues to crash, move your game files to Sikarugir. It is the direct successor to KegWorks and includes specific fixes for Unity 6 compatibility on macOS.
  4. Use Windowed Mode: If the game launches but freezes, try adding -window-mode exclusive or -screen-fullscreen 0 to the launch flags in your wrapper settings to bypass common Unity 6 display initialization errors.