✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.
⭐ Key Takeaways
Quick answer: Our top pick is SanDisk 1TB Extreme microSDXC Card, with Samsung T7 Portable SSD 1TB as a strong alternative.

The ROG Ally runs Windows, and that changes the Flycast job completely. There is no Flatpak to install and no sandbox to escape: Flycast ships as a standalone Windows program, so on the Ally it behaves exactly as it does on a desktop PC, with its full settings tree and netplay features intact.

As an Amazon Associate, we earn from qualifying purchases.

This walkthrough covers the Ally-specific work: installing the Windows build somewhere sensible, placing a BIOS dumped from your own Dreamcast, organising your own disc dumps, protecting your saves with per-game VMUs, and choosing renderer settings that respect a 7-inch 1080p screen.

This article contains affiliate links, and purchases made through them may earn this site a commission at no extra cost to you.

Quick Answer

Download the standalone Windows build of Flycast from the project’s builds page, extract it to its own folder on the Ally, and add your game dumps under Content Location. The built-in replacement BIOS starts most games; add dc_boot.bin and dc_flash.bin dumped from your own Dreamcast for the best compatibility, then enable per-game VMUs.

Step 1: Install the Windows Build

Flycast’s project page offers three Windows channels: master builds with the newest fixes, nightly dev builds that are frankly experimental, and stable tagged releases on GitHub Releases. Take a stable release; on a handheld you set up once, the newest fix is rarely worth the newest bug.

The build arrives as an archive, not an installer. Extract it into a dedicated folder on the internal drive or a microSD card and run the executable; Flycast keeps its data beside itself, so the whole setup can be copied or backed up as one folder. Adding it to Armoury Crate’s game library keeps it reachable from the couch-friendly side of the Ally.

Step 2: The Data Folder and Your BIOS

Flycast organises itself around a data folder inside its home folder. That is where the BIOS files live, where the console’s flash memory file sits, and where your VMU save files are written, named for their controller port and slot, such as vmu_save_A1.bin. Learn where this folder is before anything goes wrong: your entire Dreamcast save history is a handful of small files inside it.

Flycast does not strictly need a BIOS for Dreamcast games. It carries a high-level emulation of the console’s system software, and most games boot and play on the replacement with nothing added. The real dump is still the route the project recommends: some games lean on exact BIOS behaviour, and the authentic boot sequence only appears with the real file. Dump two files from your own Dreamcast, dc_boot.bin and dc_flash.bin, and place them in the data folder under those exact names. Keep boot and flash from the same console; a mismatched pair is the usual suspect when the date and time refuse to stick.

Step 3: Add Your Games With Content Location

Games are added by folder, not file by file. In Settings, the Content Location option has an Add button: select the folder holding your disc dumps and Flycast scans it recursively, so one parent folder with subfolders per system works well. Flycast reads the standard dump formats, GDI, CDI, CUE and CHD among them.

CHD is the practical choice on the Ally. It compresses each disc into a single file, kinder to a microSD card and tidier to move between machines, and Flycast reads it natively. Arcade games arrive differently, as MAME-format archives, and one layout rule catches people out: a Naomi GD-ROM title needs its CHD inside a folder named after the game, next to the archive. A black screen usually means exactly that folder is missing.

Step 4: Per-Game VMUs, Set Once

The Dreamcast saved to the Visual Memory Unit in the controller, and Flycast emulates up to four of them, one per controller socket. By default every game shares the same VMU files. That mirrors a one-VMU household and fails the same way: the shared card holds a limited number of blocks, fills quickly, and one full or corrupted file can block saving across your whole library.

Open Settings and turn on Per-Game VMUs, set to VMU A1 or to all VMUs, before your library grows. Each game then gets its own VMU file, and a problem stays inside one game. Also enable the VMU screen display for the first socket: a few games, Resident Evil Code: Veronica among them, show real status information on that little LCD. Then build the backup habit: copy the data folder, VMU files included, to a second location whenever you add games.

