Inscryption

What works

The game loads, and the main menu and the options dialog are functional.

The first match in the demo is fully playable and can be completed.
With all workarounds applied, the demo is fully playable and can be completed.

What does not

The installer fails with an error message “File not found”. (See Workarounds section.)

If you use a package manager or if you extract the game files manually, the app directory may end up not writable by non-root users. In that case, you may be able to complete the first match of the demo but the game may hang immediately after that, i.e. at the precise moment the map is supposed to appear. Instead of showing the map, the game may then just keep showing the empty wooden floor indefinitely, with no option to continue the game. (See Workarounds section.)

If you run the game full screen and switch apps, the game freezes. That issue has been reported on MacOS hosts, and I can confirm that the same thing happens for me on Linux using Wayland. (See Workarounds section.)

Workarounds

1. The installer fails for me with an error message “File not found”.

   Workaround: Extract the content from the installer file, e.g. using innoextract. Then copy the files to any directory.

2. On the Linux version of Wine, you won’t hear any music or sound unless you have 32-bit sound drivers installed.

   Workaround: Figure out which audio subsystem your Linux installation uses (e.g. pulseaudio). Look up the package name under which your distribution gives you 32-bit sound drivers that match your subsystem. Then install that package on your Linux side.

3. Immediately after the first match, the game may appear unresponsive, showing just the empty wooden floor indefinitely, with no way to continue the game.

   Workaround: The game is trying, and failing, to save its state. Make sure the game directory is writable for the current user.

   Workaround for package authors: Consider an overlay filesystem so all the upstream game files can remain read-only. Alternatively, create a bunch of symbolic links (pointing to the game files) inside a user-writable directory in order to simulate an overlay filesystem.

4. The game freezes when I run it in full screen and then switch to another app.

   Workaround: Avoid app switching.

5. The display resolution seems wrong, and parts of the screen are cut off.

   Workaround: Try undoing all changes made to the game’s settings on the filesystem and in the registry. If all else fails, back up your SaveFile.gwsave and then re-install your Wine prefix. Temporarily disable any secondary monitors before starting the game. Avoid app switching while in the game, and stick with the default resolution the game detects for you.

6. The game isn’t centered in full screen mode.

   Workaround: Avoid app switching. Stick with the default resolution. If the damage is already done, try undoing all changes made to the game’s settings on the filesystem and in the registry. If all else fails, back up your SaveFile.gwsave and then re-install your Wine prefix.

What was not tested

I haven’t tested the game on X11 because I only have Wayland.

Hardware tested

Graphics:

• GPU: Intel
• Driver: unknown

Additional Comments