Right on, you're very welcome. :)

Thanks for your help on this headkase.194 I also was not able to run the game but the Visual Studio C++ 2015 runtimes, 64-bit version fixed it.

You're welcome too. :)

Thanks for your hint, this solved my issue! I installed the game from the offline installer via Lutris and had the same problem with the black screen.

In Lutris, I selected from the game config "winetricks" -> "Install Windows DLL" -> "mfc140" and then was able to run the game without any issues!

-- My software and system info --

Lutris 0.5.18 (installed via DEB-package)
Wine version: wine-ge-8-26-x86_64
Distro:Linux Mint 22.1
Kernel:6.8.0-57-generic
RAM:32 GB
GPU-Driver:NVIDIA 550.120
GPU:NVIDIA GeForce RTX 4070 Ti
CPU:AMD Ryzen 7 3700X 8-Core

Right on, that's another way then to get the game working.

See this link: https://www.microsoft.com/en-us/download/details.aspx?id=48145

Quote: "These packages install run-time components of these libraries: C Runtime (CRT), Standard C++, MFC, C++ AMP, and OpenMP."

So, MFC is one of the components in the full-runtime, and if that's all that needs to be updated then good. The case for using the installer though is that it includes all the components, and they are all the same version. And later on, maybe, the game might need another one of them that only gets installed with the full-installer.

Ah, good to know. Thanks for the hint!
I will remind this if I run into any further issues.

Right on, you're very welcome. :)

Edit: also by using the installer all the components are the same version. If different components were from different versions of the same runtime then they may have undefined results between each other, e.g. just crashing or corrupted behaviour from the program. Installing the runtime avoids that.

Ok, while I'm tech savvy I am new to the world of gaming on Linux, I'm not sure what the process is here. I've got a Steam Deck and have been using Heroic Launcher. What is the step-by-step process for getting this running properly? All I'm getting is the blank screen

Thank you both! I installed Doom 2016 just today and thanks to this thread I could play it right away. :D

Follow the instructions in this video: https://www.youtube.com/watch?v=rzfMXBaLeb0&t=300s

Jump to 5:00 if the timestamped link doesn't start there automatically.

It's for another game but the procedure should be the same. (I don't have a Steam Deck, so I hope that the video's method is still up to date.)

Worked like a charm, just wanted to say thanks for doing the hard part for everyone else!

Thanks for all the helpful hints!

Just some sidenotes regarding audio/sound related issues which might just happen on some rare use cases:

tldr; the usage of a sound server like PulseAudio or Pipewire might help if black screen issues still occur after the redistributables where installed.


I still got a black screen on startup after I installed the C++ redistributables as described.

After stumbling across https://github.com/ValveSoftware/Proton/issues/4016#issuecomment-678020441
I tried to debug with WINEDEBUG="warn+alsa" since I just use plain ALSA without PulseAudio or Pipewire.

I got the following warning in the logs:

0124:warn:alsa:alsa_open_device Unable to open PCM "plughw:0,0": -16 (Device or resource busy)

This happens with one sound card (external via USB) and with the default ALSA config.

My theory, which might be wrong or incomplete, is the following:

Wine (or the game) tries to open the ALSA default sound device, which works. But then, for whatever reason, Wine (or the game) wants to open the sound device again but now directly (via plughw), which then results in the blocking device issue since the card in already in use and the game keeps in the black screen.

After some try and error with different ALSA configuration and dmix I installed PulseAudio and the game works as expected.

I guess this game needs a sound server (like Pulseaudio or Pipewire) or maybe a more comprehensive ALSA config to handle the sound card access properly.

I just wanted to say thanks for this! I had tried everything mentioned in this thread and was going nuts trying to figure out the problem. I changed my launch script to include apulse before the wine command and it started working.

FYI for those who don't know, apulse is a little program that "substitutes" for pulse audio (i.e. make a program think that pulse is installed).