Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

YellowBastle

2
Posts
A member registered 13 days ago

Recent community posts

Hey, thanks for reaching out. I’m happy to provide Unity logs and test experimental builds. 


Feel free to reach me on Discord, my user is Ledesmutt

Mac user here. I’ve been troubleshooting this game using both Whisky and CrossOver. I’m not a developer, but I’ve been analyzing Unity logs and known Wine/macOS limitations to figure out what’s happening.

The issue appears to be related to Unity 6’s rendering pipeline. Even when forcing DX11 using:

-force-d3d11 -force-d3d11-no-singlethreaded

Unity still initializes DirectX 12 internally before falling back to DX11:

[D3D12 Device Filter] Feature Level: 12.2

The DX11 fallback partially succeeds:

Direct3D 11.0 [level 11.1] Renderer: AMD Compatibility Mode

However, the game then fails due to missing DX11 features not implemented in Wine’s D3D11 → Metal layer:

GpuFence::Create(): Failed to create ID3D11Fence Dedicated video D3D11 device multithread protection failed

Unity 6 requires ID3D11Fence, and this is treated as a fatal error, causing the crash. This is a known limitation on macOS using Wine/Metal and does not appear to be fixable via launch arguments or render backend toggles.

Possible ways this could work in the future would be:

Building with Unity 2022 or earlier

Providing a Vulkan backend

Providing a Metal backend

Allowing a DX11 fallback without fence requirements

Native macOS support

Just wanted to share this so other Mac users don’t spend hours troubleshooting, and in case it’s useful info for the dev. Totally understand if macOS support isn’t a priority — thanks for the game regardless.