What it is
MameDuo is a dual-instance arcade launcher built to run two separate game environments at the same time on one piece of hardware and one shared screen.
Finished project
MameDuo H2H
MameDuo.exe is a custom head-to-head arcade frontend that runs two game sessions side by side on a single PC and single display, allowing each player to load and change games independently without interrupting the other side.
Two live game sessions
Independent left and right play
Single PC, single display
Unlocked or locked-system launch
Standalone or frontend-ready
Simple selling line
MameDuo turns one machine and one screen into a live dual arcade system, where both players can play, swap, and reload games independently without interrupting each other.
Overview
A dual-instance arcade launcher built for real-time independence
How it works
Each side operates independently, so the left and right players can launch, reload, and swap games live while the other player keeps playing.
Why it matters
It can run as an independent app or be built into a frontend, giving more flexibility for cabinets, versus displays, and custom dual-play arcade setups.
Full description
More than a normal one-game frontend
Two sessions together
Unlike a normal frontend that launches one emulator for one game, MameDuo manages two separate sessions together in real time on one machine and one shared display.
Live management tools
It handles window placement, side-by-side layout, overlays, controls, popups, and live swapping so both players can move between games without breaking the overall experience.
Built for H2H use
This makes it ideal for a head-to-head cabinet, versus display, or dual-play arcade setup where two users want independent game choice on a single machine.
Flexible deployment
Because it can work as a standalone executable or be integrated into a frontend flow, it suits both direct end-user installs and larger custom cabinet projects.
Screens
Branding, popup workflow, and showcase visuals
Popup control flow
The popup flow supports the live dual-session idea by giving each side a controlled way to change, reload, and manage games without collapsing the other player's session.
Arcade and console direction
This visual direction shows how MameDuo can support a broader battle, versus, or pick-up-and-play experience rather than feeling limited to one rigid arcade presentation style.
Key benefits
Why this setup is useful
Less hardware, more flexibility
It runs two game sessions at once on one PC and keeps everything on a single shared display, reducing the need to build two separate machines for a dual-play setup.
Independent play per side
Each side can support independent gameplay and, where enabled, independent system selection, so one player can change games live without stopping the other side.
Built for live swapping
MameDuo is designed around real-time swapping, not just launching and closing games, which creates a more dynamic arcade battle and pick-up-and-play experience.
Guide reference
How the app works and how to launch it
How the app works
- MameDuo is a two-player head-to-head launcher. Each side keeps its own game choice, system choice, controller profile, MAME working folder, artwork, and INI path.
- Press `Enter` or `1` to launch both selected games into the left and right MAME windows.
- During gameplay, either player can swap only their own game without interrupting the other side.
- The frontend manages the menu, overlay, loading curtains, preview videos, and swap popups as one joined H2H presentation.
Launch options
- `Normal`: run with no system argument for the full unlocked menu. Each side can choose a different supported system.
- `Locked system`: start with `arcade`, `genesis`, or `snes` to keep the whole session on that one system.
- `Skip menu`: `--skip` launches a random game for each active player-side system.
- `Alternate config`: `--config YourFile.cfg`.
Controls
Menu and gameplay keys
Left player
- `Up`: previous game
- `Down`: next game
- `Left`: jump backward by first letter
- `Right`: jump forward by first letter
- `G`: change left player system
Right player
- `I`: previous game
- `K`: next game
- `J`: jump backward by first letter
- `L`: jump forward by first letter
- `H`: change right player system
Global menu keys
- `Enter`, `Return`, or `1`: launch the selected games
- `M`: toggle menu music
- `B`: quit MameDuo from the menu
- In locked mode, the chosen system remains visible but the system-cycle keys do nothing.
Gameplay keys
- `Escape`: return from gameplay to the main menu
- `G`: open the left-side game swap popup during gameplay
- `H`: open the right-side game swap popup during gameplay
- A full launch uses a full-screen loading curtain; a side swap uses a local curtain so the other player stays visible.
Swap popup
Popup controls and helpful notes
Left popup
- `G`: cancel left popup and return to gameplay
- `T`: change left popup system
- `Up`: previous game
- `Down`: next game
- `Left`: jump backward by first letter
- `Right`: jump forward by first letter
- `Enter` or `1`: confirm the new left-side game
- `Escape`: abandon and return to the main menu
Right popup
- `H`: cancel right popup and return to gameplay
- `T`: change right popup system in unlocked mode
- `I`: previous game
- `K`: next game
- `J`: jump backward by first letter
- `L`: jump forward by first letter
- `Enter` or `1`: confirm the new right-side game
- `Escape`: abandon and return to the main menu
- In locked mode, `T` does not change the popup system.
Helpful notes
- The app hides the mouse pointer while it is running and restores it on exit.
- The left and right MAME windows can each use their own artwork, bezels, and INI settings.
- If images, music, or snaps do not appear, check the paths in `config.cfg` first.
Configuration
Editing `config.cfg`
MameDuo reads its settings from `config.cfg`. Keep this file in the same folder as the built EXE or script you are running. Edit it with Notepad or another plain text editor, then restart MameDuo for changes to take effect.
Common section
- `systemMediaPath`: folder containing shared MameDuo media and system selector images
- `bgImagePath`: main menu background image
- `gameOverlay`: overlay image shown over the in-game MAME windows
- `popupBgPath`: background image used by the in-game swap popup
- `bgMusicPath`, `MusicOn`, `musicVolume`: menu music file and volume settings
- `PreviewVideosOn`: true or false, controls whether menu snap videos play
- `LEFT_MENU_JOYSTICK_INDEX` and `RIGHT_MENU_JOYSTICK_INDEX`: 0-based Windows device indexes for the frontend menu; use `-1` to disable a side.
- `LEFT_POPUP_BUTTONS` and `RIGHT_POPUP_BUTTONS`: the two 1-based buttons held together to open or close that side's swap popup.
MAME paths
- `mameLeftExe` and `mameRightExe`: the MAME executable used for each player side
- `mameLeftCwd` and `mameRightCwd`: the working folders for the left and right MAME installs
- `LEFT_CTRLR_NAME` and `RIGHT_CTRLR_NAME`: controller profile names used by the two sides. Use the matching filename without the `.cfg` extension.
Systems
System sections and safe editing tips
Each supported system has its own section, such as `[arcade]`, `[genesis]`, and `[snes]`. These sections tell MameDuo where to find ROMs, logos, and preview videos for that system.
Per-system values
- `romPath`: folder containing the games for that system
- `logoPath`: folder containing marquee or logo images for the games
- `videoPath`: folder containing preview snap videos
- Arcade games launch normally from zipped ROMs.
- Genesis accepts `.bin`, `.md`, `.gen`, `.smd`, and `.zip`; SNES accepts `.sfc`, `.smc`, and `.zip`.
- Genesis and SNES use cart launch mode automatically when those systems are selected.
Safe editing tips
- Make a backup copy of `config.cfg` before editing.
- Keep Windows paths inside the value exactly as written, including drive letters and folder names.
- Use true or false for on or off options such as `MusicOn` and `PreviewVideosOn`.
- If artwork or videos do not appear, check the related path first.
- If MAME does not launch, check the MAME exe path and working folder for that side.
- After editing `config.cfg`, close and reopen MameDuo.
Advanced setup
Layout, controller IDs, and quick checks
Fine-tune the H2H layout
- `LEFT_MAME_X`, `LEFT_MAME_Y`, `LEFT_MAME_W`, and `LEFT_MAME_H` set the embedded left gameplay rectangle.
- The matching `RIGHT_MAME_*` fields set the right gameplay rectangle.
- `STARTUP_MASK_*` defines the tiny hidden staging area used to reduce visible right-side reload flash.
- If either game appears slightly off, these layout fields are the first values to adjust.
Controller and troubleshooting checks
- MAME controller IDs are separate from MameDuo's 0-based menu joystick indexes. Each side's MAME controller profile should map its own physical device.
- If artwork is missing, check the shared media paths first. If MAME does not launch, check that side's EXE, working folder, and system ROM path.
- For no videos or music, confirm `PreviewVideosOn` or `MusicOn` is true and verify the relevant media path.
- The complete guide includes the MAME device-ID test commands and controller-file example.
Get started
Download the guide and explore the H2H workflow
Use the H2H guide to understand the finished workflow and feature set. MameDuo can be used as its own app or integrated into a frontend when you want a flexible dual-session arcade experience on one machine.