How do I install Flycast Dojo?
What is the preferred romset?
Where do I put my BIOS & ROMs?
When I map my controller, why am I unable to map Button 6 (Hard Kick / 2nd Assist) ?
How do I map my analog joystick to the directions?
What are the optimal settings for the least input latency? / Why is the frame pacing weird on my computer?
Does game X have a training mode?
Using the internal training mode, why do enemies still attack me/why is my health bar diminishing?
When will feature X be added?
My screen is stuck on STARTING NETWORK. What do I do?
I can't establish a connection using Match Codes, is there anything I can do about this?
Why is my opponent unable to join a game when I challenge them even though I am able to accept challenges just fine?
Why am I able to host games just fine, but I am unable join others?
How do I reset my settings to their defaults?
My mouse and keyboard are unable to make any menu selections. What do I do?
My video is just a blank screen, but I am still able to hear sound. How do I fix this?
Why is my game desyncing? What can I do about it?
Flycast crashes on launch. What do I do?
I'm playing on WiFi and my game performance is crap. Is there anything I can do to improve performance?
Wi-Fi has always worked fine for me. / My landlord won't let me access the router. / (Insert insistent Wi-Fi excuse here.)
In broad strokes:
naomi.zip) and Dreamcast/Atomiswave/NAOMI ROMs into the provided
Once you have done this, you should be ready to host or join any games. Specifics may be found in the README, or in the rest of this FAQ.
For the BIOSes, we use
naomi.zip validated against RetroArch's System.dat file. This should serve as a standard for all system BIOSes used. Dreamcast games use Flycast's built-in HLE BIOS by default.
As a general rule, players use the MAME 0.218 romset for NAOMI games, and the MAME 0.226 romset for Atomiswave games. For Dreamcast games, CHD files based on the Redump set are preferred. You may also look at the included
flycast_roms.json file to see a list of filenames and checksums corresponding with the current preferred ROMs as well.
For more information on specific games, try asking on the relevant Community Discord. They typically know what is best for competition play at any point in time.
For the BIOS, be sure to add
awbios.zip for Atomiswave games or
naomi.zip for NAOMI games into your
data directory in the folder you have Flycast installed. In your settings, the folder Flycast is installed in is your Home Directory.
If you are running Fightcade, you can find the ROMs folder at
Fightcade\emulator\flycast\ROMs. Non-Fightcade users can use the included
ROMs directory, or specify any other folder as a Content Directory in the settings.
It's likely that the button you are trying to set is configured as an axis input on your controller. On the right hand side of the controller mapping screen, there is a section called Analog Axes. Find the button you want to map, and try to assign it again.
On the Analog Axes side of your controller mapping screen, find DPad X for horizontal movement, and DPad Y for vertical movement. Once you click on Map, flick the joystick in the direction you want to map.
To improve input latency, and to ensure the correct frame pacing for monitors that run above 60Hz, you can disable VSync in your Flycast video settings and set
flycast.exe to be limited to 59.94 frames per second, either in your video card settings or an FPS limiter like Rivatuner Statistics Server. Just make sure that you and your opponent are operating at approximately 59.94 FPS to ensure proper syncing in netplay. We hope to eventually make this an internal option.
If you're playing a NAOMI or Atomiswave game, it's likely not the case by default (Akatsuki Blitzkampf Ausf Achse appears to be the exception to this rule). If there is a Dreamcast port of the game though, your best bet is finding that version and running it for training.
Flycast Dojo itself has a universal training mode to help you lab in games that may or may not have one built-in, allowing you to switch players on the same controller with a single keystroke, record/play/loop inputs, load RetroArch cheat files and savestates at will. You can access this through the Menu button (TAB by default) or through keyboard/controller mappings. For details on how to use this, check out the Training Mode section of the README.
Flycast Dojo's internal universal training mode, being applicable to all games, isn't magical. You need to load the relevant cheat files or savestate for your game to get it to the state you want. If applicable, using it in tandem with a game's existing training mode would give you the largest set of features.
When it's ready.
This is most likely a networking issue. The problem can either be on your end, or your opponent's, with the culprit usually being your router or something in the connection between you. Refer to the question below for troubleshooting tips.
In some edge cases, Match Codes don't work out of the box if someone is behind a double NAT or has a noncompliant router. Sometimes this can be resolved by switching who is hosting and who is joining. If that doesn't work, try the following:
It's possible that your computer's firewall is disallowing Flycast Dojo from sending or receiving connections. Check your Windows Firewall and make sure that
flycast.exe is able to connect to all networks and that connections are allowed, both inbound and outbound.
In your Video settings, try switching between OpenGL, Vulkan, or DirectX rendering. To toggle this, check your Video settings and change the Graphics API. Ideal settings depend on your video card. DirectX is intended for older PCs and is largely around as a fallback for older PCs.
emu.cfg file in your flycast directory. If you are using Fightcade, you can find it at
Fightcade\emulator\flycast\emu.cfg. One will be regenerated the next time you launch Flycast.
As of Flycast Dojo 0.4.1.0, upstream changes by Flycast have changed how mice and keyboards are defined. Deleting the
emu.cfg redefines them upon regeneration.
Games desynchronize when your memory and opponent's memory have mismatched, leading to two different game states. Common causes include not loading the same ROM or BIOS, having different savestates or dipswitches, or using different builds of Flycast Dojo.
First, make sure that you and your opponent are using the same version of the software. What version of Flycast Dojo you use determines the common arcade dipswitches/VMUs are, as well as individual software builds. Next, validate your ROM against your opponent's ROM.
If you are on Wi-Fi, the performance hit of it being half duplex has occasionally been known to cause desyncs between clients. It is recommended that you play on a wired network to ensure synchronization, and to generally not have a bad time.
In general, anything that can lead to a different memory state than your opponent would contribute to desyncs. For more information, check out E2xD's Desync Troubleshooting Guide. While Smash is a different scene, the causes for desyncs are much the same.
Here are a few steps to help troubleshoot and diagnose what's going on.
Sometimes, Fightcade upgrades or incompatible defaults in
emu.cfg may cause crashes. Just delete
emu.cfg from the same directory as
flycast.exe. A new one will be generated the next time Flycast is launched. For Fightcade users, this will be in the
Fightcade\emulator\flycast folder. Open Flycast after deleting the file and verify that the emulator works.
Device-specific controls were fixed in a recent bug, but may be a culprit older mappings still exist. Be sure to set your controller mappings for both "Dreamcast Controls" and "Arcade Controls". You may also want to try deleting the contents of the
mappings/ directory and mapping your controls before launching a game.
If a session isn't established within Fightcade, the client will automatically close Flycast. The firewall may be the culprit in this instance. To diagnose this, you can either temporarily disable Windows Firewall and try to start a replay or connect with your opponent. If this works, add a rule in Windows Firewall allowing Flycast to use your network.
%USERPROFILE%\AppData\Local\Temp directory for a file ending in
.dmp. If one exists at the time of the crash, send it over to us in the Flycast Discord so that we can determine the issue. If one isn't available, then it's likely that a crash technically didn't happen, but is still likely unintended behavior.
If none of the steps above worked, please run DebugView, replicate the crash, and send the log to me through the
#flycast-emulator channel on the Fightcade Discord or via a GitHub issue. Be sure to include Flycast Dojo version, your hardware specs and OS version.
Don't play on Wi-Fi. Buy an ethernet cord, or get a powerline adapter if you don't want wires running across your house.
Wi-Fi is half duplex, meaning that it can only send or receive packets at one time. This is in contrast with Ethernet which is full duplex, meaning both sending and receiving can happen at the same time. Wi-Fi also has a tendency to have ping spikes throughout a session, leading to speed issues when a connection isn't consistent.
Other games and emulators with rollback can sometimes mitigate network issues presented by Wi-Fi. In spite of this, it's generally recommended to have a wired connection when playing online, no matter what you're playing.
(These are less like questions and more like statements, but I definitely get these frequently. Please stop pestering me with this.)
As a general rule, while you may not feel the difference, your opponent most certainly does. This is why Fightcade and many popular games have a Wi-Fi detector. Everyone's trying to avoid you. In general though, the laws of physics and protocol limitations do not care about your excuses. Sorry.