Dreamcast reicast not starting

Efriim

@cmatteod said in Dreamcast reicast not starting:

From there I opened the reciast controller mapping configuration from retropie setup

What you're gonna have to do, is exit to the command line by pressing F4, (or open an alternate terminal with SSH) and run this binary directly.
/opt/retropie/emulators/reicast/bin/reicast-joyconfig
When this is done it will display the list of input keys that need to be copied to one of the controller configs at, write it down or open up the appropriate file in samba with **programmer's notepad/notepad++/edit+/notepad2/notepad3/akelpad or nano
/opt/retropie/configs/dreamcast/mappings/controller_~xbox360
and enter the key values from reicast-joyconfig.

The joyconfig used to save the configuration but now it doesn't, and last time I checked (a month ago) the reicast source was broken. So only the binary install will work.

cmatteod

@Efriim ugh ok. I'll give this a shot tonight. In terms of an easier workaround I tried to use lr-beetle-dc which was able to successfully launch my roms. The controls work, but the rom is running extremely slowly (MvC2). While I understand Dreamcast emulation is difficult, I was wondering if you could make any suggestions to improve speed/playability (i.e. resolution settings, Retroarch settings, lr-beetle-dc settings). I'm hoping not to overclock my 3b+. LR-beetle-dc obviously has the huge advantage of auto-controller mapping.

Also, is reicast working on a solution to the problem you described above? While I'll try the solution, it seems like a really cumbersome solution.

Thanks in advance for the help!!

Efriim

@cmatteod
reicast runs mvc2 pretty well, I don't think I made any configuration, other than setting the resolution to 640x480. Using the reicast-joyconfig will give a neat output for the keymaps and all you have to do then is copy the values to the controller.cfg in configs/dreamcast/mappings/. It would be a good idea to make a backup of this controller config, because I think it will get overwritten if you use the reicast-joyconfig or binary update or input config or something will do it anyway make a backup.

cmatteod

@Efriim will this work on any controller? For example, I am thinking about using my retropie in a modified Arcade 1Up cabinet and have a Qenker arcade kit with corresponding USB encoder that I plan on connecting to my 3B+. My existing one works fine with this setup. I assume once I run the reicast-joyconfig I just take those values and insert them into the base controller mappings config file?

Sorry if my questions seem relatively straightforward. I am a total noob and only understand the basics.

Efriim

@cmatteod
In the network share for configs. If you look in this folder \\\configs\dreamcast\mappings; there is a controller_~.cfg for each controller. It would be easy to do the same thing for a different controller, all that needs to be done is copying the corresponding keymap numbers to the automatically generated config. It must come up with the config from somewhere but as is the case with PS3 controllers and the sixaxis driver, the manual entry is required.

cmatteod

@Efriim I see. Ok I'll give it a shot tonight with my existing controllers in order to make sure this works. One follow up question, if I am using two controllers in two different inputs (or using a bluetooth adapter to use multiple Xbox 360 controllers through one USB port), will I have to go into emu.cfg and mess with the [input] text? Currently example on github is:

evdev_device_id_1 = 2
evdev_device_id_2 = 3
evdev_device_id_3 = -1
evdev_device_id_4 = -1
evdev_mapping_1 = /opt/retropie/configs/dreamcast/mappings/controller_Xbox360WirelessReceiver(XBOX).cfg
evdev_mapping_2 = /opt/retropie/configs/dreamcast/mappings/controller_8BitdoSNES30GamePad.cfg
joystick_device_id = -1

Let's say I have a wireless receiver for two Xbox controllers both connected to USB port 2, would both evdev_device_id_1 and _2 both be =2?

Again, thank you in advance. Just trying to get a full understanding of how Reicast works with controllers so I can change them based on circumstance.

Efriim

@cmatteod
If they are the same controller, only 1 input configuration should be needed for that controller type. The emulator should work with both controllers without needing to add anything more than the map. I can't guarantee the performance of all bluetooth adapters, but it will definitely identify as two separate controllers.

So far I think that the controllers must be turned on and synced before initializing the emulation, if one of the controllers dies or goes to sleep then the input will not be registered on re connection for this emulator. Was just a topic I was going through, so far this reconnection problem is only with most standalone emulators and controllers. None of the libretro Retroarch emulators share this problem.

ScrumpyDaniel

Thanks for the help guys. Will try the options when I next get a chance. Do we think the screen I was getting to on Reicast was because the controllers weren’t mapping correctly?

Efriim

@ScrumpyDaniel
I think it was the Dreamcast Bios, I don't know if it has a special name. It looks like a loader type for modded dreamcasts, or maybe it is a graphical interface for reicast I haven't seen it before. It should be safe to use a regular BIOS.

It could be the cdi image you were using, contained this data.

Of course, you're welcome.

robsonink

I have the exact same issue, it’s driving me nuts!

cmatteod

I tried the steps suggested last night and was unable to resolve the issue. I went into joyconfig and followed the instructions. It spit out the following:

296 (BTN_BASE3).
288 (BTN_JOYSTICK).
289 (BTN_THUMB).
291 (BTN_TOP).
290 (BTN_THUMB2).
297 (BTN_BASE4).
0 (ABS_X).
1 (ABS_Y).
292 (BTN_TOP2).
293 (BTN_PINKIE).

I then cross referenced this with the controller config file that was generated in the mappings folder. All buttons were identical. They didn't include the text. I tried to run Reicast with the new mapping and it was unsuccessful. I then cut and pasted the text above to create a new controller config. Still nothing. The lr-beetle-dc emulator is running and finding my controller fine (albeit the emulation is slower than reicast).

Efriim

@cmatteod

/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.