The shader is already present in /opt/retropie/configs/all/retroarch/shaders/retropie/ in a default installation. You need to use the RetroArch RGUI to load it, using the Shaders -> Load Shader preset menu.
How are you trying to load the Shader ? Here's a handy

showing you how to load a shader.

@stoney66 Thanks for that.

I had a look at those cfg files and they all looked fine.

So I did a completely fresh install of RetroPie.

Tried it out, R-Type controls worked fine.

Then I started adding nice tweaks such as ES Themes etc, and suddenly R-Type had the same problem - P1 right not working unless I re-configure the MAME2003 controls every time.

Not sure what change I applied that caused this, so I'm going to do it all again step-by-step and see when it reoccurs.

My gut feeling is this is a bug in the Pimoroni Picade HAT drivers.

Here are some settings for Conker's Bad Fur Day:
~mupen64plus.cfg

[Video-Rice] #This will fix the colored black tail and a few other things. Sometimes this setting isn't found in the cfg. #I think it loads only hi-res textures for when there are far away objects it would load lo-res. LoadHiResTextures = True #This will fix the transparency of the fence. NormalAlphaBlender = True

It might be possible to add these to the .ini files for the specific game. But I'm going to move on to other things for a while and probably won't get back to this. There are some settings that improve performance and I don't know exactly which ones these were, I could post my entire plugin configuration if someone wanted it. The setting for the dancing toadstools remains to be found, maybe I imagined it.

And here are two settings for Starcraft 64:
~mupen64plus.cfg

[Video-GLideN64] #The game fails without this, however it slows down the menus immeasurably. BackgroundsMode = 1 #FBinfo needed for scroll updates in-game, however the logos at the beginning are no longer able to be seen. DisableFBInfo = False

@PCKid ok hold the horses. Just fiddled with the controller in Bluetooth ie disconnected and some of the buttons work on the controller just not all and messed up. EG analog sticks work up down left right but none of the others do. Redid buttons now all good thank the maker. Thanks for all your help. No idea why it has suddenly decided to work but it does.

I realize this topic is old now, but after recently updating the xpad driver in RetroPie-Setup, I was suddenly able to map L2/R2 in X-input mode. So whatever update was added to the xpad driver, it seems to have resolved this mapping issue, or at least how the driver reads the L2/R2 inputs on 8bitdo controllers. So this issue is now resolved for me.

I can map the "parameter" keys 0-9 by hitting "Tab" to bring up the MAME menu, and the game will work fine until I close out and re-open it....then those settings aren't saved. Does anybody else have that problem?

Does anybody know hot to get a mixer control that supports stereo on retropie?

cheers for the info. i'll go with the easy option for now.

@vinny710 Yes - the previous post: http://files.retropie.org.uk/images/weekly/.

@jackyracer thanks for the info! I had already sarted to play with individual UAE config files and looking in the XML file. I still couldn't get it to work and the controller randomly changed to parallel port 2!?!. So I deleted all the config files I had created or had been playing with and it started working! Port 0 was the mouse and port 1 was joystick and recognised on games 👍

Now I've noticed an issue, only tested Turrican but when I hit any button the game pause's then carries on when I press again, anyone seen this?

@thedavegray it should be the Button you configured as "a".
It takes some time after you pressed it, the mapping is saved and that takes some seconds.

@mitu thank you, Mitu! I bought another memory card and it works!! You're the best :)

@flower4000 I explained in the previous reply what it means: if your path element contains the folder (i.e. /home/pi/RetroPie/roms/genesis/game.md), then remove the folder part of the path and leave only the file name (./game.md).

For future internet reference........

That 'lv10 Volume Control: Failed to find mixer" error is the cryptic message that Emulationstation gives when it cannot find the Audio Mixer on the selected Audio Card. You can find more information about that in the Sound Troubleshooting instructions I wrote on the Retropie website

To solve this, we need to figure out what the name of the Audio Card is, and the name of the Audio Mixer on the Audio Card, so that we're able to correctly reference them from within Emulationstation.

Firstly, you can run aplay -l to get a list of the Audio Cards that ALSA recognises. You should get something like this (this is for an ODROID):

odroid@odroid64:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: ODROIDHDMI [ODROID-HDMI], device 0: I2S.27 dit-hifi-0 [] Subdevices: 0/1 Subdevice #0: subdevice #0

(You may have different results, just take note of the the HDMI audio card name and keep it for later.)

