com.fightcade.Fightcade on Flathub.org
com.fightcade.Fightcade.Wine extension on Github
In the appropriate subdirectory under ~/.var/app/com.fightcade.Fightcade/data/ROMs/
Flycast accepts BIOS files in its subdirectory, but the flycast/data/ directory is mapped to ~/.var/app/com.fightcade.Fightcade/data/config/flycast/data just in case you'd prefer to put them in there.
This issue happens on Nvidia sometimes, you'll need to install the GL32 Flatpak version of your Nvidia driver. See this link for instructions.
Override the USE_DXVK environment variable using Flatseal or any similar tool. When set to true Fightcade will automatically install DXVK at launch.
Please ensure that your hardware is DXVK capable (Vulkan support) before doing this.
If you are having issues in gaming mode (such as replays not opening) please install com.fightcade.Fightcade.Steamos.
This is an optional extension that improves compatibility with SteamOS.
Please report any SteamOS-specific bugs in that repo's issue tracker
Extract the zip with the json files directly into ~/.var/app/com.fightcade.Fightcade/data
There is a logfile located at ~/.var/app/com.fightcade.Fightcade/data/frm.log. Use tail -f from a terminal to follow it live and ensure it is working.
Make sure to have the controller plugged in before running Fightcade. Flatpak currently doesn't support USB hotplugging.
If Flycast is laggy try disabling vsync.
If you install the Fightcade Flatpak but find it's still trying to launch another version of Fightcade, remove the following files and try again (might require a reboot)
~/.local/share/applications/Fightcade.desktop
~/.local/share/applications/fcade-quark.desktop
Join the official Discord at https://discord.gg/EyERRSg and ask in #linux-version