Step 5: Renderer Settings With Restraint

Flycast’s settings tree is deep, and the Ally’s screen argues for touching very little of it. Start with the Graphics API on Vulkan: it is the renderer the per-pixel sorting mode is built around, with OpenGL as the fallback.

Internal resolution is a multiplier of the Dreamcast’s native 640 by 480 output. On the Ally’s 1920 by 1080 panel, 3x renders 1920 by 1440, which already fills the frame height; pushing higher is supersampling the panel cannot show. Treat 3x as the ceiling and 2x as the drop if a game stutters, rather than reaching for frame skipping. Transparent Sorting decides how faithfully translucent objects layer: Per-Triangle, the default, is the sensible baseline, and Per-Pixel resolves glass, water and smoke exactly as the hardware intended, at real cost, so raise it per game when transparencies visibly break. Leave the DSP audio emulation and threaded rendering on, and keep texture filtering at its default, because the project wiki warns that forcing a filter globally can glitch games. Widescreen deserves the same restraint: prefer per-game widescreen cheats where they exist, and keep honest 4:3 for 2D-heavy games.

Step 6: Two Layers of Controller Mapping

Controls on the Ally have two layers, and confusing them is the common dead-buttons cause. The first layer is Armoury Crate’s operating mode: the built-in pads must be in Gamepad mode, not Desktop mode, or Flycast sees mouse and keyboard input instead of a controller. The second layer is Flycast’s own Controls settings, where each connected device is mapped per profile.

Map the analogue triggers deliberately. The Dreamcast pad had proportional triggers, and its racing and shooting games were built around that range; a mapping that treats them as plain buttons loses it. Docked, an external pad or arcade stick maps the same way through the same screen.

Naomi and Atomiswave in Brief

The same Windows build also emulates Sega’s Naomi, Naomi 2 and Atomiswave arcade boards. They are stricter than the console: each board needs its own BIOS archive, naomi.zip, naomi2.zip and awbios.zip, dumped from your own boards and kept zipped in the data folder, and the games load from MAME-format sets rather than disc images. This site’s dedicated Naomi and Atomiswave with Flycast guide covers board setup in depth; treat the arcade side as a second project once the console library runs well.

Online Play, As the Project Documents It

Flycast’s standalone build carries real netplay, which the RetroArch core does not expose. It offers rollback netplay for fighting games, and it emulates the Dreamcast’s modem and broadband adapter so surviving titles can reach the community servers that replaced Sega’s network, principally Dreamcast Live and DCNet. Support varies by game, the servers are community-run rather than official, and a wired dock connection is the stable way to play.

Power Modes and Battery, in Words

Armoury Crate’s performance modes trade fan noise and heat against battery life, and Dreamcast emulation sits at the light end of the Ally’s workload. The quieter, lower-power modes are its natural home: they keep the fans down during long sessions, and the standard performance mode is headroom you will rarely need. The Ally X stretches the same sessions further on its larger battery. Reserve the turbo mode for docked play on the charger.

Gear That Fits the Ally Setup

SanDisk 1TB Extreme microSDXC Card

SanDisk 1TB Extreme microSDXC Card

SanDisk 1TB Extreme microSDXC Card

Check price on Amazon

The Ally’s card slot is the easy way to carry a CHD library without touching the internal drive.

Specs:

  • Model: SDSQXAV-1T00-GN6MA
  • Capacity: 1TB, microSDXC UHS-I
  • Speeds: up to 190 MB/s read and 130 MB/s write, as SanDisk states

See it on Amazon

Samsung T7 Portable SSD 1TB

Samsung T7 Portable SSD 1TB

Samsung T7 Portable SSD 1TB

Check price on Amazon

A fast pocket drive for moving the Flycast folder, library and VMU backups between the Ally and a PC.

