Reicast stopped working after update

sreisig1

I had Reicast working fine using the version that came on the newest Retropie image. Decided to update my emulators through the Retropie setup script (tried both binary and source) and my Reicast no longer works. Used same bios files. Bios files are named correctly and in the bios folder. They are also in the data folder. When I go to launch system manger or a game it goes black and the back to emulation station eventually. Didn't do this when I was using whatever version came standard on the newest Retropie image. Anyone else experiencing this?

sreisig1

Tried to run systemmanager, didn't work. Took a look at my runcommand.log and this is what it says:

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: 1005 Aborted
aoss "$rootdir/emulators/reicast/bin/reicast" $params -config config:image="$ROM" >> /dev/null

nowonch

I am surprised that no one has wrote back to you yet. I have the exact same problem since the update as well.

racmac

Hola a todos, soy nuevo en este foro y quería comentar que tengo el mismo problema que el compañero sreisig1. Pose una raspberry pi3 con la imagen anterior 3.7 funcionaba correctamente el System Manager de la dreamcast, desde que actualizé a 3.8.1 me dejó de funcionar.
Un saludo

BuZz

@racmac This is an English language forum

ronlaws86

I'm also having the same issue, Updated recently and now STD::Logic Error :( all i know based on my limited programming knowledge is this is a C++ error, something that's using the std namespace is kicking back an issue, could be a dependancy issue of some sort? (i'm speculating)

sreisig1

Yea, something is obviously wrong since it's not an isolated incident. Hopefully they'll have a fix or someone who knows about it can comment soon.

nowonch

I'm thinking about reflashing my sd. It should allow the reicast to work.

sreisig1

@nowonch

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"