Reicast stopped working after update

sreisig1

Yea, Id rather not do that, took forever for me to get my bluetooth controllers working correctly. Fingers crossed that someone posts a fix.

ronlaws86

Same here, i've put a to of work in to customising the system, including nvidia game streaming and support for my controller with a re-compiled version of xpad, i really don't what to go through all that for a 3rd time..

gizmo98

I can still not reproduce your issues. I have updated a rp3.6 and a rp4.0 rc1 installation and have still no issues. Which controller do you use?

You could also remove >> /dev/nullat the end of aoss "$rootdir/emulators/reicast/bin/reicast" $params -config config:image="$ROM" >> /dev/nullto get more debug info.

ronlaws86

@gizmo98 The controller I'm using is the afterglow Prismatic Xbox One controller (https://www.amazon.co.uk/Afterglow-Prismatic-Wired-Controller-Xbox/dp/B00ZJRHSRW) the currently bundled version of the xpad driver shipped with the kernel does not have the device ID for this controller so it's not possible to use it with xboxdrv or the packaged version of xpad; the ID was added to the latest version on github, but this won't find its way in to the kernel until the next release is pushed out with Rasbian.

(i did a thread about it here https://retropie.org.uk/forum/topic/3200/afterglow-prismatic-wired-controller-for-xbox-one/2 )

sreisig1

I use two 8Bitdo NES30 Pros and a wired keyboard

gizmo98

Sounds like a interesting controller if even retroarch controller config autogeneration does not work :-D The reicast controller config script is much more fishy because reicast ist the only emu which uses event devices with completely different button numbers. Could be a problem with your controller config file.

ronlaws86

@gizmo98 Which file am i removing this from? hopefully i can pull up some more output for the std::Logic_error

gizmo98

And 8Bitdo controllers are also known for special controller config script hacks for different firmware versions. If possible try to test with another controller. If reicast runs we need some new controller specific workarounds.

gizmo98

Just another tip. Press F4 and type...

cd RetroPie-Setup
sudo ./retropie_packages.sh reicastinput

Configure your controller from this menu and try again.

sreisig1

So this is a controller config issue you think? Even though the controllers are working for the other systems? An issue with the controller config for reicast alone would cause it to not even launch at all? What about using a keyboard? Does that not count? I've tried with keyboard plugged and and no go. Or do I need to try with another gamepad?

gizmo98

"Could be". I just do some investigations on this topic.

ronlaws86

@gizmo98
I'm not sure where to remove >> /dev/null from, I've assumed the script /opt/retropie/emulators/reicast/bin/reicast.sh

in which case, there is no more output being given than was previously to the runcommand.log which follows: -

pi@retropie:/dev/shm $ cat runcommand.log
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid
/opt/retropie/emulators/reicast/bin/reicast.sh: line 76: 21330 Aborted aoss "$rootdir/emulators/reicast/bin/reicast" $params -config config:image="$ROM"

gizmo98

@ronlaws86
Open /opt/retropie/emulators/reicast/bin/reicast.sh and edit line 69 and line 71. If there is no more output the input parameters or ini files are certainly wrong.

So there are different things which can be tested:
-run ./retropie_packages.sh reicastinput as described above to create a new controller config file
-delete /opt/retropie/dreamcast/emu.cfg

ronlaws86

@gizmo98 said in Reicast stopped working after update:

./retropie_packages.sh reicastinput

running ./retropie_packages.sh reicastinput has fixed it for me, or it's launching at least.

E: Seems fine now, How peculiar.

sreisig1

@ronlaws86 Hmmm interesting. Ill have to try it out when I get home from work later.

Hydro

@gizmo98 said in Reicast stopped working after update:

@ronlaws86
Open /opt/retropie/emulators/reicast/bin/reicast.sh and edit line 69 and line 71. If there is no more output the input parameters or ini files are certainly wrong.

So there are different things which can be tested:
-run ./retropie_packages.sh reicastinput as described above to create a new controller config file
-delete /opt/retropie/dreamcast/emu.cfg

there are no line 69 or line 71

undefined

also getting error on cd RetroPie-Setup
sudo ./retropie_packages.sh reicastinput

undefined

sreisig1

Worked for me as well. Settings controls through the supplied setup script worked for some odd reason. Games launch now. Only problem is when setting controls it asked for D pad 1 left and then up and then Dpad 2 left and up. Then asked for joystick left and up. It never asked for right and down for anything? Although Dpad seems to work fine, the joystick does not, only the up and down.

gizmo98

@Hydro
Your RetroPie-Setup script is not up to date and there are some controllers which crash reicast-joyconfig.py. It seems to be you have one of these special controllers.