R36S Arcade Guide: MAME Romsets, Cores and Why Games Refuse to Load
Arcade is the one system where the R36S hardware is rarely the problem. Almost every failure traces back to a romset that does not match the core you loaded it in. This guide explains that relationship, then covers the handful of arcade-specific habits — zips, filenames and system BIOS — that differ from every console system on the device.
The One Rule That Explains Almost Every Failure
Console emulation is forgiving about ROM files. A SNES ROM is a SNES ROM; any decent core will load it. Arcade emulation does not work that way, and this is the single fact that turns a frustrating afternoon into a working setup:
An arcade romset is tied to a specific emulator version
Arcade machines were custom hardware, and MAME's understanding of each board changes as it improves. When MAME changes how it reads a board, the expected contents of that game's zip change too. A zip built for one MAME version will be rejected by a core built from a different one — even though both are “MAME” and both files are named the same.
So “my arcade games don't work” almost never means the R36S is too slow. It means the romset and the core disagree about what should be inside the zip.
Matching Sets to Cores
Each arcade core expects one particular set. These are the ones you are likely to meet:
| Core | Romset it expects | Notes |
|---|---|---|
| MAME 2003-Plus | MAME 0.78 | The practical default on this hardware. Built from the 0.78 driver base, so most 0.78 sets work as-is. It also adds games and fixes beyond 0.78, and those additions need 2003-Plus-specific sets. |
| MAME 2003 | MAME 0.78 | The unmodified original. 2003-Plus supersedes it; there is little reason to choose this instead. |
| MAME 2010 | MAME 0.139 | Newer drivers, more accuracy, meaningfully heavier. A 0.139 set will not load in a 0.78 core and vice versa. |
| FBNeo | FBNeo's own set | Narrower library than MAME but strong on what it does cover, particularly Neo Geo and Capcom boards. Its sets are versioned to FBNeo, not to a MAME release. |
Which cores your device actually offers depends on the firmware build, so check the core list on your own unit rather than assuming. What matters is that once you know which core you are using, you know which set to go and find.
Start with MAME 2003-Plus on the R36S
Not because it is the most accurate — it is not. Because a 2003-era driver base does far less work per frame than a modern one, and on four Cortex-A35 cores that difference is the whole game. Newer MAME versions buy accuracy you will struggle to notice on a 640×480 panel, at a cost you will notice immediately.
Our ROM setup tutorial lists mame as the folder and a 2003-Plus set as the format, which is the combination this guide assumes.
Keep the Zip Zipped
Two habits that work fine for console ROMs will break arcade games:
- Do not unzip the file. An arcade zip is not a container for one ROM — it holds many separate chips' contents, each with a filename the core looks up by name. Cores read the zip directly. Extracting it gives you a folder of files the core will not find.
- Do not rename the file. The filename is the game's identifier.
sf2ce.zipis how the core knows this is Street Fighter II Champion Edition and which chips to expect. Rename it to something friendlier and the game disappears from the list.
If you want readable names in the menu, that is what scraping artwork and metadata is for — covered in our themes and scraping guide. Change the display, never the filename.
Arcade BIOS Files Are Romsets Too
Console BIOS files are loose binaries that go in /bios/ and stay there. Arcade system BIOS files are zips, and they behave like romsets rather than like console BIOS files — which changes two things about how you handle them.
They stay zipped, and they can live in either place
A Neo Geo game lists neogeo as its parent set, so the core resolves it exactly the way it resolves the game itself: by looking up a zip by name. That means it must stay zipped — extracting neogeo.zip is a common and completely silent failure.
Cores search several locations, and which ones differ by core, so there is no single correct folder. The reliable approach is to put the BIOS zip both in /bios/ and alongside your games. Our BIOS setup guide lists the specific files — neogeo.zip and pgm.zip are the ones most people meet — and which games need them.
A symptom worth recognising: if some Neo Geo games launch and others fail, that points at a missing or wrong-version neogeo.zip rather than bad dumps of the individual games. The BIOS zip is version-matched to the set just like everything else.
Read the Error, It Is Telling You Something
When an arcade game fails to launch, the core usually reports which files it wanted and could not find. That message is the most useful diagnostic on the device, and it distinguishes the two failure modes:
| What you see | What it usually means |
|---|---|
| A list of missing or wrong-size files | Romset version mismatch. The zip is for a different MAME version than your core. |
Missing neogeo or another system name |
A BIOS zip is absent, has been extracted, or is in a folder this core does not search. |
| The game is not in the menu at all | Wrong folder, an unzipped set, or a renamed file. Not a romset problem. |
| It launches, then runs slowly | The only genuinely hardware-related case, and the rarest one for the boards listed below. |
If games are missing from the menu rather than failing to start, the checklist in our ROM setup tutorial is the faster path.
What the R36S Actually Runs
Here the news is good. What decides the outcome is how demanding the board is to emulate, which is not the same as the year it shipped and not quite the same as whether it draws in 2D. 2D is a good rough guide — and CPS3 is the exception that shows why it is only a guide, being a 2D board that is nonetheless beyond this hardware. Almost everything people mean by classic arcade gaming falls on the right side of the line, including CPS2 titles from as late as the end of the 1990s:
| Board | Examples | Result |
|---|---|---|
| CPS1 | Final Fight, Street Fighter II | Full speed |
| CPS2 | Marvel vs. Capcom, Alien vs. Predator | Full speed |
| Neo Geo MVS | Metal Slug, King of Fighters | Runs smoothly |
| Earlier boards | Pac-Man, Donkey Kong, Golden Axe | Full speed with room to spare |
| Late-1990s boards | CPS3 (2D but demanding), Sega Model 2 and up (3D) | Beyond the comfortable range |
Two boards deserve a note. Naomi and Atomiswave are not MAME territory on this device — they share the Dreamcast's architecture and run on Flycast, so they are covered in the Dreamcast guide instead. And the R36S's D-pad and buttons suit fighters and beat-em-ups well; games built around a spinner, trackball or rotary joystick are playable but will never feel right on any handheld.
A working order of operations
- Decide the core first, then obtain the matching set — not the other way round
- Copy zips to
mame, still zipped, still named as they came - Put
neogeo.zipand any other arcade BIOS in both that folder and/bios/ - Launch one known-good game before copying hundreds
- Read the failure message rather than swapping cores at random
Realistic Expectations
Arcade is one of the best reasons to own this device. The generation the R36S handles effortlessly — roughly Pac-Man through Marvel vs. Capcom — happens to be the generation with the densest concentration of arcade classics, and the compatibility ceiling that frustrates people on Dreamcast and PSP barely applies here.
The cost is that arcade setup is fussier than any console. Not harder, once you know the rule: the set must match the core, every zip stays zipped, and the filename is the game’s identity. Get those three right and most of the library simply works.
Related Guides
- How to Add Games — folder names and the games-not-showing checklist
- BIOS Files: Complete Setup Guide — every system's requirements
- Dreamcast Emulation — where Naomi and Atomiswave are covered
- Best Games to Play — arcade picks worth starting with
- Performance & Compatibility — every system at a glance