Skip to content

Mapping

mojouto3 edited this page Aug 1, 2026 · 5 revisions

Mapping

The Mapping tab detects your physical controllers and forwards their input onto a vJoy virtual device.


Detecting devices

MIM detects physical controllers through the browser's Gamepad API, the same mechanism your browser uses, so no extra drivers are needed just to see them. If a device doesn't show up right away after plugging it in, move a stick or press a button: many controllers only report themselves to Windows on their first input.

MIM's own vJoy virtual devices are automatically excluded from this list, so you can't accidentally map a device to itself.


Single-device mapping

  1. Click a device in the left-hand list to select it.
  2. Pick a target from Forward to (a vJoy virtual device you created in Virtual Devices).
  3. Click Start Mapping.

While mapping is active, the right-hand panel shows the selected device's axes and buttons updating live, and the same live values are what's being sent to the vJoy target.


Multi-device mapping

Click more than one device in the left-hand list to select several at once. Their axes and buttons are concatenated in selection order and forwarded together to a single vJoy target, useful for a HOTAS split across two USB devices (stick + throttle), or any setup where one logical controller is actually several physical ones.

A vJoy device accepts up to 8 axes. If your combined selection exceeds that, MIM shows a warning and the extra axes are dropped rather than mapped incorrectly.

The right-hand panel shows one panel per selected device, so you can confirm each one individually while combined.


Remembered mappings

MIM remembers the last physical device (or combination) mapped to each vJoy target. The next time you launch the app with the same device(s) connected, the selection and target are restored automatically, no need to click through it again.

What's remembered is only the association between devices and target, mapping itself is never started automatically. You still need to click Start Mapping each time, this is intentional: MIM doesn't assume you always want live input forwarding the moment it launches.

If you unplug a device from a remembered combination and reconnect a different set, MIM won't guess, it only auto-restores a combination if every device in it is currently connected.


Mapping keeps running in the background

Closing MIM's window (the X) sends it to the system tray instead of quitting, and minimizing it works the same way, mapping keeps feeding vJoy normally either way, so you can start mapping, put MIM aside, and switch to your game without interruption.

Stopping mapping

Click Stop to release the vJoy device. Mapping also stops automatically if you navigate to a different tab (Mapping's live feed only runs while that tab is open) or fully quit MIM via the tray's Quit, so a vJoy device is never left claimed by a MIM process that's no longer running or visible.

Clone this wiki locally