Got it working under Mame-lr2003, but not sure why. See the ending of this thread for my post about it.

@dankcushions that worked perfectly! thank you for the assistance.

@Lummox-JR So if you're not wanting the Bluetooth USB either, I'd recommend checking this out :

https://github.com/RetroPie/RetroPie-Setup/wiki/Sound-Issues#using-a-usb-audio-device

@AGMspokesman If you have a question, just open a new topic - don't necro-post on 2 years old ones.

@Striderx99 hi bro. How did you go about adding WCW here comes the bang? The files I find are for project 64 with a full conversion kit but can't seem to find the basic rom. Any help or guide you can give me would be most helpful. Thanks

It doesn't.

Atari 5200 controllers aren't implemented at all. There is no analog input into the system.
If you use something with analog, it's converted to digital first, which is why so many games don't work properly (Super Breakout, Missile Command, etc)

Basically it's an Atari 800 emulator (Which had digital 2600-style joysticks and a keyboard) with some 5200 stuff slapped-on.

If you have a keyboard attached, Numbers work from the keyboard. For instance, LEO in countermeasure is 123.

Please add more info about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.
Changes in RetroArch's configuration are not saved automatically, you need to either save a configuration override (for the Core used or for the Game) or - if you want to change an option globally - use the RetroArch entry in the RetroPie system and save explicitly the configuration.

Script works and i havent black videos. Thanks!!

@grzzlybr said in ROMs do not launch:

@mitu True, although obviously many people have it running fine from a desktop session (I did before these issues).

Sure, but that's not a configuration that's tested and supported.

I have just tried running RetroPie from boot and it seems to be working fine with local ROMs, but not with ROMs using symlinks (which were working fine before). So I guess that's one issue (sort of) solved and another found!

Can you add more details - and possibly the log file asked earlier, not that Runcommand should be working again ?

@Loque said in To play games of years 2000:

Which is the cheaper Raspberry that can run DreamCast games smoothly?

A Pi4 maybe, when it's going to be supported.

And why GameCube cannot be emulated with retropie?

Because the hardware is not powerful enough to run the GameCube emulator (Dolphin).

It may be a power issue - are you using a proper power source ? Can you try and test your controller via jstest to see if the buttons/d-pad/joysticks are registering ?

@polishedball https://github.com/RetroPie/RetroPie-Setup/wiki/Runcommand#adding-custom-launching-images. This shows how to get launching images setup for each system.

For Naomi and atomiswave you'll need to use lr-flycast and have the right bios. See here: https://github.com/retropie/retropie-setup/wiki/Dreamcast.

Also wanted to say it's great you decided to build your own image, you'll learn a lot more this way.

@bombers821 it is illegal to sell retropie especially with roms already included. 3rd party images are not supported here. If you would like support here you will need to download the official supported image (https://retropie.org.uk/download/). If you want support for you're current image you'll need to ask the person who sold it to you for help.

Thank you, thank you, thank you.

I looked up how to get into service mode and is f2. I have my hotkey input_save_state set to f2. One time, I must have not hit the hotkey.

And now I'm going to re-map these buttons.

@tackett1980 Cool.. you know, I'm just gonna say the difference in bios files might be a wild goose chase.. so only search for mine if you're really bored :P Hopefully the reicast folks will address the build issue with the stable branch on rpi3.

@mitu switching the controller to the switch mode, which I didn't realize would even pair, fixed the loading issue. Crazy!
It does introduce some input lag but still very usable.

Thanks so much!

Try using the Sound configuration in the RetroPie system (or using raspi-config) to force the sound on the HDMI or the 3.5'' jack.

This is a RetroPie dedicated forum, I don't think this topic belongs here - though some of the forum users might have a 3DS and some experience using it, you'd be better off asking in a dedicated Nindendo 3DS forum.

I'm using the following setup:

Raspberry Pi 3 Model B
RetroPI: 4.5.1
Retroarch: 1.7.6