Dreamcast reicast not starting

Efriim

/opt/retropie/emulators/reicast/bin/reicast-joyconfig
should give an output like this.

Here's your mapping file:
Save this as "~/.local/share/reicast/mappings/Sony PLAYSTATION(R)3 Controller.cfg"

[emulator]
mapping_name = Sony PLAYSTATION(R)3 Controller
btn_escape = 314

[dreamcast]
btn_a = 304
btn_b = 305
btn_x = 308
btn_y = 307
btn_start = 315
btn_dpad1_left = 546
btn_dpad1_right = 547
btn_dpad1_up = 544
btn_dpad1_down = 545
axis_x = 0
axis_y = 1

[compat]
btn_trigger_left = 310
btn_trigger_right = 311
axis_x_inverted = no
axis_y_inverted = yes

that is what the controller_xpad.cfg should look like, or maybe it uses a different map file title.

cmatteod

@Efriim thanks. I used the Reicast controller configuration tool through Retropie setup rather than running the script. I'll try this to see if there is a different output.

Just as an FYI I'm using a wireless SNES controller. It works when plugged in on Retroarch and used to work on Reicast until the recent update.

cmatteod

@Efriim I tried following your directions verbatim. I ran the joyconfig and got a "Save this as" and a set of names/inputs. I opened the configs folder and went to reicast mappings and created a config file that matched the name that they gave and put in the information verbatim. I launched the ROM and it did not find the controls. I'm seeing the same strange BIOS screen when I launch REICAST as well. Don't know what happened when I updated. The ROM itself MvC2 previously ran fine and the controller configuration tool in Retropie mapped my controller just fine.

I hope the next update they fix whatever they did. I have lr-beetle-dc running on my overclocked 3b+ but the rom runs slow...

I'm throwing up my hands in defeat at this point. I'll keep any eye out on this board to see if anyone comes up with a solution.

BJRetro

@cmatteod I think something is just screwed up with reicast right now. Both reicast and lr-reicast were finally in an awesome place and then all of a sudden it looks like it tanked from a bunch of posts recently with a bunch of people getting all various errors. Anyhow on the lr-beetle-dc I don’t have that version but on the old lr-reicast messing with some of the settings could get pretty close to standalone reicast (output resolution to 320 or 640, frameskip to 1- things like that - though oddly sometimes I found having frameskip on acrually made it look slower/choppier depending on the game).

cmatteod

@BJRetro if you have something that is currently stable, I would suggest not updating. The lr-beetle-dc is lr-reicast. They renamed the emulator due to legal reasons in the past 10 days or so. Output resolution is down to 640 and I've been messing with the frameskip. Even with overclocking to 1570 it still runs MvC2 slow. The infuriating part is that I can launch regular reicast with only one controller I have (Xbox 360) and it runs 100% full speed. I'll wait for another update at this point and hope that someone comes up with a fix.

mitu

@cmatteod Now it's renamed to lr-flycast, from lr-beetle-dc.

Efriim

@cmatteod
Your other controller should work.
Plug in a SSH and or get connected to the command line interface.

This will list all the controller configs and the date modified in that directory, you should see one for the xbox pad, one of them should be there for the snes pad too.
ls -la /opt/retropie/configs/dreamcast/mappings/

Running this script and inputting the right buttons will give you everything you need to edit the controller_~snespad.cfg. This joyconfig will ask which connected device you want to map so make sure the snespad is connected first. The mappings go in this order; answer y/n and then give the input with the controller: (Close Emulator)(A)(B)(C)(D)(X)(Y)(Z)(START)(DPAD1-LRUD)(DPAD2-LRUD)(TriggerL)(TriggerR)(Analog-XY).
/opt/retropie/emulators/reicast/bin/reicast-joyconfig

Once completed it will give you a config with the appropriate key numbers associated with each button press, all that needs to be done is edit the correct controller_~.cfg file with these updated mappings.
nano /opt/retropie/configs/dreamcast/mappings/controller_~.cfg
Obviously replace the controller_~ with correct filename.

You could also access the mappings folder through samba \configs\dreamcast\mappings.

cmatteod

@Efriim I tried this and still no luck. I have two RB 3b+. They are identical in every way except one is updated with the newest version of reicast while the other one is not. I copied and pasted all controller config files over and tested the exact same controllers using the same ports. The controllers work on my device that hasn't been updated but will not work on the newly updated device. I tried following the steps and the controller config file mirrors the output that was given to me. Still nothing.

As a workaround, is there any way to revert back to the prior version of Reicast or import the version of Reicast I am running on my other Pi to the one that has been updated?

mitu

@cmatteod said in Dreamcast reicast not starting:

As a workaround, is there any way to revert back to the prior version of Reicast or import the version of Reicast I am running on my other Pi to the one that has been updated?

If an update from binary (which might not have the latest version) does not solve it, you can just copy the /opt/retropie/emulators/reicast folder from the working system to the other.

cmatteod

@mitu how do I access this folder using windows via my laptop? Both Pis are connected to my network, so it should be as easy as drag and drop. However, the only folders that are visible when I open the PIs are Bios, Configs, Roms, Splashscreens.

