Charts for the titles matching the filters aboveMAME and MiSTer over timesets of the filtered titles (as of MAME ): in MAME, by the release that first listed each set; on MiSTer, by the date of its first MRA. Drag across the chart to filter by the date titles entered MAME
· Coverage by release yearfiltered titles, grouped by the year MAME gives the parent setCoverage by genrefiltered titles; genre from catver.ini, else the MiSTer Arcade Database, else the MRA, cascaded between parent and clonesShare on MiSTer by genrepercentage of each genre's filtered titles with an MRA on any core; the overall share is the vertical line
Title
Set
Year
Manufacturer
Genre
MAME Driver
Sets
On MiSTer since
Cores
+1
MAME Driver
Titles covered
Sets covered
Genre titles
Genre sets
First on MiSTer
Cores
+1
Core
Source
Repository
MAME drivers
Titles
Sets
First MRA
Latest build
Verified against
Titles and drivers people would like to see on MiSTer, most requested first. Use the +1 button next to any title or driver that is not fully on MiSTer to add your vote. Requested lists those still waiting; Fulfilled lists the ones that are now fully on MiSTer.
Drivers
#
MAME Driver
On MiSTer
Votes
Recent voters
Last vote
Titles
#
Title
Set
Year
Manufacturer
Sets on MiSTer
Votes
Recent voters
Last vote
Every source the coverage is read from. Counts are working arcade sets and titles loaded by at least one core of that source; click a row to list those titles.
Database
Cores
Titles
Sets
Location
Downloader database
Set names found in MiSTer MRAs that do not exist in this MAME version: hacks, homebrew, renamed or removed sets, or MRA typos.
Set name
HBMAME description
Year
Manufacturer
Cores
What this is
A comparison of the arcade machines MAME emulates with the ROM sets MiSTer FPGA cores can load, to show what is still missing on MiSTer. Everything on this page is computed by a Python script (source) and served as static files.
How it is built
MAME side. The -listxml output mamedev attaches to each release. A machine counts as arcade when it is runnable, takes coins, has a video display and is not flagged mechanical; gambling boards (by driver folder, driver file or words such as poker, slot, bingo in the title) and mahjong boards are categorised separately and left out of the headline counts. Working means MAME does not flag it MACHINE_NOT_WORKING (listxml emulation="preliminary"). Not-working sets are kept in the data but excluded from every default count.
MiSTer side. Every MRA (plus the NeoGeo core's romsets.xml) in the official distribution, JTCORES (jotego), Coin-Op Collection, OngoGablogian's MiSTer_Ongo database, the per-core releases/ folders, the developer downloader databases (MeatCores, Slop Cores, kuzecores, jlrh, arcfpga, blahm1d; cores published only as builds, such as Patreon releases, count through the MRAs their database ships), a hand-kept list of repositories nobody indexes yet, and the registry kept by alamone/fpga-verified-against. An MRA's <setname> is the MAME set it loads; its <rbf> names the core.
Dates. Each repository is cloned without file contents and git log gives the day each MRA file was first committed. The earliest date across every source is the date a set became available; a title (MAME parent set plus its clones) takes the earliest of its sets. Where a repository's history was squashed (jotego's jtbin in May 2024, the official distribution starts September 2021) the per-core repository history fills in; where no history exists at all the core's latest build date is used and marked approximate.
Genre. From MAME's category file catver.ini first (a current copy at data/catver.ini if present, else the copies libretro vendors), then the MiSTer Arcade Database, then the MRA's own <category> tag. A set without a category takes its parent's, else a clone's. The raw strings (135 spellings across sources) are remapped to a short common list by data/genre_map.json, which is meant to be edited. The raw value and its source show in the title's tooltip.
When a set entered MAME. From catver.ini's VerAdded section up to 0.180 and from the mame.lst of every later release on GitHub (a set in release N's list but not N−1's was added in N); release dates come from mamedev's git tags, with the few pre-2007 versions interpolated from known dates. A set is counted as "in MAME" from that date even if it was not working then; renamed sets are dated by their new name. Kept in data/mame_added.json.
BIOS sets (MAME isbios, e.g. "Acclaim ZN-1", "Neo-Geo") are not games and are left out entirely.
Charts. They sit under the Titles filters and follow all of them, Coverage included; when the filters match no title they collapse. The "MAME and MiSTer over time" chart counts sets, the others titles.
Titles vs sets. A title is a MAME parent set with all its clones. It counts as covered when any of its sets loads on any core. The burndown therefore shows titles, not individual ROM sets.
Caveats
"On MiSTer" means an MRA exists; it says nothing about how well the core runs the game.
The MAME total is for one MAME version. Sets MAME added after a core shipped show up as covered from the MRA date, so the early part of the curve is measured against today's MAME, not the MAME of the time.
Cores that predate the MRA format (2018 to mid-2019) are dated by their first MRA, which is later than the core's first release.
Category heuristics are rough: some gambling and mahjong boards live in ordinary driver folders and count as arcade.
Data
coverage.json holds every title, set, core and date on this page. summary.json is the roll-up (meta, cores, drivers, unmatched sets).