- Top Pick: SanDisk 1TB Extreme microSDXC Card
- Runner-up: Samsung T7 Portable SSD 1TB
- Also consider: JSAUX 6-in-1 Docking Station HB0609
Every other Windows handheld in this class runs AMD graphics. The MSI Claw line is the Intel exception, so a Flycast setup here starts with a question the ROG Ally and Legion Go never ask: how does this emulator treat Intel Arc graphics? The honest answer shapes the whole walkthrough.
As an Amazon Associate, we earn from qualifying purchases.
What follows is the Claw route in order: the Intel picture stated plainly, the standalone build in its own folder, BIOS files from your own Dreamcast, per-game VMUs, renderer settings matched to the 1080p and 1200p panels, and MSI Center M power modes.
This article contains affiliate links, and purchases made through them may earn this site a commission at no extra cost to you.
Quick Answer
Install the stable Windows build of Flycast from the project’s GitHub Releases page, extract it to its own folder, and keep Intel’s current Arc driver installed, because the driver decides how well Flycast runs here. Add dc_boot.bin and dc_flash.bin from your own Dreamcast, enable per-game VMUs, and cap internal resolution at 3x.
The Intel Question, Answered Honestly
Flycast’s published material names no Intel exclusion. Its documentation asks for a GPU that handles its Vulkan or OpenGL renderers, and the Arc graphics in the Claw line, Arc 140V in the AI+ models, are modern Vulkan hardware. Dreamcast emulation is also light work next to the systems that genuinely strain integrated graphics.
Two honest caveats follow. First, the expensive rendering mode is per-pixel transparent sorting, which resolves glass, water and smoke exactly as the hardware did, and integrated graphics feel that cost first; treat it as a per-game fix, not a global default. Second, Intel develops its Arc driver on a rapid release cycle, so the driver version matters more here than on any AMD rival. Install Intel’s current Arc driver from Intel directly, not just the package MSI bundled; if one game renders wrongly on Vulkan, the project’s own troubleshooting advice is to switch the graphics API to OpenGL for that title.
Step 1: Install the Windows Build
Flycast offers master builds with the newest fixes, nightly dev builds that are openly experimental, and stable tagged releases on GitHub Releases. On a handheld you configure once, take a stable release. The download is an archive, not an installer: extract it into a dedicated folder on the internal SSD or a microSD card and run the executable. Flycast keeps its data beside itself, so the folder can be backed up as one unit. Adding the executable to MSI Center M’s game library keeps it one tap away in handheld mode.
Step 2: The Data Folder and Your BIOS Files
Inside the Flycast folder sits a data folder. The BIOS files live there, the console’s flash memory file lives there, and the VMU save files are written there with names that follow their controller port and slot, such as vmu_save_A1.bin. Your entire Dreamcast save history is a handful of small files in this one place.
Flycast does not strictly require a BIOS for Dreamcast games. It carries a high-level emulation of the console’s system software, and most games boot and play on that replacement with nothing added. The real dump is still the recommended route: some titles lean on exact BIOS behaviour, and only the real file restores the authentic boot sequence. Dump dc_boot.bin and dc_flash.bin from your own Dreamcast and place them in the data folder under those exact names, keeping 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. In Settings, the Content Location option has an Add button: point it at the folder holding your disc dumps and Flycast scans it recursively, so one parent folder works well. Flycast reads the standard dump formats, GDI, CDI, CUE and CHD among them.
CHD is the practical format on a Claw. It compresses each disc into one file, which suits a microSD library and makes the collection easy to move, and Flycast reads it natively. Arcade games arrive as MAME-format archives instead, with one layout rule: a Naomi GD-ROM title needs its CHD inside a folder named after the game, next to the archive.
Step 4: Per-Game VMUs, Set Once
The Dreamcast saved to the Visual Memory Unit in the controller, and Flycast emulates up to four, 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 library-wide.
Open Settings and turn on Per-Game VMUs, set to VMU A1 or to all VMUs, before the 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 back up the data folder whenever you add games.
Step 5: Renderer Settings for the Panel You Own
Internal resolution is a multiplier of the Dreamcast’s native 640 by 480 output. On the 7-inch models at 1920 by 1080, and on the 8 AI+ at 1920 by 1200, 3x renders 1920 by 1440, which already fills the frame height of either screen; anything higher is supersampling the panel cannot show. Treat 3x as the ceiling and 2x as the drop for a stubborn game.
Start with the Graphics API on Vulkan, the renderer per-pixel sorting is built around, with OpenGL as the documented fallback. Transparent Sorting decides how faithfully translucent objects layer: Per-Triangle, the default, is the sensible baseline on integrated graphics, and Per-Pixel is the per-game fix 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.
Step 6: Two Layers of Controller Mapping
Controls have two layers, and confusing them is the common dead-buttons cause on this machine. The first layer is MSI Center M: the built-in pad must be in its gamepad mode, presenting as a standard Xbox-style controller, rather than desktop mode, where it sends mouse and keyboard input Flycast cannot use as a pad. 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. An external pad or arcade stick connected through a dock maps the same way.
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.
MSI Center M Power Modes and Battery, in Words
MSI Center M is the Claw’s control room, and its power modes trade fan noise and heat against battery life. Dreamcast emulation is light work, so the lower, quieter modes are its natural home for handheld play, with a higher mode as headroom for per-pixel sorting. Battery expectations follow the model: the A1M and 7 AI+ carry the smaller batteries and suit shorter sessions, while the 8 AI+ stretches the same library furthest. For long sessions, a dock with wired networking and pass-through charging removes both limits at once.
Gear That Fits the Claw Setup
SanDisk 1TB Extreme microSDXC Card
Carry a CHD library in the Claw’s microSD slot without touching the internal SSD.
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
Samsung T7 Portable SSD 1TB
A fast pocket drive for moving the Flycast folder and VMU backups between the Claw 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
JSAUX 6-in-1 Docking Station HB0609
A dock gives the Claw a TV output, wired Ethernet for netplay and charging while you play.
Specs:
- Model: HB0609
- Video: HDMI output up to 4K at 120Hz, as JSAUX states
- Networking: Gigabit Ethernet
- Ports: USB-A and USB-C 3.2 Gen 1 expansion
- Charging: USB-C power delivery input up to 100W
Spigen Rugged Armor Pro Carrying Case
A hard-shell case with room for the charger and accessories.
Specs:
- Model: AFA07463
- Fit: Lenovo Legion Go and MSI Claw 7 AI+ and 8 AI+, as Spigen lists
- Shell: hard shell, polyurethane
- Storage: pockets for accessories and the original charger
MAYFLASH F500 Elite Arcade Stick
The Dreamcast library leans on fighters and shooters born in arcades, and this stick ships with genuine Sanwa parts.
Specs:
- Lever and buttons: Sanwa Denshi parts
- Case: metal panels with an acrylic artwork layer
- Connection: wired USB
How to Choose
Choose your setup by what you will actually play. A console-only library needs the stable build, a current Intel driver, 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 Claw for Dreamcast play specifically if you refuse to manage graphics drivers, because Intel ownership includes occasional driver maintenance an AMD handheld asks for less often. And skip the tweaking if your games already run well on defaults.
FAQ
Do I need a BIOS file for Flycast on the Claw?
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 the most compatible route and restores the authentic boot sequence. The Naomi and Atomiswave boards are stricter and require their own BIOS archives.
Does Intel Arc graphics hold Flycast back?
Flycast publishes no Intel exclusion, and its renderers run on the Arc 140V’s Vulkan support. The honest limits are narrower: per-pixel transparent sorting costs more on integrated graphics, so use it per game, and Intel’s driver updates often enough that keeping it current is part of owning this handheld.
Why do my games not respond to the Claw’s controls?
Almost always the MSI Center M mode. The built-in pad must be in gamepad mode; in desktop mode it sends 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 back up the data folder.
Final Verdict
On the MSI Claw, Flycast needs no workarounds, only one habit: keep the Intel Arc driver current. 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.











