Sega’s Dreamcast lasted less than two years on store shelves, yet its library keeps growing in 2026 thanks to one open-source project: Flycast. The emulator, maintained by a developer known as flyinghead, shipped version 2.7 on August 19, 2026, adding frame pacing improvements, five new localizations, and multiscreen support for arcade cabinets that originally ran on three linked monitors, and it’s still the current stable release as of September 2026. If you’ve been putting off setting it up because BIOS files and disc formats sound intimidating, this 12-step walkthrough covers every step from download to your first booted game in about 30 minutes, spanning all five Sega systems Flycast supports: Dreamcast, NAOMI, NAOMI 2, Atomiswave, and System SP.
Flycast isn’t just a Dreamcast emulator. It’s a Dreamcast, NAOMI, NAOMI 2, Atomiswave, and System SP emulator rolled into one GPL-2.0-licensed package, and as of September 2026 its GitHub repository sits at 2,509 stars, 320 forks, and 297 open issues, according to the project’s GitHub API data. That arcade coverage matters because Sega, and later Sammy, built entire arcade boards on modified Dreamcast hardware, which is why a single emulator core can run Crazy Taxi at home and Virtua Fighter 4 in the arcade cabinet configuration it originally shipped in.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Is Flycast? Dreamcast, NAOMI, and Atomiswave Explained
Supported Platforms and the Libretro Core
Flycast is a free, open-source, multiplatform Dreamcast emulator descended from the reicast project, itself a continuation of earlier Dreamcast decompilation efforts. It runs natively on Windows, Linux, macOS, Android, Steam Deck (through Flatpak or EmuDeck), and homebrew builds exist for Nintendo Switch and Xbox One/Series consoles. A RetroArch libretro core is also maintained alongside the standalone build, pulling from the same upstream source so the two rarely drift far apart in compatibility.
Five Sega Systems on One Code Path
What separates Flycast from most single-console emulators is the number of systems sharing one code path. The Dreamcast’s Hitachi SH-4 CPU and PowerVR2 GPU became the foundation for three arcade boards: Sega’s NAOMI and NAOMI 2, and Sammy’s Atomiswave. A fourth, lesser-known board called System SP also shares the architecture. Because Flycast emulates the underlying hardware rather than each board individually, it can run home console games and arcade ROMs side by side once the correct BIOS files are in place.
Version History and Origins
The project’s release cadence has been steady through 2026. Version 2.5 shipped in May 2025 with DCNet, a free dedicated connection service for Dreamcast online games, plus a redesigned on-screen gamepad and support for DreamConn+ and DreamPicoPort controller adapters. Version 2.6 followed on January 10, 2026, adding per-pixel transparency rendering on OpenGL ES for mobile devices, a match-code server that revives “battle cable” link titles like F355 Challenge and Cyber Trooper Virtual-On: Oratorio Tangram, and integer scaling. Version 2.7, the current release, adds automatic frame rate detection and pacing, localization in French, Hungarian, Japanese, Brazilian Portuguese, and Swedish, and multiscreen support for the three-monitor NAOMI cabinets Airline Pilot, Sega Strike Fighter, and Derby Owners Club.
Flycast’s lineage traces back to nullDC-era decompilation work that eventually became reicast, a project that itself stalled before flyinghead picked it up and rebuilt it into Flycast. That history matters for anyone comparing accuracy claims between emulators, because Flycast isn’t a clean-room rewrite starting from a blank slate; it inherited over a decade of accumulated hardware quirks and per-game fixes from its predecessors, then layered arcade board support on top. The Dreamcast itself ran a 200MHz Hitachi SH-4 CPU with 16MB of main RAM and a PowerVR2 GPU rendering at roughly 640×480, modest specs even by 2001 standards, which is exactly why a modern phone or budget mini PC can emulate it without difficulty in 2026.
Prerequisites: What You Need Before You Start
What You’ll Need
Before opening a terminal or installer, gather the following. Skipping any of these is the single biggest reason first-time Flycast setups fail partway through.
- A PC, Mac, Android device, or Steam Deck running a 64-bit operating system released in the last five years.
- A Dreamcast console and/or arcade board that you personally own, for legally dumping BIOS files. Flycast can run Dreamcast games with a built-in high-level emulation (HLE) BIOS in a pinch, but NAOMI, NAOMI 2, and Atomiswave titles require the real BIOS files with no HLE fallback.
- Your own Dreamcast game discs, or digital backups you created from discs you own, in GDI, CDI, or CHD format.
- A GPU or integrated graphics chip with Vulkan 1.1 or OpenGL 3.0 support. Almost any hardware from the past decade clears this bar.
- At least 200MB of free storage for the emulator itself, plus roughly 1-1.5GB per Dreamcast game and considerably less for compressed CHD arcade sets.
- A controller. Flycast supports Xbox and PlayStation-style pads out of the box, plus dedicated Dreamcast controller adapters like DreamConn+ and DreamPicoPort.
Platform Compatibility at a Glance
| Platform | Minimum | Recommended | Notes |
|---|---|---|---|
| Windows | Windows 10 64-bit, dual-core CPU, OpenGL 3.0 GPU | Windows 11 64-bit, quad-core CPU, Vulkan 1.1 GPU | Native .exe build, no installer required |
| Linux / SteamOS | 64-bit distro, Vulkan or OpenGL 3.0 | Ubuntu 22.04+, Fedora, Bazzite, SteamOS 3.x | Flatpak is the recommended distribution method |
| Steam Deck | Any SteamOS or Bazzite build | Desktop Mode with Flatpak or EmuDeck integration | Runs comfortably at native resolution |
| macOS | macOS 12 (Apple Silicon or Intel) | macOS 14+ on Apple Silicon | Distributed via Homebrew or CI build |
| Android | Android 8.0, ARM64 chip | Android 12+, mid-range Snapdragon or Dimensity | Available on Google Play and via CI APK |
Step 1: Confirm Your Hardware Meets the Requirements
Performance Expectations by System
Dreamcast emulation is lightweight by 2026 standards. Because the original console ran at 200MHz with 16MB of RAM, almost any PC built in the last ten years handles single-Dreamcast-game emulation without breaking a sweat. Arcade emulation on NAOMI 2 titles is heavier, since those boards paired two PowerVR2 GPUs for extra fill rate, so Flycast has to emulate more silicon per frame. If you’re on a low-power device like an entry-level Android phone or an older Steam Deck LCD, stick to standard Dreamcast and NAOMI titles first and treat NAOMI 2 games as a stress test.
Updating Your GPU Drivers
Check your GPU driver version before installing anything. Flycast’s Vulkan renderer is the default in recent builds and generally outperforms the OpenGL path, but it also exposes driver bugs that OpenGL papers over. On Windows, update through Nvidia GeForce Experience, AMD Adrenalin, or Windows Update for Intel Arc and integrated graphics. On Linux, make sure Mesa is current, since older Mesa builds shipped with distro-default repositories can lack full Vulkan 1.1 support.
Step 2: Download Flycast v2.7 for Your Platform
Official Download Sources
Get Flycast only from the official GitHub releases page or the linked continuous integration builds page, which publishes fresh builds off the master branch between tagged releases. Avoid third-party download sites bundling Flycast with adware installers; the project itself is free and doesn’t need a wrapper.
Choosing the Right Build for Your Platform
Windows and Linux users get a portable zip or AppImage with no installer. macOS users typically build through Homebrew or grab a signed CI build. Android users can install from Google Play or sideload the CI-built APK. The CI builds page explicitly warns that non-master branches are bleeding-edge and may crash, so for a first setup, stick to the tagged v2.7 release rather than a nightly build.
# Recommended folder layout once downloaded
Emulation/
flycast/
flycast.exe (or flycast on Linux/Mac)
data/
dc_boot.bin
dc_flash.bin
naomi.zip
awbios.zip
mappings/
vmu_save_A1.binStep 3: Install Flycast on Windows and Linux
Installing on Windows
On Windows, extract the downloaded zip to a permanent folder outside Program Files or any OneDrive-synced directory, since Windows write permissions and cloud sync can silently corrupt the config file Flycast creates on first launch. Run flycast.exe directly. The first launch generates a settings folder in your user profile alongside a config file that stores every setting you touch in the interface, so there’s no manual config editing required for a standard setup.
Installing on Linux via Flatpak
On Linux, the cleanest install path is Flatpak, distributed through Flathub as org.flycast.Flycast. Flatpak handles sandboxing and dependency management automatically, which avoids the library version mismatches that plague manually compiled builds across different distros.
# Install Flycast via Flatpak on any modern Linux distro
flatpak install flathub org.flycast.Flycast
# Launch it
flatpak run org.flycast.FlycastIf your distro doesn’t have Flatpak configured, install it first (most distros ship a package called flatpak in their default repos), add the Flathub remote, then run the command above. AppImage builds are also published for users who prefer a single-file, no-install option.
Step 4: Install Flycast on Steam Deck, macOS, and Android
Steam Deck and Bazzite Setup
Steam Deck and Bazzite users have two solid paths: install the Flatpak directly in Desktop Mode using Discover or the flatpak command above, or use EmuDeck, which bundles Flycast alongside dozens of other emulators and pre-configures BIOS folder paths automatically. EmuDeck’s Flycast integration is documented on the project’s own wiki and handles the folder structure so you only need to drop BIOS and game files in the right place, rather than hunting for Flycast’s data directory yourself.
Adding Flycast to Steam for Gaming Mode
Installing the Flatpak only makes Flycast launchable from Desktop Mode by default. To play from Gaming Mode instead, stay in (or switch to) Desktop Mode, open Steam, choose Add a Game, then Add a Non-Steam Game, and check the box next to Flycast in the list before confirming. It then shows up as a regular entry in your Steam library, so you can launch straight into it from Gaming Mode without dropping back to the desktop first.
Installing on macOS
On macOS, Apple Silicon and Intel builds are both maintained. Homebrew users can build from source with the standard cmake toolchain, though most people will prefer grabbing a prebuilt binary from the CI builds page to skip the Xcode command-line tools setup.
Installing on Android
On Android, install from Google Play for the stable, signed release, or sideload the CI-built APK if you want a build closer to the latest commits. Android’s storage permission model on Android 11 and newer requires granting Flycast “All files access” rather than the default scoped storage permission, or it won’t be able to see your BIOS and game folders even after you place files correctly.
Step 5: Understand Dreamcast BIOS Files
Which BIOS Files You Need
Flycast is unusual among console emulators in that the Dreamcast BIOS is technically optional. The emulator ships a high-level emulation BIOS that boots most Dreamcast games without any files from a real console. That said, HLE BIOS has known compatibility gaps, and some titles behave incorrectly, hang on boot animations, or fail region checks without the genuine BIOS installed. For the most accurate experience, dump the real files from a Dreamcast you own.
The two files you need are dc_boot.bin and dc_flash.bin. In the standalone build, both go directly into Flycast’s data folder alongside the executable. In the RetroArch libretro core, they go into a dc subfolder of RetroArch’s system directory instead, for example system/dc/dc_boot.bin. Libretro’s own documentation lists dc_boot.bin with an md5sum of e10c53c2f8b90bab96ead2d368858623 for verification purposes, which is worth checking against your dump if a game refuses to boot with the real BIOS installed.
Dumping BIOS Files From Your Own Dreamcast
Dumping these files requires a Dreamcast with a way to run homebrew, typically through a boot disc exploit or a modded GD-ROM drive, plus a way to transfer the dump to your PC over a broadband adapter, SD card mod, or serial cable. This is identical in spirit to dumping prod.keys from a Nintendo Switch or a firmware image from a PS3: it’s legal when you own the hardware and only distribute the dump to your own devices, and it’s the only way Flycast’s developers or any legitimate emulation community will help you obtain these files.
Step 6: Add BIOS Files for NAOMI, NAOMI 2, and Atomiswave
Arcade BIOS Requirements
Unlike the Dreamcast, none of the arcade boards Flycast supports have an HLE fallback. NAOMI, NAOMI 2, and Atomiswave games simply will not boot without their respective BIOS archives in place, so this step isn’t optional if you want to play arcade titles like Marvel vs. Capcom 2, Virtua Tennis, or Guilty Gear X.
| System | Required File(s) | HLE Fallback? | Goes In |
|---|---|---|---|
| Dreamcast | dc_boot.bin, dc_flash.bin | Yes, built-in HLE available | Flycast data/ folder (or dc/ in RetroArch) |
| NAOMI | naomi.zip | No, mandatory | Flycast data/ folder (or dc/ in RetroArch) |
| NAOMI 2 | naomi.zip (shared BIOS) | No, mandatory | Flycast data/ folder (or dc/ in RetroArch) |
| Atomiswave | awbios.zip | No, mandatory | Flycast data/ folder (or dc/ in RetroArch) |
| House of the Dead 2 (NAOMI) | hod2bios.zip (game-specific) | No, mandatory | Flycast data/ folder (or dc/ in RetroArch) |
Sourcing Arcade BIOS Archives
Most NAOMI and Atomiswave BIOS archives are sourced the same way MAME arcade ROM sets are: through your own dumps of arcade PCBs, or through preservation projects built specifically around personally owned hardware. A handful of games, like House of the Dead 2, ship a unique BIOS variant separate from the standard naomi.zip, so if a specific title refuses to boot even with the standard arcade BIOS present, check whether it needs its own file before assuming your install is broken.
What Makes NAOMI and Atomiswave Different From Dreamcast
NAOMI and NAOMI 2 Architecture
It’s worth understanding why Flycast treats these as separate systems with separate BIOS requirements rather than just “Dreamcast games running in an arcade cabinet.” NAOMI, which stands for New Arcade Operation Machine Idea, was Sega’s arcade board built directly on Dreamcast-derived hardware, but it used cartridge-based ROM boards or GD-ROM discs instead of the console’s proprietary GD-ROM format, and it ran a stripped-down BIOS designed for coin-op operation rather than a home console boot sequence. NAOMI 2 added a second PowerVR2 GPU purely for extra geometry and fill-rate headroom, aimed at 3D fighting and racing games that needed more polygons than a single Dreamcast-class GPU could push.
Atomiswave’s Cartridge System
Atomiswave, developed by Sammy rather than Sega, is a separate but architecturally similar board that arcade operators favored for its cartridge-swap system, which let a single cabinet run multiple games without re-flashing anything. Games like Guilty Gear XX and Melty Blood Actress Again originated on Atomiswave hardware before being ported elsewhere. Because none of these arcade variants shipped with a home-user-friendly BIOS the way the Dreamcast did, Flycast can’t fall back to an approximate HLE implementation for them the way it does for Dreamcast software; the arcade BIOS controls low-level board initialization that HLE substitution would get wrong in ways that break more games than it fixes.
Step 7: Choose the Right Disc Format — CHD vs. GDI vs. CDI
Comparing CHD, GDI, CDI, and CUE/BIN
Flycast reads three main disc image formats: CHD, GDI, and CDI, plus CUE/BIN pairs when loaded through an m3u playlist in the libretro core. Each has tradeoffs worth understanding before you spend hours converting a library.
| Format | Extension | Compression | Best For |
|---|---|---|---|
| CHD | .chd | Yes, roughly 40-60% smaller than raw GDI | Storage-constrained devices, Steam Deck, phones |
| GDI | .gdi + .bin/.raw tracks | No, uncompressed | Maximum compatibility, easiest to troubleshoot |
| CDI | .cdi | No, uncompressed | Older dumps from DiscJuggler-era rips |
| CUE/BIN | .cue + .bin | No, uncompressed | Multi-disc games via m3u playlists |
Converting GDI to CHD
CHD is the format most 2026 emulation guides recommend by default because it saves substantial disk space without sacrificing accuracy, and it’s the format MAME’s own tooling produces for arcade sets. If your existing collection is in GDI, you can convert it to CHD using chdman, the command-line tool distributed with MAME, rather than re-ripping anything.
# Convert a GDI dump to CHD with chdman (from the MAME tools package)
chdman createcd -i "Crazy Taxi.gdi" -o "Crazy Taxi.chd"Point Flycast at your games folder, or add individual disc images through the built-in file browser, and the library screen will populate with box art pulled from local metadata once you’ve launched each title at least once.
Step 8: Set Up VMU Memory Card Saves
How VMU Saves Are Stored
The Dreamcast’s VMU (Visual Memory Unit) doubled as both a memory card and a tiny secondary screen, and Flycast recreates its save behavior faithfully rather than substituting generic save states. VMU saves are stored as binary image files named vmu_save_A1.bin, vmu_save_B1.bin, and so on for each of the four controller ports, plus a separate dc_nvmem.bin file that holds system-level settings and non-volatile memory unrelated to any single VMU.
Fixing Missing VMU Errors
In the standalone build, these files live in Flycast’s data folder, the same directory as your BIOS files. In the libretro core, they’re stored under RetroArch’s system/dc/ directory. If a game reports “no VMU found” or refuses to save, open Settings, then Maple, and confirm Port A Device 1 is set to VMU rather than none or a different peripheral type. Android’s v2.7 release added Google Auto Backup support specifically for VMU saves and non-volatile memory, which is worth enabling if you’re switching phones or reinstalling the app, since it prevents losing save data during an app data wipe.
# Typical VMU and NVRAM file layout in Flycast's data directory
data/
dc_boot.bin
dc_flash.bin
vmu_save_A1.bin
vmu_save_B1.bin
dc_nvmem.binStep 9: Configure the Renderer, Resolution, and Upscaling
Internal Resolution and Upscaling
The Dreamcast rendered natively at roughly 640×480, which looks soft on a modern 1440p or 4K display. Flycast’s renderer settings menu lets you push internal resolution well above native, along with anisotropic filtering and, on supported GPUs, per-pixel transparency rendering that the January 2026 v2.6 update brought to mobile OpenGL ES devices for the first time.
Vulkan vs. OpenGL and Widescreen Options
Set the renderer backend to Vulkan first, since it’s the primary target for new feature development and generally posts better frame pacing than the OpenGL fallback, particularly with the automatic frame rate detection v2.7 introduced. If you hit graphical glitches or crashes on an older or less common GPU, switch to OpenGL 3.0 as a compatibility fallback before assuming a game is simply broken. Integer scaling, added in v2.6, is worth enabling if you want pixel-perfect scaling on 2D-heavy titles instead of the slight blur that non-integer stretching introduces.
Widescreen hacks exist for a subset of games that support them natively or through community patches, but they’re applied per-game rather than as a global setting, so check a title’s compatibility notes before forcing 16:9 and ending up with a stretched HUD.
Step 10: Map Controllers, Light Guns, and Arcade Sticks
Standard Controller Mapping
Open the Controls menu and Flycast will detect any connected Xbox or PlayStation-style pad automatically, mapping face buttons and analog sticks to their Dreamcast equivalents by default. For a more authentic feel, dedicated adapters like DreamConn+ and DreamPicoPort let you use an actual Dreamcast controller or VMU hardware over USB, and both received additional stability fixes in the v2.7 release alongside contributions to the newer DreamPotato project.
Arcade Sticks and Light Guns
Arcade stick users running NAOMI or Atomiswave fighting games should remap inputs per-game where needed, since some arcade titles used six-button layouts that don’t map cleanly to a standard gamepad’s four face buttons without doubling up on the shoulder triggers. Light gun games, a notable part of the NAOMI library thanks to titles built on House of the Dead hardware, use mouse-based aiming by default rather than requiring a specialized peripheral, which is the same approach most PS2 and arcade emulators take in 2026.
Step 11: Turn On Netplay and Multiplayer Features
DCNet and the Match-Code Server
Flycast’s online features go beyond simple netplay between two emulator instances. DCNet, introduced in v2.5, is a free dedicated connection service built specifically to revive the Dreamcast’s original online games without requiring you to run your own server infrastructure. Version 2.6 added a match-code server on top of that, restoring “battle cable” link functionality for games originally designed to connect two physical Dreamcasts, including F355 Challenge and Cyber Trooper Virtual-On: Oratorio Tangram, both of which received specific online fixes again in the v2.7 changelog.
Games With Restored Online Play
Other titles with restored or improved online play as of v2.7 include Power Smash (also known as Power Stone in some regions) and Rune Jade. To use these features, check each game’s dedicated wiki entry or in-emulator online status indicator, since not every Dreamcast game with original online support has had its servers rebuilt, and functionality varies title by title rather than working uniformly across the whole library.
Step 12: Launch and Verify Your First Game
First Boot Checklist
With BIOS files placed, a disc image loaded, and your controller mapped, launch a well-known, forgiving title first rather than jumping straight to a NAOMI 2 fighting game. Crazy Taxi, Sonic Adventure, or Power Stone are commonly used as first-boot tests because they’re not especially demanding on the renderer and make BIOS or controller misconfigurations obvious immediately through crashes or black screens, rather than subtle graphical glitches you might not notice.
Confirming Your VMU Save Works
If the game boots to a menu, displays the Sega logo correctly, and accepts controller input, your BIOS and renderer setup are working. Save your progress once, exit, and relaunch the game to confirm your VMU save persisted correctly before moving on to the rest of your library. This two-minute check catches VMU path misconfigurations before you’ve sunk hours into a save file that silently isn’t being written to disk.
Best Games to Test Your Flycast Setup
Console Test Titles
Once the basics work, run a short gauntlet of titles that stress different parts of Flycast before trusting it with your full library. Sonic Adventure and Crazy Taxi are light on the renderer and a good baseline check for BIOS and controller configuration. Soulcalibur and Power Stone push texture and transparency handling harder, which is useful for confirming your Vulkan renderer settings are working correctly rather than silently falling back to a lower-quality path.
Arcade Test Titles
On the arcade side, once your NAOMI BIOS is confirmed working, Virtua Tennis and Crazy Taxi’s arcade original are forgiving first tests. Marvel vs. Capcom 2 and Guilty Gear XX are heavier fighting-game tests worth trying once you’ve confirmed input mapping is solid, since precise frame-perfect inputs will expose any controller latency or mapping issues immediately. If you’ve set up the multiscreen feature added in v2.7, Sega Strike Fighter or Derby Owners Club are the titles built specifically to validate that configuration, since they were designed around the original three-monitor cabinet layout.
Building Flycast From Source (Advanced)
Why and When to Build From Source
Most users never need to compile Flycast themselves, since prebuilt binaries and CI artifacts cover every mainstream platform. Building from source becomes worthwhile if you’re on an unsupported Linux distro, want to test a specific unreleased fix before it lands in a tagged version, or want the latest commit-level improvements to a specific game’s compatibility ahead of the next scheduled release. The official repository uses a standard CMake-based build with a recursive git clone to pull in the project’s submodules.
# Build Flycast from source (Linux/macOS)
git clone --recursive https://github.com/flyinghead/flycast.git
cd flycast
mkdir build && cd build
cmake ..
make -j$(nproc)Common Build Errors
The –recursive flag matters here, since Flycast pulls in several third-party libraries as git submodules and a shallow clone will fail partway through configuration without them. If you hit a build error referencing a missing header, it’s almost always a missing system dependency like Vulkan headers, SDL2, or a compiler that doesn’t support the C++ standard the project targets, rather than a bug in the source itself. The project’s GitHub Actions workflows are public, so you can check the exact dependency list a fresh Ubuntu runner installs before building if your local environment is missing something.
Common Pitfalls When Setting Up Flycast
Installation and Permission Pitfalls
- Extracting to a OneDrive or Google Drive-synced folder. Cloud sync clients lock config files mid-write on Windows, corrupting Flycast’s settings file and causing it to silently reset on every launch.
- Assuming HLE BIOS covers arcade games too. The built-in HLE fallback only applies to Dreamcast titles. NAOMI, NAOMI 2, and Atomiswave games need their real BIOS archives with no exceptions.
- Placing BIOS files in the wrong folder for your build type. Standalone Flycast uses a data folder next to the executable, while the RetroArch libretro core expects a dc subfolder inside RetroArch’s system directory. Mixing these up is the most common cause of “BIOS not found” errors.
- Skipping Android’s “All files access” permission. Android 11 and newer’s scoped storage model blocks Flycast from reading BIOS or ROM folders unless you manually grant broader file access in system settings.
BIOS, Disc, and Save Data Pitfalls
- Forgetting that some NAOMI games need a game-specific BIOS file. House of the Dead 2 and a handful of other titles won’t boot with only the standard naomi.zip present.
- Mixing CDI dumps from different ripping tools without checking region and revision. Older DiscJuggler-era CDI dumps sometimes have mismatched track layouts that cause black screens even though the file loads without an error.
- Running a bleeding-edge CI build as your daily driver. Nightly builds pull straight from the master branch and can introduce regressions between tagged releases; stick to the numbered v2.7 release unless you specifically need an unreleased fix.
- Overwriting VMU saves by testing multiple emulators on the same game. If you also run the libretro core alongside the standalone build, remember they use different save folders by default, so progress in one won’t automatically appear in the other.
Flycast vs. Redream vs. Demul: How the Three Compare
How the Three Emulators Compare
Flycast isn’t the only Dreamcast emulator still standing in 2026, but it’s the only one of the three major options under active, cross-platform development. Redream is a closed-source alternative with a free tier and a paid premium tier that unlocks higher internal resolutions and other extras; it’s built primarily for Dreamcast games rather than the broader arcade board family, and it’s known for running acceptably on lower-end hardware where Flycast’s Vulkan path can be more demanding. Demul, by contrast, is an older Windows-only emulator that also covered Dreamcast, NAOMI, and Atomiswave, but development has stalled and it no longer receives meaningful updates.
| Feature | Flycast | Redream | Demul |
|---|---|---|---|
| License / price | Free, open-source (GPL-2.0) | Free tier + paid premium tier | Free, closed-source |
| Platforms | Windows, Linux, macOS, Android, Switch/Xbox homebrew | Windows, Linux, macOS, Android, consoles | Windows only |
| Arcade boards (NAOMI, Atomiswave) | Yes, full support | Limited / Dreamcast-focused | Yes, but unmaintained |
| Development status (2026) | Active, monthly-scale updates | Actively maintained | Discontinued |
| Netplay / online | DCNet, match-code server, per-game online fixes | Basic netplay | None |
| Best for | Full arcade + console coverage, latest hardware | Low-end hardware, simplicity | Legacy setups only |
Which One Should You Choose?
If your goal is strictly casual Dreamcast console gaming on an aging laptop, Redream’s lower system demands might get you there with less renderer tinkering. If you want NAOMI and Atomiswave arcade titles, active development, and features shipping every few months, Flycast is the only one of the three still actively closing that gap in 2026.
Advanced Tips: Performance Tuning and NAOMI Multiscreen
Widescreen Cheats and Synchronous Rendering
Once your basic setup is stable, a few advanced settings squeeze out extra accuracy and performance. Widescreen cheats bundled in the config folder unlock native 16:9 rendering for supported titles without stretching. The synchronous rendering toggle can fix subtle timing bugs in a small number of games at a minor performance cost, worth trying if you notice audio desync or frame-pacing stutter that persists after switching renderer backends.
NAOMI Multiscreen and Frame Rate Detection
The headline addition in v2.7 is multiscreen support for NAOMI cabinets that originally used three linked monitors side by side, specifically Airline Pilot, Sega Strike Fighter, and Derby Owners Club. These titles previously ran with a single, cropped view in Flycast; the new release can drive multiple output windows or a single ultrawide span to recreate the original triple-screen cabinet layout, assuming you have the display setup or a wide enough single monitor to accommodate it.
For frame pacing, the automatic frame rate detection introduced in v2.7 removes the need to manually tell Flycast whether a game targets 30fps or 60fps internally, which previously caused visible judder on titles that didn’t match your display’s refresh rate. Leave it enabled unless you’re debugging a specific game’s timing and need manual control.
Troubleshooting Flycast: Common Errors and Fixes
BIOS, Boot, and Display Errors
- “BIOS not found” on a Dreamcast game. Confirm dc_boot.bin and dc_flash.bin sit directly in the data folder (standalone) or system/dc/ (libretro), and double-check the filenames aren’t renamed with extra characters by your browser’s download manager.
- Arcade game won’t boot at all, no error shown. This almost always means the arcade-specific BIOS (naomi.zip or awbios.zip) is missing or in the wrong folder, since there’s no HLE fallback for arcade boards.
- Black screen after the Sega logo. Usually a corrupted or mismatched disc image. Re-dump the game or convert it to CHD with chdman rather than assuming the emulator itself is broken.
- “No VMU found” in-game. Open Settings, then Maple, and verify Port A Device 1 is set to VMU rather than none or an incompatible peripheral type.
- Audio crackling or popping. Try switching the audio backend in settings, and confirm your buffer size isn’t set too low for your hardware; a slightly larger buffer trades a few milliseconds of latency for stability.
Controller, Config, and Build Errors
- Controller not detected. Confirm the OS recognizes the pad in another application first, then check Flycast’s Controls menu to make sure the correct port is assigned before assuming a driver issue.
- Config resets on every launch (Windows). Move the Flycast folder out of OneDrive, Google Drive, or Program Files, all of which can interfere with write permissions or file locking.
- Android says storage permission denied despite files being present. Grant “All files access” manually in Android’s app settings rather than relying on the default permission prompt, which only grants scoped access on Android 11 and newer.
- Game runs but multiscreen NAOMI titles only show one panel. Confirm you’re on v2.7 or later, since multiscreen support for cabinets like Airline Pilot and Sega Strike Fighter didn’t exist in earlier releases, and check your display output configuration in Flycast’s video settings.
- Build from source fails with missing header errors. Re-run the clone with the –recursive flag to pull in required submodules, and confirm Vulkan SDK headers and SDL2 are installed before running cmake again.
Is Flycast Legal? BIOS Dumping and Copyright
Why the Software Itself Is Legal
The Flycast software itself is unambiguously legal. It’s open-source, contains no Sega copyrighted code, and is distributed under the GPL-2.0 license on GitHub without restriction. The legal gray area, as with every console emulator, sits entirely on the content side: BIOS files and game images.
Rules Around BIOS and ROM Dumps
US case law, dating back to Sony v. Connectix in the early 2000s, has generally treated emulator software as legal to write and distribute, since reverse-engineering for interoperability is protected. What isn’t protected is downloading BIOS files or game ROMs you don’t own from the internet. The safe, legal path is dumping your Dreamcast BIOS and disc images from hardware and discs you personally own, exactly as the setup steps above describe, and not redistributing those dumps to anyone else. Arcade BIOS files fall under the same principle, though sourcing them legitimately is harder in practice since few people own physical NAOMI or Atomiswave arcade PCBs.
Frequently Asked Questions
Do I need a real Dreamcast BIOS to use Flycast?
Not for Dreamcast games, since Flycast includes a high-level emulation BIOS that boots most titles without one. NAOMI, NAOMI 2, and Atomiswave arcade games do require the real BIOS files with no fallback option.
What’s the difference between the Flycast standalone app and the RetroArch core?
Both pull from the same upstream flyinghead/flycast codebase, so compatibility is nearly identical. The main practical difference is folder structure: standalone uses a data folder next to the executable, while the libretro core stores BIOS and save files inside RetroArch’s system directory.
Should I use CHD or GDI for my Dreamcast games?
CHD if storage space matters, since it’s roughly 40-60% smaller than an uncompressed GDI dump with no accuracy tradeoff. GDI is fine if you’re not short on space and prefer the simplicity of raw, uncompressed track files.
Can Flycast run NAOMI 2 games well on a Steam Deck?
Most NAOMI 2 titles run acceptably on Steam Deck hardware, though the dual-GPU NAOMI 2 architecture is more demanding than standard Dreamcast or first-generation NAOMI games, so expect a bigger performance cushion to matter more on lower-power devices.
Why does my arcade game show a black screen with no error message?
This is almost always a missing or misplaced arcade BIOS file. Unlike Dreamcast games, NAOMI and Atomiswave titles fail silently rather than showing a clear “BIOS not found” message in some builds, so check your BIOS folder first.
Is Flycast better than Redream?
It depends on your priorities. Flycast covers more systems, including NAOMI, NAOMI 2, and Atomiswave arcade boards, and receives more frequent feature updates. Redream is closed-source but tends to run better on lower-end hardware and offers a simpler setup for users who only care about Dreamcast console games.
Is Flycast the best Dreamcast emulator to use in 2026?
For most setups, yes. Flycast is the most actively developed Dreamcast emulator of the three major options covered above, and it’s the only one that also runs NAOMI, NAOMI 2, and Atomiswave arcade titles on the same code path. Choose Redream instead if you only play Dreamcast console games on lower-end hardware and want the simplest setup; choose Flycast for the broadest system coverage and the most frequent updates.
Does Flycast support online multiplayer for Dreamcast games?
Yes, through DCNet, a free dedicated connection service introduced in v2.5, plus a match-code server added in v2.6 that restores “battle cable” link functionality for select titles. Coverage varies by game rather than working uniformly across the whole library.
Where do VMU save files get stored?
In the standalone build, VMU saves are stored as vmu_save_A1.bin and similarly named files inside Flycast’s data folder. In the RetroArch libretro core, they’re stored under RetroArch’s system/dc/ directory instead.
Related Coverage
- Nintendo Switch PC Emulator Setup: 12 Steps, 90 Min [2026]
- VBA-M Setup for Pokémon: 12 Steps, 40 Min [2026]
- Shadow PC Lite vs Neo/Power: Steam Deck Setup in 12 Steps [2026]
- Set Up Shadow PC Cloud Gaming: 13 Steps, 100 Min [2026]
- How to Set Up Cemu Wii U Emulator: 12 Steps, 90 Min [2026]
