R36S Dreamcast Emulation: Flycast Settings & What Actually Runs
Dreamcast is the point where the R36S stops being effortless, though it gets further than its reputation suggests — a little over half the library is playable. This guide covers the BIOS files you have probably been told are mandatory and are not, the Flycast settings that actually move the needle, the one everybody recommends that you should ignore, and an honest account of what runs.
The BIOS Is Optional, Whatever You Have Read
Almost every Dreamcast guide opens by telling you that you need dc_boot.bin and dc_flash.bin or nothing will run. That is worth correcting first, because it sends people hunting for files they may not need and it misdiagnoses failures that have other causes.
Flycast has its own built-in BIOS
Flycast ships a high-level reimplementation of the Dreamcast boot ROM, known as reios, and falls back to it automatically when no BIOS file is present. libretro's own core definition reflects this: dc/dc_boot.bin is listed as optional, and dc_flash.bin is not listed at all — Flycast generates its own flash-memory file on first run rather than reading one you supply.
So most games boot and play with no BIOS files whatsoever. The advice to treat them as mandatory is inherited from Reicast, the older core Flycast replaced.
The real BIOS is still worth adding, for a narrower reason than usual: the built-in reimplementation covers most of the library but not all of it. Supplying dc_boot.bin buys you
- the last slice of compatibility — a handful of titles check for a real boot ROM and will not start without one
- the actual Dreamcast boot animation and disc-less system menu
- MIL-CD support, for the audio-CD-based releases that used it
If you do add it, the path is /roms/bios/dc/dc_boot.bin — a dc subfolder, not the /bios/ root where PS1's file goes. Our BIOS setup guide has the paths for every system.
A black screen is not a BIOS diagnosis
Because Flycast does not need the BIOS to boot, “every Dreamcast game shows a black screen” is not evidence of a misplaced BIOS file. Look instead at whether the game image itself is sound and whether the core is loading at all — our boot and display troubleshooting guide works through black screens properly.
Which Core
Use Flycast. On a Linux-based firmware like ArkOS or Rocknix it is effectively the only viable option in RetroArch, and it is the core that has received the optimisation work for this class of hardware.
You may see Reicast listed. It is the older lineage that Flycast forked from and it is no longer the one to reach for — if a game misbehaves, the fix is a Flycast setting rather than a core swap. There is no Dreamcast equivalent of the SNES situation where several cores trade accuracy against speed; here there is one core and a handful of settings.
The Settings That Matter
Flycast exposes a long options list. Most of it will not change your experience on this device. These will, and they are worth setting before you conclude a game is unplayable:
| Setting | Value | Why |
|---|---|---|
| Threaded Rendering | On (confirm it is) | Puts rendering on a separate thread from CPU emulation, which suits a quad-core chip with modest individual cores. Flycast's own option text calls it “highly recommended” and attaches no figure to it; neither will we. It costs roughly one extra frame of input latency, and a few games have worse frame pacing with it on. |
| Alpha Sorting | Per-Strip | This is a three-way choice, not a toggle: Per-Strip (fast, least accurate), Per-Triangle (normal) and Per-Pixel (accurate, slowest). Per-Pixel is the expensive one. Per-Strip is the right default here; step up to Per-Triangle if a game shows transparency drawn in the wrong order. |
| Enable DSP | Off | Emulating the Dreamcast's audio DSP is costly and this hardware cannot spare it. The cost is fidelity: some reverb and filter effects are produced by that DSP and will be missing or thinner without it. Turn it back on for a specific game if you notice, but off is the right default here. |
| Internal Resolution | Native (1×) | Do not upscale. The panel is 640×480, so rendering above that throws away performance to produce detail the screen cannot show. |
| Frame Skip | Off, then 1 if needed | Only reach for this when a game has a real deficit. It does not make emulation faster — it draws less so the game logic can keep correct timing. |
| SH-4 CPU Clock | Leave at 100% | Widely recommended, poorly evidenced — see the note below. Not your first lever. |
The 720p advice you may have seen is wrong for this device
Guides written for more powerful handhelds sometimes suggest a 720p internal resolution. On the R36S that is strictly a loss: the display is 640×480, so every pixel rendered above native gets thrown away during downscaling while still costing the GPU to produce. Native is both the fastest and the sharpest choice here.
About the CPU clock slider
Almost every Dreamcast-on-cheap-handheld guide tells you to drop the SH-4 clock to 50%, and the reasoning sounds right: fewer emulated CPU cycles per frame means less work for the emulator, at the cost of the game's own logic running slower. We are not repeating that advice as a number, because we cannot substantiate it.
Flycast's own issue tracker contains reports that changing the SH-4 clock produces no observable difference at all — one thread compares settings across a wide range and in both the libretro core and standalone builds finds no change. That may be version-dependent, and it may behave differently in the build your firmware ships. But a setting whose effect is disputed by the emulator's own bug reports is not something to spend your time on first.
Try the levers in this order
- Confirm Threaded Rendering is on — usually the default, and the change Flycast itself recommends most strongly
- Alpha Sorting to Per-Strip and DSP off — both give back real headroom
- Confirm native resolution — free if something set it higher
- Frame skip 1 — when a specific game still falls short
- The CPU clock slider — last, and verify for yourself that it did anything
Why Dreamcast Is the Hard Boundary
It is worth understanding what makes this system different from PS1, which the R36S handles comfortably. The Dreamcast was a genuine sixth-generation console: a 200 MHz SH-4 CPU with a vector unit, a PowerVR2 GPU, and a dedicated audio DSP. Emulating it means simulating all three, and the graphics work in particular cannot be handed off cleanly to the Mali-G31 MP2.
That collides with the R36S's specific shape. As covered in our hardware breakdown, the RK3326's four Cortex-A35 cores are efficiency cores, and emulation pins the timing-critical work to one of them. Four modest cores are excellent for a 16-bit console and merely adequate here — which is why the honest description is borderline rather than broken. Enabling Threaded Rendering helps precisely because it is one of the few ways to use a second core for something that matters.
What Actually Runs
Community compatibility testing puts roughly 59% of the Dreamcast library in the playable range on RK3326 hardware — a little over half, rather than the minority figure often quoted. The number is more useful once you know the pattern behind it: 2D fighters and arcade-style games do well; open 3D worlds and anything with heavy transparency do not. Dreamcast arcade ports were often designed for fixed, tightly-scoped scenes, and those are the ones that fit.
| Game | Type | How it holds up |
|---|---|---|
| Crazy Taxi | Arcade driving | Playable — one of the reliable picks |
| Sonic Adventure 1 & 2 | 3D platformer | Playable, with dips in the busier stages |
| Soulcalibur | 3D fighter | Playable — fixed arenas suit the hardware |
| Virtua Fighter 3 | 3D fighter | Playable |
| Power Stone 1 & 2 | Arena brawler | Playable; Power Stone 2 is busier and less consistent |
| Jet Grind Radio | Action | Playable — the flat cel-shaded look is cheap to draw |
The titles that disappoint people are the ones with large streaming environments and layered transparency effects. If a game is famous for its draw distance or its water, expect trouble regardless of settings.
Set expectations by genre, not by title
Rather than hunting compatibility lists game by game, use the shape of the game as your predictor. Fixed-camera fighters, arcade conversions and flat-shaded art hold up. Open worlds, long sightlines and alpha-heavy effects do not. That heuristic will be right more often than any list, because it describes why the hardware struggles rather than cataloguing the symptoms.
Audio: Expect Some Crackle
Dreamcast is the system where the R36S's audio weakness is most audible, and two separate things are going on.
The first is not Dreamcast-specific at all: the R36S has a known crackling issue caused by power supply interference, which affects headphones less than the speaker. The second is that Dreamcast titles are simply more demanding on the audio pipeline than earlier systems, so any buffer that was marginal elsewhere becomes audible here.
Two practical steps: increase the audio buffer (Dreamcast benefits from a larger one than other systems need), and save that change as a Core Override rather than a per-game override, since it applies to the whole system rather than one title. Our audio and performance guide walks through both, including the RetroArch menu paths.
Naomi and Atomiswave
Flycast also runs Sega's Naomi and Atomiswave arcade boards, which share the Dreamcast's architecture. They do not inherit its compatibility rate, though, and they differ from each other: Atomiswave lands around 43% and Naomi lower still. Both are a rougher ride than Dreamcast proper, so treat them as a bonus rather than a reason to choose this device.
Two things differ in practice. Unlike Dreamcast itself, these boards genuinely do need BIOS files — Flycast lists naomi.zip, naomi2.zip and awbios.zip among others, all sourced from MAME — and romsets are version-sensitive in the way arcade emulation generally is — a set that works in one Flycast build may not in another. If you are coming to this from MAME, expect the same class of romset friction here — our arcade and MAME guide explains why romsets are version-locked to cores.
Realistic Expectations
Dreamcast on the R36S is a bonus, not a headline feature. If you bought the device to play Dreamcast, you bought the wrong device — our before you buy guide is explicit that anyone prioritising Dreamcast, N64 or PSP should look at more powerful hardware. If you bought it for the 8- and 16-bit era and PS1, then a working Crazy Taxi and Soulcalibur are a genuine pleasure on top of what you came for.
Two closing notes. Dreamcast games drain the battery faster than lighter systems, so budget toward the lower end of the range in our battery guide. And Dreamcast discs were large: expect roughly 200 MB to 1.2 GB per game in CHD form depending on how much of the disc was real data, which makes a roomy TF2 card worth having — see the dual SD card guide for how to set that up without touching your firmware card.
Related Guides
- BIOS Files: Complete Setup Guide — exact paths for every system
- Audio & Performance — fixing crackle and input lag
- R36S Specs & Hardware — why the ceiling sits here
- N64 Optimisation — the other borderline system
- Performance & Compatibility — every system at a glance