EDIT: Well, this guide might be a bit out of date now. Still relevant, but some fine details might have changed. FFB support is now part of the FFBplugin main release, for one.
Guide to running ID3 on Flycast, including a section on LAN 
Results:Flyinghead is updating the builds a few times a week, he's really working fast. I’ve had a few graphical glitches, but basically everything is pretty much perfect. Eventually there will be a Flycast mainline release but that might be a way off.
Downloads:At present you need one of the dev builds of Flycast. The build from 15th April works. newer builds will almost certainly work fine, older builds may not. Scroll down this link.
https://flyinghead.github.io/flycast-builds/The initdv3e.zip and gds-0033.chd from MAME 0.241 will work but older Demul sets probably don't. You also need the naomi.zip and naomi2.zip BIOS files from the MAME romset. Older MAME versions probably work but I haven’t tested.
Run Flycast:It's easiest to put flycast.exe into its own directory, but this is up to you. Run flycast.exe. Close it with Alt-F4. You now have some new directories where flycast.exe is. Put the BIOS files into the /data folder. Put initdv3e.zip into /roms and gds-0033.chd into a directory called /roms/initdv3e (you will need to make this directory. It must be named the same as the .zip file for each game).
Open flycast.exe. Alt-Enter to go fullscreen if desired. Click settings in the top right, go to the general tab. You need to set your content path (roms directory) and your home directory (main directory where flycast.exe is). Now see if the ID3game will load. Might take a minute or so to get to the intro screen. If you get an error, you likely either have the wrong rom or CHD or didn’t get a dev build of flycast.
Map Controls:Open flycast exe, load ID3 and hit Tab key while the game is running, go to settings and go to controls – this way each input is labelled for that game. Set your controller to “A”. Go in to map it, change the top right box from Dreamcast to Arcade. You only need the captioned entries in the list – Handle (wheel), Shift Up, Shift Dn, etc. Along with Coin, Start, Card, of course. Those later ones won’t be specially highlighted.
The accel/brake expects you to be using a split axis (like the triggers on a controller) so the best I have been able to do is binding half of each pedal axis until I find out how to change my G25 to combined pedals using a bat file. If you want to reverse the axes, hold a pedal down, click map, and then release once the capture screen comes up.
Flycast is set up for controllers. Wheels work fine, but you probably want to go into the "mappings" directory where flycast.exe is. Open the file for your controller, and look near the bottom. Change the entry "dead_zone" from 10 to 0 or 1. (Thanks to Alexvgz for that tip).
FFB:Boomslang has updated the plugin a number of times. You need to enable broadcast outputs, but beyond that i would recommend the TP discord, palace chat channel to FFB support.
INFO IN THIS BOX IS OUTDATED
The FFB plugin is here (only works for Flycast ID3) (awesome work by Boomslang, as usual): https://discord.com/channels/284830696860680192/468497589076099082/960770150263570432 (Update: I believe the Flycast FFB plugin is now part of Boomslang's FFB plugin pack on github)
Put those 5 files into the directory with flycast.exe. Open FFBplugin_GUI and set your wheel. Open flycast and play the game.
If FFB isn’t working:
- Hit Tab key while the game is running, go to controls tab, go down the bottom, leave the controller type A as Dreamcast, but set the first options box to the right as “purupuru”, and the next one to “none”. (Thanks again Alexvgz.)
- You may need to disable other controllers on that same tab (i.e. keyboard, mouse, etc)
- Don’t use a batfile. Weird one, but FFB fails for me that way. Launch by opening flycast and clicking the game. Or, if automating, create a shortcut with the “c:\path\to\flycast\flycast.exe C:\path\to\flycast\roms\initdv3e.zip” line as the target. You can then load the shortcut from a batfile and it works fine. Must be something to do with how the arguments are being passed?
- Taking the 200MB+ .bin file from the older Demul romset and adding it to the initdv3e.zip file might help. If that isn't enough, try adding the .pic file too (overwrite the one in initdv3e.zip). Note that you should not need to do this at all, but Demul FFB didn't work with the MAME romset, so it's something to try.
- update 24/7/22 there are reports in the FFB thread that dropping the FFB files in the directory stops xinput controllers working for some ppl. I'll try to post up more info.
LAN:DO NOT go into the game test menus. You don’t need to. At least for this guide.
Make sure your two PC's are on the same subnet, as with any other LAN setup.
Open flycast.exe on cab1. Go to settings, go to advanced tab. Set Broadband adapter on, set Naomi Networking on. Set run as server on. Leave the port alone and UPNP on. (GGPO is netcode rollback for fighting games, not used here. Leave it off)
Copy the whole flycast folder you created above to your second machine.
Open flycast.exe on cab2. (Go to settings, go to advanced tab. Set Broadband adapter on, set Naomi Networking on.) Set run as server off. Leave the port alone and UPNP on. Enter the IP of the server to be the IP cab1 is set to (cab1 being the machine set to server).
Run both instances of flycast within ten seconds of each other and they should link.
(Using a single PC to run two instances, i got network running by simply leaving the IP field blank on the second instance. The port option did not exist then, so if it fails, maybe change that by one number.)
Updating:You should be able to grab a new dev build and just drop the flycast.exe in place of your old one. If it's been too long between updates, you might need to set flycast up again, but most of the time it works fine.[/list]
Home
Help
Search
Login
Register
Send this topic
Print
Topic: Flycast Naomi2 - with Initial D 3 setup & LAN guide (Read 21286 times)
