Arcade Emulation in Batocera: MAME, FBNeo, NAOMI, and Atomiswave

Batocera arcade emulation guide featuring arcade joysticks and buttons with MAME, FBNeo, NAOMI, and Atomiswave.

You select an arcade game, the screen goes black, and a few seconds later you are back at the game list. Where do you start?

Start with the files and the emulator. Batocera brings many arcade systems together, but those systems still have different requirements. Understanding ROM sets, BIOS files, CHDs, and controls makes troubleshooting much more manageable.

MAME vs FBNeo: Which should you use?

MAME covers a broad range of arcade hardware. FBNeo offers a more focused alternative for many supported 2D arcade games. For NAOMI and Atomiswave, Flycast is a separate option worth starting with. There is no single emulator that is the best choice for every arcade title.

Your goal Suggested starting point
A broad classic arcade collection MAME, with files matching the selected version
Supported 2D fighters, shooters, and Neo Geo games FBNeo, with a matching set
NAOMI or Atomiswave games Flycast in the appropriate system folder

Treat this as a starting strategy. Test the games you actually want to play before committing your whole collection to one setup. Batocera FBNeo reference · MAME reference

Why the correct ROM set matters

An arcade ZIP contains components the emulator expects to find. An archive with the right name can still contain the wrong files. Renaming it does not repair its contents.

Use the ROM definitions for your installed emulator build. FBNeo changes over time, so a collection labeled simply “FBNeo” is not a guarantee of compatibility. Its DAT file describes expected filenames, sizes, and checksums; a ROM manager can audit your files against it. Auditing identifies problems but cannot manufacture missing game data. Official FBNeo core documentation

Recommended workflow: record your Batocera version and selected emulator, validate a small group of games, and expand only after that group works. Back up the working configuration before upgrading.

Split, merged, and non-merged sets

Type How it works
Split Clones depend on shared files in parent archives.
Merged Parent and clone data share an archive; frontend support affects which variants you can launch.
Non-merged Each game includes its parent data; shared BIOS files may remain separate.
Full non-merged Includes shared ROM dependencies, simplifying selection of individual games. Required CHDs remain separate.

Keep arcade ZIP names intact and leave the archives compressed. Use scraping or metadata editing for readable display titles. Official Arcade Guide

Where arcade games go

System Folder
MAME /userdata/roms/mame/
FBNeo /userdata/roms/fbneo/
Neo Geo /userdata/roms/neogeo/
NAOMI /userdata/roms/naomi/
Atomiswave /userdata/roms/atomiswave/

After copying files, refresh the game list. Advanced Arcade Info

What are CHD files?

CHD stands for Compressed Hunks of Data. Some arcade games need a CHD containing disk data alongside their ROM archive.

Batocera's NAOMI documentation uses Ikaruga as an example. Its files are arranged as:

  • /userdata/roms/naomi/ikaruga.zip
  • /userdata/roms/naomi/ikaruga/gdl-0010.chd

The folder matches the ZIP's short name; the CHD keeps its expected filename. Do not assume the CHD itself should be renamed to match the ZIP. Official NAOMI setup reference

Fixing Neo Geo BIOS issues

Neo Geo games require a compatible BIOS set. Batocera documents /userdata/bios/neogeo.zip, with compatibility depending on the ROM set.

  1. Confirm the game is in the Neo Geo folder.
  2. Check which emulator is selected.
  3. Verify that the game and neogeo.zip satisfy that emulator's requirements.
  4. Keep the BIOS archive compressed.

A matching filename alone is insufficient: the files inside the archive must also be correct. If every Neo Geo title fails, investigate the shared BIOS and emulator selection first. If only one fails, investigate that game's files. Official Neo Geo reference

Setting up NAOMI and Atomiswave

Both systems have Dreamcast-related hardware and are supported by Flycast. Use their own system folders for original arcade dumps; a Dreamcast conversion belongs to a different setup.

  1. Place compatible game archives in roms/naomi or roms/atomiswave.
  2. Check the BIOS location required by your installed release. Current wiki paths are /userdata/bios/dc/naomi.zip and /userdata/bios/dc/awbios.zip. Older layouts differ.
  3. Add any required NAOMI CHD in its correctly named subfolder.
  4. Select an available Flycast option for that system and test one game.
  5. Once it launches reliably, tune controls and graphics.

The NAOMI wiki describes its BIOS as optional but recommended for best results. Its version cutoff for the path change is unresolved, so verify your installation rather than guessing from an old tutorial. NAOMI guide · Atomiswave guide

Arcade controls and button mapping

First establish the controller's base mapping in Batocera. Then adjust individual games where their original layouts differ. A menu that responds correctly does not prove that a six-button fighter is mapped comfortably. Controller mapping reference

For FBNeo, open RetroArch's Quick Menu → Controls to adjust player mappings. Save a game remap for a title-specific layout. This RetroArch route applies to libretro cores; standalone emulators have their own controls. FBNeo controls reference

Test movement, every action button, coin, start, player two, and the exit shortcut before calling the setup finished. Avoid changing your global mapping to solve one unusual game.

Quick troubleshooting checklist

Symptom First checks
Returns to the menu Emulator compatibility, ROM audit, BIOS and disk dependencies
One clone fails Missing parent data in a split set
All Neo Geo titles fail Shared BIOS compatibility and selected core
NAOMI game will not boot Archive format, CHD path, BIOS location, Flycast selection
Game runs but buttons feel wrong Player assignment and per-game remap

For a persistent launch failure, inspect /userdata/system/logs/es_launch_stderr.log and es_launch_stdout.log after reproducing it. Batocera troubleshooting reference

Our recommendation: build a collection around games you enjoy and have tested. A smaller library with reliable launches and comfortable controls makes a better home arcade than thousands of unverified entries.

Related guide: How to Map Your Buttons on Batocera V43.

Related Articles

SD Card: Create, Clone, Back Up — SD cards, USB drives and SSDs, American Gear Company Arcade Tips and Tricks.
American Gear Company arcade cabinets with illuminated Pixelcade marquees showing system artwork and Crystal Castles.
Arcade light gun controllers beside a cabinet displaying a target game with a white tracking border.
Arcade Spinners Explained: What They Do and Which Games Use Them
Steam on Batocera: Steam games and Proton setup on a gaming PC
Batocera performance tuning banner featuring a mini PC, game controller, and arcade controls.
Batocera ROMs, BIOS and game setup guide with an arcade joystick, game folders, a BIOS chip and discs