Specs:

  • Model: MU-PC1T0T/AM
  • Capacity: 1TB
  • Interface: USB 3.2 Gen 2
  • Speeds: up to 1,050 MB/s read and 1,000 MB/s write, as Samsung states

See it on Amazon

JSAUX 6-in-1 Docking Station HB0609

JSAUX 6-in-1 Docking Station HB0609

JSAUX 6-in-1 Docking Station HB0609

Check price on Amazon

A dock turns the Ally into a desk machine with wired networking, the stable route for netplay.

Specs:

  • Model: HB0609
  • Video: HDMI output for an external display
  • Networking: Gigabit Ethernet
  • Ports: USB-A and USB-C expansion
  • Charging: USB-C power delivery pass-through

See it on Amazon

Xbox Wireless Controller, Carbon Black

Xbox Wireless Controller, Carbon Black

Xbox Wireless Controller, Carbon Black

Check price on Amazon

The zero-fuss external pad: Flycast maps it without complaint, and its analogue triggers stand in for the Dreamcast’s.

Specs:

  • Model: QAT-00001
  • Connection: Bluetooth and USB-C wired
  • Controls: hybrid D-pad, Share button, analogue triggers
  • Power: 2 AA batteries

See it on Amazon

MAYFLASH F500 Elite Arcade Stick

MAYFLASH F500 Elite Arcade Stick

MAYFLASH F500 Elite Arcade Stick

Check price on Amazon

The Dreamcast library leans on fighters and shooters born in arcades, and this stick ships with genuine Sanwa parts as standard.

Specs:

  • Lever and buttons: Sanwa Denshi parts
  • Case: metal panels with an acrylic artwork layer
  • Connection: wired USB

See it on Amazon

How to Choose

Choose your setup by what you will actually play. A console-only library needs the stable build, a real BIOS dump, per-game VMUs and 3x resolution, and nothing more. Fighters argue for the arcade stick and a wired dock for netplay. A big library argues for the microSD card and CHD files from the start, because reorganising later means moving everything twice.

Who Should Skip

Skip this route if you do not own a Dreamcast and its games: the BIOS and the disc images legitimately come from your own hardware, and without them there is no library to set up. Skip the tweaking if your games already run the way you like on defaults, and skip the nightly builds unless you are chasing one specific fix. If you want a Dreamcast emulator with no settings tree at all, this is the wrong program; Flycast’s depth is the point.

FAQ

Do I need a BIOS file for Flycast on the Ally?

Not strictly. The built-in replacement BIOS starts most Dreamcast games with no files added. A dump from your own console, dc_boot.bin and dc_flash.bin in the data folder, is still the most compatible route and restores the authentic boot sequence. The Naomi and Atomiswave boards are stricter and require their own BIOS archives.

Why do my games not respond to the Ally’s controls?

Almost always the Armoury Crate operating mode. The built-in pads must be in Gamepad mode; in Desktop mode they send mouse and keyboard input, so Flycast sees no controller. Switch the mode first, then check the mapping in Flycast’s Controls settings.

Why did all of my games stop saving at once?

Because they share. The default setup points every game at the same VMU files, so one full or corrupted vmu_save_A1.bin blocks saving everywhere. Enable Per-Game VMUs so each title gets its own file, and keep a backup of the data folder.

Can I play Dreamcast games online on the Ally?

Yes, within limits. The standalone build offers rollback netplay for fighters and emulates the console’s modem and broadband adapter, reaching the community-run Dreamcast Live and DCNet servers for the titles they support. A wired connection plays best.

Final Verdict

On the ROG Ally, Flycast needs no workarounds: the standalone Windows build installs like any PC program and keeps its full feature set, netplay included. The setup that lasts is a short one: stable build in its own folder, a BIOS dumped from your own Dreamcast, per-game VMUs on before the library grows, Vulkan at 3x with Per-Triangle sorting as home and Per-Pixel as the per-game fix, and the data folder backed up.

Explore Our Guides & Free Tools