I apologize for so many questions and being a Noob at this. Trying to learn as much as I can on my own. This forum is an amazing resource and again I sincerely appreciate the help

Efriim

reicast unknown version

You can use winSCP or SSH

What OS are you using? windows 10 has SSH builtin, otherwise download puTTY.
Enter the IP address and connect to the terminal, I don't know if you can push with the SSH but you can copy the binary to the BIOS folder then run this command to move it over and give it right permissions.

cd /opt/retropie/emulators/reicast/bin && 
sudo mv reicast reicast-backup && 
sudo mv /home/pi/RetroPie/BIOS/reicast-legacy ./reicast &&
sudo chmod +x reicast

that will copy the binary 'reicast-legacy' from the BIOS folder and rename it to reicast

mitu

@cmatteod said in Dreamcast reicast not starting:

I apologize for so many questions and being a Noob at this. Trying to learn as much as I can on my own. This forum is an amazing resource and again I sincerely appreciate the help

No need to apologize, that's why the forum exists.
As @Efriim said, enable SSH and use WinSCP to access the whole filesystem on the PI, the folder I mentioned does not appear in the file shares you can access from your PC.

ilkayefe

Hi, i have this issue too.I have tried a lot of BIOS and the methods that you gave but still same result. Can somebody help me?

mitu

@ilkayefe said in Dreamcast reicast not starting:

Can somebody help me?

Please add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first about your system better explain your issue.

ilkayefe

@mitu Hi my system information is;

Pi Model or other hardware: 3 B+
Power Supply used: Official Rpi power supply(5V, 2.5A)
RetroPie Version Used: 4.4.13
Built From: Pre made SD Image on RetroPie website
USB Devices connected: Only controller
Controller used: Microntek Controller
Error messages received:
Log found in /dev/shm/runcommand.log:

Parameters:
Executing: bash "/home/pi/RetroPie/roms/dreamcast/+Start Reicast.sh"
glGetError 0x500
Compiled
Compiled

Emulator: reicast

Efriim

@ilkayefe
Hi ilkayefe.

I'm not sure about that error, I think it is normally within the function of the emulator to give those when it is working. Yes I too get the same log.

Now it isn't asking for the dc-bios so you probably got those okay
\BIOS\dc\dc_boot.bin and dc_flash.bin
If you are at the same screen that OP shared with us, prior to my knowledge it is in fact the newest GUI that has been added to the reicast emulator. It has some new configurations and they are well organized in the settings.

The first thing though is the controller. For some controllers, I think the reicast mapper is working, though you will need to either start it through SSH
sudo RetroPie-Setup/retropie_setup.sh
or plug in a keyboard to the Pi in order to answer the input queries.
Enter RetroPie setup
Configuration / tools >> reicast >> Configure input. Once it is complete I had to run the reicast gui mapper to change the dpad mappings. I believe left and right were swapped with up and down, while it is still able to navigate (tilt your controller 90 degrees if it helps you visualize) mapping in the gui might be able to be completed foremost by default. If using retropie reicast configuration; while it asks for left-right-up-down try answering with up-down-left-right.

One of the other reicast settings that you will want to change to get much improved performance:
Advanced tab > SMC Checks = Faster
The omx audio backend I think has been improved, but I think this is still chosen by instance of the runcommand emulator selection.

would you mind updating the RetroPie-Setup script to 4.4.14 and then updating reicast as well?
Let me know where this falls off the tracks, and I'll try to pick it up again.

ilkayefe

@Efriim
Hi Efriim,

I have updated RetroPie-Setup script to 4.4.14, but and changed controller input but i got same result.

Efriim

@ilkayefe
I'm sorry, what is it that is resulting.

I had forgotten.

There are somethings that I can't know if you tried. Did you use the retropie setup > configure > reicast > input?

Efriim

@ilkayefe
There is at least some information that is needed from the reicast input config.

0: Logitech Anywhere MX (/dev/input/event0, usb-3f9800000.usb-1.3:1)
1: Logitech K400 (/dev/input/event1,
2: Logitech K350 (/dev/input/event2, ...
4: Sony PLAYSTATION(R)3 Controller (/dev/input/event4, ...
Please enter the device id:

I think with the full name of the controller we can use that

Connect to samba and find the file located at \configs\dreamcast\mappings
the file will be named something like 'controller_microntek.cfg'
just change the name to 'evdev_fullnameofcontroller.cfg'

for example my config is "evdev_Sony PLAYSTATION(R)3 Controller.cfg" it includes spaces different from its correspondent.

Additionally if this doesn't quite work out, then the input mapping will need to be inserted as well, following through with the reicast input config will tell you the button numbers that correspond to the button.

ilkayefe

@Efriim
Hi again,
I entered to the reicast input screen from SSH and i got this screen;

0: Microntek              USB Joystick           (/dev/input/event0, usb-3f980000.usb1.1.2/input0)
Please enter the service id:

And when i enter to the /opt/retropie/configs/dreamcast/mappings/
i saw a file about my controller named "controller_MicrontekUSBJoystick.cfg"
So what should i do now?