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?
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?
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.
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 and Vulkan rendering. To toggle this, there is a checkbox with the label Use Vulkan Rendering. Try turning it on and off. Ideal settings depend on your video card.
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 playing a game that is prone to desyncs after a period of time, you can correct these by "resyncing" with your opponent to a common savestate made just after a game's boot sequence. You can do this by hitting the Quick Load button (Backspace by default in Flycast Dojo 0.4.2.0)
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.