@dash-dot I bought the adapter because for the life of me, I couldn't get my controllers paired with the bluetooth on my pi. I tried everything. Some people have had luck pairing them, but unfortunately I was one person who couldn't get the generic ones to connect. I leave my pi in one place all the time, so I don't mind having the adapter at all as long as my controllers work ! :-)

EDIT: I didn't have to calibrate anything. Plugged the adapter in and synced my first controller and the other ones followed suit just by turning the controllers themselves on. No other messing around with them ! I bought this adapter as I was new to the scene at that time and didn't know what other dongles existed for the controllers to function.

@xvo Reicast doesn't have BBA emulation support. Demul on Windows is the only DC emulator that can play online, as far as I know.

There are premade disc images for Sylverant called PSO DC Ives Pack 2.0. They're all bugfixed, online and offline capable and ready to go. Not linking them here, obviously.

I'm sure there are other private servers out there too.

@mth75 I have been struggling to get Dreamcast to load on my desktop PC with retropie. Where exactly are the system links for the BIOS files located?

It gets a bit weirder.

Despite libSDL1.2-dev being a dependancy the Makefile actually doesn't use USE_SDL=1 so it's built without it anyway! So much for my original question.

I've tried using the "update from source" option in Retropie-Setup and the newer version it builds is buggy in a similar way to my Vero4K builds. I guess the Reicast devs have a commit somewhere that's broken it a bit. So again it would be very useful to know when the Reicast binary was built? so I can pull from that time to compare.

Incidentally if the Retropie devs are reading this there is a Reicast commit "6ae93b3" which breaks it to the point of segfaulting at startup. This affected the the Vero4K and as it shares a CPU with the RPi3 it will likely break on their too, so be aware should you pull in anything newer from their repository.

@chinjw 3rd party images are not supported - please download and install the RetroPie image from retropie.org.uk/download and see if you still have problems with Reicast.

Yeah, I installed Recalbox, now my PS4 controller isn't pairing. I guess the grass isn't greener on the other side. lol

well I had my head wrapped around several problems with Reicast and controllers for the past few days. I had configured the controllers many, many times with joyconfig, editing emu.cfg, controller files for DC, etc, and I finally found the source of my problems.

The so called 'automatic configuration' is broken. No matter what you put into the config files, it gets overwritten when you run Reicast. The script tries to identify the devices configured in the OS and assign them automatically. In my case, always assigning them wrong, so anything seemed to work (keyboard or gamepad).

The only thing that worked was to comment out the line in the script (.sh) where it gets the result of the "automatic" detection and put it into the command line for Reicast call. I dont have my PI here to see exactly the script name and exact line, will try to update this post later with more details. But you get my point.

Just commenting this single line and voila, my pad started to work and I was able to get past the date/time screen, and play a game.

I have this exact same problem months later, was this ever resolved?

There are plenty of games with notes for Pi2 and no notes for Pi3. Generally means they suffer from the same issues.

@tonythetiger
That "Sniper Mode" bug is a known issue for Reicast. Check out their official compatibility list:
http://wiki.reicast.com/index.php/Reicast_Compatibility_List?wap2

I watched a YouTube video of someone on an Android phone using Reicast and they had the same issue (from 2014):

More information here and here (both are also from 2014):
https://github.com/reicast/reicast-emulator/issues/76
http://forums.reicast.com/index.php?topic=122.0

@zerojay

Perfect, if there is a pull request for it I can wait for it to be incorporated into a future update and I can update. For now, lr-reicast seems to actually be working pretty well for the couple of games i've tested.

I will have a look for the pre-compiled binary though and perhaps give it a try.

Cheers

@sagoannahs
You can also use the Configuration Editor (instead of editing /opt/retropie/configs/psx/retroarch.cfg manually)

RetroPie Setup Script >> Setup / Configuration >> Edit RetroPie/RetroArch Configurations

More information (with pictures) here:
https://retropie.org.uk/docs/Configuration-Editor/

@shaolinmatt

Did you follow the directions on the Wiki/Docs here
https://retropie.org.uk/docs/Dreamcast/

You can check the md5sum or CRC32 of your BIOS files dc_boot.bin and dc_flash.bin to verify you have the correct ones.
https://retropie.org.uk/docs/Dreamcast/#bios

If you go into the RetroPie-Setup Script you can goto Configuration / tools then to reicast - Dreamcast emulator Reicast then Configure input devices for Reicast

The location for your controller mapping config file is /opt/retropie/configs/dreamcast/mappings/

You will also need to verify that in /home/pi/.reicast/emu.cfgthat both evdev_mapping_1 and evdev_mapping_2 are pointing to the matching controller mapping configuration file(s).

Example

evdev_mapping_1 = /opt/retropie/configs/dreamcast/mappings/controller_Xbox360WirelessReceiver(XBOX).cfg evdev_mapping_2 = /opt/retropie/configs/dreamcast/mappings/controller_Xbox360WirelessReceiver(XBOX).cfg

Also, make sure that evdev_device_id_1 and evdev_device_id_2 are set to the corresponding controller's /dev/input/event* number (run evtest to find out which event number your controller is using).

Example

[input] evdev_device_id_1 = 0 evdev_device_id_2 = 1

@BJRetro thanks for your answer but really need this for other options.

Thanks

Anyone else had this issue?