In our example we have an Audio Card named 'ODROIDHDMI', which is not an Audio Card type that is in the built-in list of Audio Cards in Emulationstation.

The second thing we need to do is figure out what the audio mixers are available on the audio card. For my example I run the amixer scontrols -D ODROIDHDMI command, which will show you the names of the audio mixers on the ODROIDHDMI audio card. Replace the ODROIDHDMI name with the name of your Audio Card you just got above. Based on my research you should see something similar to this:

Simple mixer control 'Analogue',0 Simple mixer control 'Deemphasis',0 Simple mixer control 'Digital',0

(Again, you may have different results, just take note of them and modify the command below as needed.)

Take a note of the names of the all the Audio mixers on that Audio Card as we'll need them later.

The next step is figuring out which audio mixer from that list actually controls the volume. On my Rpi Justboom DAC HAT, its the 'Digital' mixer. You will need to experiment to see what works for you. To test the audio mixer, you need to first make a noise out the HDMI, and then second use amixer to adjust the various mixers until you figure out which one changes the volume of the HDMI.

To make a sound out the audio device you can use speaker-test -D ODROIDHDMI -t wav -l 20 & to run the speaker test 20 times in a loop (and go into the background) (replace ODROIDHDMI with the name of your Audio Card you got in step 1). You quickly then run alsamixer to get a nice GUI for the ALSA mixer, which you can then use to adjust the various audio mixer devices on the audio card

At the end of that testing you should know the Audio Card name, and the Audio Mixer name on that card that controls the volume.

For our example, lets say the 'Digital' mixer on the ODROIDHDMI is the one that controls the volume.

So now we need to tell emulationstation how to use these new cards.

As mentioned earlier 'ODROIDHDMI' is not an Audio Card type that is in the built-in list of Audio Cards in Emulationstation. Luckily this isn't an issue for us, as the patch I added to emulationstation last year allows you to add a Custom Audio Card, and a Custom Audio Mixer (the audio mixer is called an 'Audio Device' in emulationstation).

To add a Custom Audio Card just follow these instructions and replace the <string name="AudioCard" value="default" /> line in the es_settings.cfg file with <string name="AudioCard" value="ODROIDHDMI" /> . This should allow emulationstation to successfully look for an use the ODROIDHDMI Audio Card.

To add a Custom Audio Mixer just follow these other instructions and modify the <string name="AudioDevice" value="Digital" /> line in the es_settings.cfg file so that Digital is changed to the Audio Mixer name you discovered above with your alsamixer testing.

Please note that if you change the Audio Card or Audio Device settings from within the Emulationstation GUI at any stage, you will lose your custom settings, and you will need to readd them in es_settings.cfg again as described above.

With the combination of settings above you should be getting sound when you go into emulationstation.

Hope that helps people avoid these problems again!

Cheers
Tminit

@Shadowkiller324
Check the pcsx.cfg in /opt/retropie/configs/psx/pcsx/
the first line should have the bios name.
I know you have probably tried this but update the pcsx emulator.

I wouldn't give up hope on the lr-pcsx, I use it for every psx game. Maybe one of the retroarch configs has a problem, like; system_directory = "~/RetroPie/BIOS" being something else
You could backup both /opt/retropie/configs/psx/retroarch.cfg and /opt/retropie/configs/all/retroarch.cfg if you have them, or if youre not attached to your configs then you could delete them. A new one will be generated and you could copy it as configs/psx/retroarch.cfg then restore the configs/all/retroarch.cfg.backup.

well that would take me almost a month to do every game. the favorites folder should list the whole title even if its in brackets. because all the other folders don't do that.

Through trial and error, I figured out how to solve the problem.

Assuming it was a permissions problem, I first reset all the permissions to the ones all files had at the beginning. As expected, my conf file did not run.

I then copied the default dosbox configuration file from ~/.dosbox/dosbox-SVN.conf and edited that with my custom setup.

Now everything works fine, though I never did figure out which permissions were broken.

Thanks anyway!

@SpudsMcToole I’m new to Amiga emulation... Have been trying this but it doesn’t load as seems unable to load the right rom

I had the same issue, with the same brand PDP controller as the OP but purple controller (vVendor ID 0x0e6f, product ID 0x02bd). I followed the instructions to recompile the driver, but it still wasn't getting picked up.

I then did full update as per https://retropie.org.uk/docs/Updating-RetroPie/ and it all came good :)

Regards
Dan