We may have to amend the docs and don't recommend ds4drv anymore. Try with regular bluetooth pairing again - it should work.

Its just working ingame now after removing xbox drivers and some tampering with the PS 3 driver like remove and install again and switching to antherone and back to shanwan.
Not yet tested in Retroarch

Holy crap. Never mind... I.... yeah... that .... that was stupid. It's been a while since I configured the machine and I totally forgot that it wasn't retroarch's settings but MAME's settings I had to change.

I'll go hide under a rock now. Kthx

@lolonois Thankyou very much. I will keep this in mind !

By the way, MAME 2003-Plus has four different button layout presets for gamepads and arcade sticks. See Default RetroPad Layouts in the Libretro wiki for MAME 2003-Plus. They should cover most games' button layouts.

Thank you for your post. Having two SF30 pro and got the same issue.
After configuring as per you post above, the mapping is strange. For example, the hotkey is used to jump under tomb raider.
In other words, the controller map is not as per lib-retro "standard" for psx. Any idea how to be back on standard lib retro mapping ?
My config : retropie 4.7.3 / pi 4

@dankcushions it’s about performance. On 2016 I can play eg. Die Hard Arcade with minimal slowdowns during QTE but overall game is pretty playable. With current mame it works in around 10 fps. Apart from that I have Mame2016 romset and don’t need to find another source for that.

It's a pity it doesn't work, it was the ideal steering wheel for an outrun-based arcade, because of the Ferrari logo theme and the license :(

@mahoneyt944 , @Melvin-FoX Thanks for the suggestion, disabling the digital autocenter did the trick!

Thanks pal will do. Cheers
@windg

Had a similar issue with my kidzplay racingwheel.
For that i just mapped the analog control as D-pad without using the "Analog to Digital" option for the individual games i used it with.

Since your controller is broader, you can save the button mapping for entire systems, that do not use analog buttons at all.
Only the systems that do use it you'd still have to do it per game for.

Not really a solution, but its a workable workaround.

Not necessarily - you can remap one of the existing buttons (X/Y/L/R) to be the P2 start. For the games you mentioned, it wouldn't be a problem, since they have very few buttons.

Hey, thanks all. I changed this around as suggested and it worked.

Button 5 is real block and 6 is "quick block".

@keith-f-kelly said in Enhancements for Dialog Navigation/Controls:

I don't see why any button needs to be mapped to the TAB key. TAB doesn't appear to be used anywhere in the menus. Am I missing something?

The physical key Tab is by default mapped to traverse the button selection (in the bottom area) in retropie's dialogs. More generally it is mapped to traverse the input fields/controls of the different widgets available in a dialog.

For 0x0a / 0x0d: I do not stick to 0x0a I just took what was there, maybe it is the cleanest to sent the terminfo's cr instead of 0x0a or 0x0d.

What image are you using?

Okay.

It appears screensaver controls only work with videos - is that right?

Also, while it did initially work setting the screensaver to activate after 5 secs, it decided it didn't like it after a while, and it appears fine with it set back to the minute again. (I'm assuming the GUI not allowing me to go below a minute is something of a warning, here.)

So now my main question really is: has anyone used Skraper recently? It seems great, but try as I might I cannot get the video resizing to work.

Take a look at https://github.com/recalbox/mk_arcade_joystick_rpi, it's similar to what you have in mind and it's already included in RetroPie.

I have the same issue with my Xbox controller. My analog does as you say, but my Dpad works fine.