Mortal Kombat 1

protonopen appid 1971870Game compatibility - Unofficial

ValveSoftware/Proton#7118 · opened 2023-09-22 by TheVeilZ · updated 2026-03-13 · 9 comments · github · game page · search this game

TTheVeilZ 2023-09-22 github

Compatibility Report

Name of the game with compatibility issues: Mortal Kombat 1
Steam AppID of the game: 1971870

System Information

GPU: RX 570
Video driver version: Mesa 23.1.8
Kernel version: 5.15.0-84-generic
Link to full system information report as Gist: System Information
Proton version: Proton Experimental

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.

Symptoms

Mortal Kombat 1 does not launch with Proton 8.0-3 or Experimental. It launches with GE 7-55, but never connects to online services when the game gets to that point.

Every time I try to launch the game with 8.0-3 or Experimental, Steam says the game is Running, but the game window never shows up.

Reproduction

Select Proton 8.0-3 or Proton Experimental (vanilla or Bleeding Edge) and try to launch Mortal Kombat 1.

Proton Log: steam-1971870.log

TTheVeilZ 2023-09-23 github

The game launches with Proton 7.0-6, as well as GE 7-55, but it never completes the "Connecting to online services..." window and just loads indefinitely (the MK logo in the bottom right is active, so it is not frozen). I noticed in the log for Proton 8 posted above, where the game window never shows up, this is the final section that it stops on before I normally close it:

Proton 8:

214.611:0140:0144:trace:seh:RtlRestoreContext returning to 000000007B00E94A stack 0000000000B9B1E0
214.616:0140:0144:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\propsys.dll" at 0000000263650000: builtin
214.617:0140:0144:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\rtworkq.dll" at 00000001FFB10000: builtin
214.618:0140:0144:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\mfplat.dll" at 00000003BB450000: builtin
214.618:0140:0144:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\mf.dll" at 000000033F230000: builtin
214.618:0140:0144:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\mfplay.dll" at 0000000289DE0000: builtin
214.629:0140:0144:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\msdmo.dll" at 0000000218320000: builtin
214.629:0140:0144:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\winegstreamer.dll" at 000000039B8D0000: builtin
pid 4677 != 4676, skipping destruction (fork without exec?)

This is the section from the Proton 7 log, which then continues on with more logs afterward:

Proton 7

30747.892:014c:0150:trace:seh:RtlRestoreContext returning to 000000007B07ED4A stack 0000000000B9B2C0
30747.893:014c:0150:trace:seh:sigsys_handler SIGSYS, rax 0x8e, rip 0x15ca3837f.
30747.900:014c:0150:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\propsys.dll" at 0000000228450000: builtin
30747.901:014c:0150:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\rtworkq.dll" at 0000000335260000: builtin
30747.902:014c:0150:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\mfplat.dll" at 00000003A6D40000: builtin
30747.902:014c:0150:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\mf.dll" at 000000020FC60000: builtin
30747.903:014c:0150:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\mfplay.dll" at 000000034EC90000: builtin
30747.920:014c:0150:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\msdmo.dll" at 000000034ABC0000: builtin
30747.920:014c:0150:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\winegstreamer.dll" at 00000002C83B0000: builtin
30747.922:014c:0150:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\atl100.dll" at 00000001C1EF0000: builtin
30747.924:014c:0150:err:ole:com_get_class_object apartment not initialised
30747.924:014c:026c:trace:seh:sigsys_handler SIGSYS, rax 0x8e, rip 0x15b790fc6.
30747.931:014c:0270:trace:seh:sigsys_handler SIGSYS, rax 0x8e, rip 0x15b790fc6.
30747.940:014c:0270:trace:seh:dispatch_exception code=406d1388 flags=0 addr=000000007B01260E ip=000000007B01260E tid=0270
30747.940:014c:0270:trace:unwind:dispatch_exception  info[0]=0000000000001000
30747.940:014c:0270:trace:unwind:dispatch_exception  info[1]=000000005be0fe70
30747.940:014c:0270:trace:unwind:dispatch_exception  info[2]=0000000000000270
30747.940:014c:0270:warn:seh:dispatch_exception Thread 0270 renamed to "FMediaTicker"
...
...

The Proton 7 log (compressed, as the original was 36 MB):
steam-1971870.log.gz

I have seen a few issues regarding games working in Proton 7 but not 8. Regarding the ones I've seen:

I do not have MangoHud.
Running gamemode doesn't seem to make a difference.
I do not have SteamVR installed.

Thank you.

Ooolikeice 2023-10-03 github

I had exactly the same problem. Switched to the flatpak version of Steam and it launched out of the box.

Mmassatt212 2023-10-30 github

Bazzite OS
16GB Ram
i7 4th Gen
RX 6600
Mesa 23.1.8

MK1 only allows medium settings, treating my gpu like a 4gb card, is there a way to by pass this problem? like a spoof or change gpu name, i tried AMDVLK also same problem btw.

Ggardotd426 2023-11-06 github

The game runs perfectly fine performance wise (5900X, RTX 3090, 1440p with DLSS Quality and Ultra High settings with the 545.29 drivers), but I can't even get through the offense tutorial without it freezing and crashing.

I was about to try and get a Proton log, but I got the stupid Denuvo 24-hour lockout. As soon as I'm allowed back in I'll upload a log.

Launch options are nothing more than PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 mangohud %command%

Mmassatt212 2023-11-17 github

vkd3d uses a lot of vram, idk if its an unreal engine problem but linux vram usage on mk1 is a lot higher.

AApxdono 2023-11-28 github

Overall - really good

Game works really well on Proton Experimental on following Plasma Wayland Arch system with no extra proton env variables.
Tested Story mode, local fights against bots and local PvP (will extend list once have more time).

Issue: "Tutorials" crashing

When trying to continue/exit/go to main menu from tutorials, the game hangs.

Here's the backtrace I was able to pull from when this error happens:
https://gist.github.com/Apxdono/724bddc7d38d155ea63d50e4fdd11ec3

DDARED3ViL90 2024-04-11 github

The game runs fine for me, but I am annoyed that it takes like 5 mins every time I close and re-open the game to "load shaders". I have Windows on a different device and it doesn't do the same, it just loads directly. on Linux; it re-loads shaders every time I open the game and it takes around 5 mins. Any suggestions?

Mmassatt212 2024-05-19 github

My rx 6400 no matter the CPU configuration or Linux Distribution, it always get 15watts ijn benchmark mode, I can't play online until I get a decent fps and MK1 is reading my device like an SteamDeck, I tried SteamDeck=0 and that didn't work, but I get max wattage in regular game mode all except the benchmarks

Gguillaumezin 2026-03-13 github

Hi, does anyone get the vibrations working with PS4 controller? It seems the rumble is not enabled when launching the game. It seems to work ok otherwise (Ubuntu 25.10, AMD RX 6600XT, Core i7-7700T, 32GB RAM). Rumble works in other games (Horizon Zero Dawn for instance).

Proton versions