We don't have extensive tests with Cinnamon.
Our Launcher and game officially supports, and has been fully tested in the following linux distos;
- Ubuntu
- Debian
- CatchOs
- Fedora
- ArchLinux
If you want, you can go to the Launcher settings, and play with some options there to see if some of them, make the game playable on Cinnamon Linux Distros.
If you find out a solution to make it playable on your Distro, please share it here what you did, and we may give official support for Mint Cinnamon in a next Linux Launcher update.
Linux support are very community driven since there's thousands of different distros.
Problem
The launcher fails to start the game correctly when the default Wine prefix already exists with a different architecture from the one requested by the launcher.
Evidence
The bundled installer sets WINEARCH_DEFAULT="win64" and uses ~/.wine-dbo as its default prefix. However, when that directory already exists, the installer logs that it is keeping the existing prefix rather than validating its architecture.
The existing prefix contains registry files marked #arch=win32. The launcher subsequently attempts to use a 64-bit Wine configuration with this 32-bit prefix, producing the error:
wine: WINEARCH set to win64 but '/home/user/.wine-dbo' is a 32-bit installation.
The installer then reports that its setup has exited with code 1.
Testing with a separate 64-bit prefix allowed the game executable to be invoked, but it subsequently crashed with a BREAKPOINT exception. This may represent an additional issue and has not yet been diagnosed.
Expected behaviour
Before using an existing Wine prefix, the launcher should detect its actual architecture and compare it with the architecture required by the game and its runtime.
If the architectures differ, the launcher should report the mismatch clearly and offer a safe way to select or configure a compatible prefix. It should not silently retain an incompatible prefix and continue with conflicting architecture settings.
Additional investigation requested
Please confirm whether the launcher explicitly detects the architecture of existing prefixes and whether its game-launching and runtime-installation components use the same prefix configuration.
Impact
The launcher can fail during runtime setup because the existing prefix does not match the requested architecture. Users may be left with a launcher that opens normally but does not successfully start the game.
I had to manually direct the launcher to the 64bit wine prefix.
Credits
