Tutorial: Using A Non-Compatible Controller With MKAK (PC) [UPDATE]

I’ve seen a lot of people having trouble using third-party controllers with this game. A possible cause for this is that the controller isn’t compatible with XInput. XInput is a DirectX library designed specifically for Xbox 360 and other compatible controllers. It was introduced in DirectX 9, replacing the now deprecated DirectInput. It has since become the new input standard for Windows-based games. Thus, all DirectInput controllers are considered legacy and may not be compatible with certain XInput games that don’t support it.

x360ce GUI

To remedy this, you may want to give Xbox 360 Controller Emulator a shot. In short, it’s a mapper library that translates XInput calls to DirectInput calls, allowing your controller to function like an Xbox 360 controller. What’s more, it’s open source, has a relatively small footprint, and is easy to set up.


Step 1: Download x360ce.zip (32-bit) and extract it to the location of MKAK’s executable (e.g., C:\Program Files (x86)\Steam\steamapps\common\mortal kombat arcade kollection\BINARIES\WIN32).

If the link is broken, it may have been updated. In which case, go here.

Step 2: Make sure your controller is plugged in before launching x360ce.exe. You should get two popup messages regarding some missing files: x360ce.ini and xinput1_3.dll, respectively. Click Yes on both popups to create them. (Later versions may create x360ce.ini automatically without a popup.)

Step 3: A New Device Detected window will follow. Leave everything as is and click Next. It will then search an internet database for a preset configuration. If it doesn’t find anything, don’t panic. It just means you’re going to have to do a little more work. Select a preset, if any, and click Finish. Otherwise, skip this by hitting Cancel.

Step 4: Now you’re ready to configure/tweak the controller itself. This is pretty straight forward. Once everything is configured to your liking, click Save and close the program before running MKAK. The changes are written to x360ce.ini, so you don’t need to run x360ce.exe again unless you need to make additional changes. It is not necessary to keep x360ce.exe in the directory for the mapper library to work, as it only configures the INI file.

If you’re having trouble identifying the buttons on your controller, open the Windows Run command (Windows Key+R) and type joy.cpl to launch the Game Controllers applet (XP/Vista/Seven/8), then click Properties to view your controller’s buttons/IDs.

A couple things to note:

    • This tutorial will work for MK9 as well. Just remember to use the 32-bit binary for either game.
    • I recommend DS4Windows if you’re using a PS4 controller. It essentially does the same thing as x360ce, but has better options for DualShock 4 controllers.

If this solution isn’t your cup of tea, there are PC controllers that support both DirectInput and XInput, such as Logitech’s F310 and F710.

Last updated on April 4, 2019

Updated links and made some minor tweaks.

Tutorial: Getting Sound To Work In MKII (WinXP)

I came across this old tutorial I created on how to get sound to work in Mortal Kombat II under Windows XP. It’s irrelevant now, but I decided to revise it a bit and post it here for reference.

Getting DOS games to work in Windows XP can be a major pain, especially when trying to get sound to work. Here’s an application that will fix the sound issue in Mortal Kombat II when running in Windows XP. It’s called VDMSound. It emulates SoundBlaster/AdLib/MIDI in DOS games better than XP does. By default, XP tries to emulate DOS audio using A220 I5 D1 T3 P330. This obviously isn’t working for MKII, but getting it to work is incredibly simple by following the steps below. On a side note, VDMSound will only run on Windows NT 4.0, Windows 95/98/ME (with some tinkering), Windows 2000, and Windows XP. It will not work on Windows Vista or later.

Step 1) Download and install VDMSound 2.0.4.

Step 2) Download and install VDMSound 2.0.4 “Update 2”. Extract directly over the VDMSound 2.0.4 files, typically residing in C:\Program Files\VDMSound, and overwrite all.

Step 3) Download and install LaunchPad 1.0.1. Run install.bat

Press any key to close the window that follows, then locate your MK2.exe and right-click on it. You should see two options listed near the top called Run with VDMS. One has a musical note icon next to it and the other one doesn’t. Select the one with the icon. When ran for the first time, this will bring up a configuration wizard with the choice of using the default configuration or a custom. Let’s choose default for now. Continue by clicking Next. On the next screen, leave everything as is, with Remember my settings checked, and click Finish. This will start up MKII. By default, VDMS uses A220 I7, so make sure these are set correctly in the game (should be default), as well as configuring the sound (F10), which is generally Soundblaster.

I got my custom configuration to work without playing the horrible MIDI music. However, disabling the MIDI emulation (located within the custom settings) will not do this. If disabled, your system will take over. So simply uncheck Dev (Device) below Output located under the MIDI tab and change MKII’s sound to Roland LAPC-1. Also, once you create a configuration of any kind, it will create a shortcut in the same directory as the game’s executable that you may edit later by right-clicking on it and selecting Properties > Advanced.