@johnl52
https://gamefaqs.gamespot.com/

Many games from the last 30 years or so on consoles have guides, walkthroughs, cheat codes that can all be found there. Most of the time, a walkthrough will explain the controls for a game.

Another trick if you want to see what the instructions that came with the game look like, you can google "[name of game] manual scan".

@jmcdra I must have fixed something. It works

@popegg235 said in Can't find Drastic emulator for ds:

can anyone tell me what's the name of the drastic emulator in the retropie setup script and where i find it????

The name is drastic, it's in the experimental packages section.

@mitu i'm back if you're still here for some reason...
i tried again for the log.
here it is: https://pastebin.com/U96FjKBt

Thanks. Much appreciated.

@akamming I’m in the same boat as you as far as running an ipac2 in redream. I can’t seem to configure my input for more than one controller per port. Can you please walk me through how to get it up and running. I did read what you did for a workaround but I’m pretty new to the raspberry pi and found it a little hard to understand. Thanks in advance!

@mitu
I've never tried before to install 2016 before yesterday. I just recently finished getting the matching romset and wanted to give it a go.

I'm reading the PR and I see there is a potential fix but it hasn't been incorporated into libretro if I'm reading this right. I'll see if I can work out how the fix can be incorporated but I'm still learning the terminology workings of github.

@mitu argh! Fantastic - thank you! It was indeed the incorrect x character. 2 Player Virtual Fighter on the arcade cabinet here I come

@tango said in SDCard Unreliable - Move all RP to USB card? Or fix SD?:

Or does it do that because I have no boot sector or boot programs on my USB stick?

If you haven't programmed the OTP bit for USB boot, the Pi will always boot from sdcard.

@jambo069 said in Flycast hotkeys for retroarch:

So should I just delete the retroarch cfg and see how it goes?

Rename the retroarch.cfg from the dreamcast system (/opt/retropie/configs/dreamcast) and then immediately re-install lr-flycast, this will re-create the default configuration for the system.

There is some configuration that can be done by modifying the ALSA configuration file ($HOME/.asoundrc), but looks complicated and there's no 'one-size-fits-all' solution (depends on the devices present on the system).

You could try installing PulseAudio and configure the module-combine for simultaneous output.

@yfzdude said in Should i get Debian x64 ?:

@crush
Dolphin does require a 64-bit operating system. To fix that you need to reinstall using the x86-64 or amd64 version of the installer or image.

When any documentation here mentions x86 it is simply using it as a term to indicate PC/Laptop hardware as opposed to ARM based hardware.

Ok thanks, i had misunderstood then, and you're right, it works fine now on the x64 distribution.

Check if you haven't got PulseAudio installed. If you go into the Audio settings in RetroPie - does it show PulseAudio at the top ?

@questionmark said in Splashscreen images not displaying | omxiv erroring out:

So will this cause performance to dip?

No, it will not.

In case anyone googles and finds this ... I did get to the bottom of it by looking into the source code (by source code I mean the RetroPie ES version, stable branch)

You can see here in VideoPlayerComponent.cpp where it launches omxplayer with a bunch of args:

VideoPlayerComponent.cpp:

// Run the omxplayer binary execve("/usr/bin/omxplayer.bin", (char**)argv, (char**)env);

Now if you fire up ES, launch the screensaver, and take a look in the process list while its running (in ssh session, ps -ef) you'll actually see all those args, something like this in the process list:

pi 2143 1 7 01:16 ? 00:00:08 --layer 10010 --loop --no-osd --aspect-mode stretch --vol -3885 -o alsa --win 0,0,800,480 --orientation 0 /home/pi/RetroPie/roms/neogeo/media/videos/trally.mp4

What I noticed is the volume is set to -3885. Now if I run that on the command line to simulate the screensaver I can play with the volume. For omxplayer, volume 0 should be 100% as it's measured in millibels according to the omxplayer help.

So I quit es and ran this:

omxplayer.bin --layer 10010 --loop --no-osd --aspect-mode stretch -o alsa --vol -0 --win 0,0,800,480 --orientation 0 /home/pi/RetroPie/roms/neogeo/media/videos/trally.mp4

ok great I can hear it now! I researched %vol to db and the formula is db = 20*log(%vol) and that checks out because I had es at roughly 65% volume which equates to about -3742 millibels.

So I went back into es and set the volume to 100%, and now I can finally hear it on a default RetroPie install. The issue is the drop off is really steep (must be some bug in omxplayer on pi, that their millibels to volume curve is off) because if you set the volume level at say, 60% you won't hear much of anything from the speakers. I think this is also compounded by the fact that when you're playing around with the audio settings in es, many times it resets the volume back to zero because it's trying to sync up the level with alsa.

Anyway, hope this helps someone get their head around the screensaver audio.

p.s. also, in es audio settings, make sure you set the "omx player audio device" to alsa (or whatever works on your pi, or in your command line experiments), as that drives the argument sent into omxplayer above.

Well I finally found another image viewer that lets me specify something to display on the second hdmi port: vlc!

But although it worked fine on FKMS, nothing showed up when I ran it with KMS... not sure if I’m doing something wrong or if that is expected.

@roslof
I have the exact same problem but I can't find mame 2016 folder under the bios folder on my image-virtualman 128gb arcade but it must be there as it is an option to use to open the rom file!
Any idea why, or where it could be??

M

@greenhawk84 to be clear they’re never going to fix dispmanx/omx support. these utilise features of the original closed source gpu firmware that they have replaced with an open, more standard linux solution. it’s not all bad news, though, as there’s typically an alternative solution (eg vlc rather than omx, but you may have to re-encode/replace your videos).