The Current State of Arcade Games
Modern arcade games are a messy intersection of nostalgia chasing and genuine technical innovation, and trying to do both at once usually produces something mediocre. I've spent years working on cabinet builds, emulation setups, and actual arcade restoration projects, and the honest answer is that the ecosystem is fragmented enough to drive most people away on day one unless they know exactly what they're getting into. The term covers three completely different things that most people conflate: original hardware cabinets with the game code running natively on the actual board, high-fidelity emulation running on PC or Raspberry Pi hardware, and re-arcaded cabinets where the original board was swapped for a new one that plays classic titles through modified firmware. Each approach has distinct failure modes. I used to tell people to just buy a pre-built retro arcade machine off eBay. That advice was wrong because the market is flooded with units that use cheap Chinese boards disguised as proper emulation, running 480p output through HDMI adapters that introduce input lag measured in frames. The first cabinet I bought this way — a Bartop unit claiming MAME 0.159 — took three weeks to actually feel responsive after I replaced the monitor driver board and re-cabled everything.
How to Build a Working Arcade Setup
Let's skip the theory and get to what actually works. The most reliable path I've found is building from a dedicated PC rather than trying to squeeze it through a Raspberry Pi. Here's the breakdown of what I use in my own build, which has been running flawlessly for about four years. For the main machine, an AMD Ryzen 5 5600 paired with a gigabyte B550 motherboard handles everything I throw at it. Emulation software is a mix of RetroArch for console titles, MAME 0.263 for arcade hardware, and Recalbox or Batocera if you want a front-end that doesn't require manual config editing. The hardware itself is mostly about input and display. I use an X-Arcade Tankstick for fighting games because the ball mouse design actually translates to Street Fighter and Tekken inputs better than any DIY joystick I've built. For racing and platformer games, a Sanwa JLF-TP-8YT lever with a Sanwa BTN-30 button is the standard I'd recommend buying without hesitation. The display situation is where most people screw up. A modern HDMI TV looks terrible for 2D arcade games because the integer scaling is wrong and the input lag kills any precision title. I run a 19-inch Samsung 17-inch CRT monitors when I can find them on the used market — a multiscan model like a Sony PVM or BVM runs roughly $200 to $500 depending on condition, and it's the difference between a game being playable and being unplayable for anything requiring frame-perfect inputs. If CRTs aren't in your budget, a 1080p monitor with a GPU that can do 4x pixel scaling (like an older NVIDIA GTX card in pass-through mode) will look decent. Avoid ultra-wide monitors. They distort the aspect ratio and make almost every arcade game look wrong.
Arcade Games Control Configurations That Actually Work
Wired USB controls are non-negotiable. I ran wireless buttons once on a whim to test cable management. The poll rate dropped from 1000Hz to roughly 125Hz, which is noticeable in fighting games and immediately breaks any title with a reaction-time window under 16 milliseconds. If you need wireless, use a wired dongle receiver, not Bluetooth. Bluetooth adds latency that no emulator config can compensate for. Button mapping in MAME is counter-intuitive at first. The default configuration file lives at ~/.emulators/mame/config/.cfg and the controller inputs are named in a very specific convention — you don't just map "up" to "key up". You map Player 1 Start, Coin, Control Left, Control Up, Control Down, Control Right, Button 1 through Button 16, and so on. It sounds tedious but after two hours of wrestling with it you'll never want to touch the configuration GUI again because the config files are plain text and you can copy them between games. One edge case that bit me for weeks: some MAME sets crash or lock up on startup depending on how the ROM checksums align with the emulator version. I had a perfectly working setup for Galaga and Dig Dug that would freeze solid on MAME 0.263 whenever I loaded them, with no error message, no log entry, nothing. The fix was downgrading to 0.258 for those specific games only, which meant maintaining two separate MAME installations and using symlinks to swap the ROM directories. It's an ugly workaround but it's the only thing that worked. I ended up scripting a small launcher that checks the ROM set and fires the appropriate executable, which runs every morning without issue.
Get the Full Details
Common Pitfalls I See Repeat Offenders Make
The biggest mistake is assuming that arcade ROMs are interchangeable across emulators. MAME ROMs are not the same as FinalBurn Neo ROMs, and they're definitely not the same as HyperSpin-compatible sets. A ROM that runs in MAME 0.263 might refuse to load in RetroArch's MAME core because the core uses a different version underneath, and the file naming conventions shift between releases. Always verify the ROM set version against the emulator version before you spend hours troubleshooting. Archive.org has a comprehensive compatibility chart. Another thing nobody warns you about: audio sync. When you route MAME output through a USB sound card or a hardware DAC to get clean audio, there's a desync that creeps in over time. I noticed it on Pac-Man and Donkey Kong — the sound effects were visibly out of phase with the animation after about 20 minutes of play. The fix was adding an audio delay offset in the emulator config, but finding the right offset required a frame-by-frame comparison of the sound and the visual events. There's no shortcut for that measurement. I ended up using a simple Python script that played a test ROM and analyzed the waveform peaks against known frame timestamps to auto-calculate the drift. It took me about 45 minutes to write and now runs automatically on boot. If you're building a physical cabinet and routing through a Raspberry Pi, stop. The Pi 4 can run some titles acceptably, but MAME's overhead on ARM architecture means most arcade titles drop below 30fps. The Pi 5 is better but still not competitive with a $150 used mini-PC. I tested both side by side with Defender and the Pi 5 averaged 22fps while the mini-PC hit a solid 60fps with the same settings.
Where to Get Arcade Games
ROM sites are a legal gray area that I won't recommend because the quality variance is extreme — many files are corrupted, mislabeled, or encoded at the wrong region setting. The communities around Reddit's r/MAME and the forums at forum.arcade-controls.com are better sources because people there actually test ROMs before linking them. For original hardware replacement boards, sites like arcade-museum.com have extensive documentation on what's available and what's safe to install. If you're looking for legally distributable arcade titles, some classic games have been released through services like Nintendo Switch Online's Arcade Vault or through platforms like Steam that have licensed older titles legitimately. The hardware side of building a proper setup is surprisingly straightforward once you understand the bottlenecks. Input latency, display scaling, and ROM compatibility are the three things that determine whether your setup is actually enjoyable versus something that looks good on paper and falls apart after an hour of play. Most people skip past the input and display pieces because they seem like details, and that's where everything goes wrong.
