The Miskatonic (870290)

Compatibility Report

The Miskatonic
870290

System Information

• GPU: RX Vega 56
• Driver/LLVM version: Mesa 19.3.4
• Kernel version: 5.5.6-xanmod4-1-xanmod
• Link to [Gist] : https://gist.github.com/speakn2pabst/4146144514d1e970adb61438ec8a67a9
• Proton version: 5.0-3

I confirm:

• [ x] that I haven't found an existing compatibility report for this game.
• [ x] that I have checked whether there are updates for my system available.

This is a proton log before the fix described below is applied.

steam-870290.log

Symptoms

Game installs but upon launch a black window is formed but displaying no content. The music eventually begins and the cursor is appropriately changed within the window space but only an empty black screen is shown.

Reproduction

Launch the game.

Solution

I was able to find a fix. The game installs with a version of libGLESv2.dll in the base installation directory. You want to ignore it and use the builtin version that ships with Proton. To do this you must run winecfg for this prefix and then go to the library tab. Once there add a new override rule for libglesv2.dll . After adding the rule edit libglesv2.dll override to "builtin (Wine)". Then hit OK closing winecfg. Your done! Just start the game normally now.

(I copy pasted this from ProtonDB but I'm the original author who posted there.)

I haven't completed a full playthrough yet but have played about an hour and tested loading and saving and closing the window (there is no "quit/exit" in the menu) and all work as expected.

The only small issue has to do with swapping from fullscreen and windowed. Pressing the "f" keyboard key switches from full screen to windowed, but after each change it is required to left click the window once to bring it to focus. After doing so everything works fine and also allows you to switch back to either fullscreen or windowed another time.

Thanks for your time.

This is a compatibility report for The Miskatonic on Proton 5.0-3, with a linked Proton log and a reported libglesv2.dll override workaround. Start by reviewing the attached log and the reported reproduction steps. No source file, test, or requested code change is identified, so completion criteria are not defined.