Looking for testers: custom joystick mappings for runcommand/retropie_setup menus

[lilbud]

@DarkWolf How well does the PS4 dpad work for 2d games?

[meleu]

@DarkWolf That's good news! Thanks! Could you answer some more questions?

• 8Bitdo Nes30 Pro (bluetooth): Works perfectly fine (as it did before)
• Xbox One (wired): Works perfectly fine (as it did before)

When you say those controllers worked as they did before, you mean the same button mappings?

• Playstation 4 Controller (no ds4drv, bluetooh): Works perfectly fine (it doesn't really before)

You mean it started to work in my tweaked version?

[DarkWolf]

@meleu

When you say those controllers worked as they did before, you mean the same button mappings?

Yes, I mean the controller button mappings. I guess it is some kind of archivement if they work like they did before :-P

You mean it started to work in my tweaked version?

Again, yes, I've 2 versions of the Playstation 4 controller (one with a led bar on the touchpad and one without) which act completely different... Both didn't work properly in retropie-setup/runcommand but now (the version with the light bar, the newer version) works totally fine... I will test the older one (which requiered ds4drv) later this week (eventually tomorrow)

---

@lilbud yes, I like the dpad of the PS4 controller more than the XBox One dpad... (All in all I prefer the Xbox one controller, but this is another story :-) ).
But I've to say that it is more fun to play with the left analog joystick in most games where precission isn't needed that much! Games like Centipede are a bit harder with joysticks though

[meleu]

Updated the OP. The steps to test became simpler.

[mosi0815]

I followed your instructions and I'm now on commit c9c7b15.

First I testet my Wii U Pro Controller:

• A invokes the runcommand menu
• B is enter in the menu
• In retropie setup invoked out of emulationstation A is enter

My PS4 controller (bluetooth, sony-hid kernel driver) doesn't work at all, outside emulationstation or games, like before.

Do I have to do something else except cloning and starting setup once to make it work right?

[XVO]

Looks very promising, but I've got a quick question for OP. Does this mean that I can map MSX keys like the "F" buttons and "Stop" to a second controller?

[cafarellidigital]

This is a great modification, thanks for working on it! I haven't been able to test it yet, but I will when I can.

I'd like to make a request though: I use an official PS3 Bluetooth controller, and in these menus, the "Select" button enters commands, and the "Left Analog Stick" navigates left/right/up/down. I'd love to be able to change that to "X/Cross" enters commands, and the "D-Pad" navigates.

It seems that your update would easily fix my Select/Cross button issue, but what about the Analog/D-Pad issue?

Does your update allow for custom mappings (in a text file, for instance), or would that require me to compile my own version?

[meleu]

@mosi0815 said in Looking for testers: custom joystick mappings for runcommand/retropie_setup menus:

First I testet my Wii U Pro Controller:

• A invokes the runcommand menu
• B is enter in the menu
• In retropie setup invoked out of emulationstation A is enter

Thanks for the feedback.

Please, go to retropie_setup >> manage packages >> core >> runcommand >> install from binary. And then runcommand menu and retropie_setup will use the same button as enter.

I'll update the OP with these instructions...

My PS4 controller (bluetooth, sony-hid kernel driver) doesn't work at all, outside emulationstation or games, like before.

Do I have to do something else except cloning and starting setup once to make it work right?

I think it's beyond the scope of my changes on joy2key. Sorry...

[meleu]

@XVO said in Looking for testers: custom joystick mappings for runcommand/retropie_setup menus:

Does this mean that I can map MSX keys like the "F" buttons and "Stop" to a second controller?

I think my changes have nothing to do with this. Sorry...

[meleu]

@cafarellidigital said in Looking for testers: custom joystick mappings for runcommand/retropie_setup menus:

I use an official PS3 Bluetooth controller, and in these menus, the "Select" button enters commands

This behaviour of PS3 controllers was my main motivation to work on this. Using select as "OK" button is annoying! :-)

what about the Analog/D-Pad issue?

Nothing changes with directionals, sorry.

Does your update allow for custom mappings (in a text file, for instance), or would that require me to compile my own version?

Look what I wrote in the OP:

I tweaked joy2key.py to make it get the mappings from the retroarch-joypads config files. So the button you configured to be the A, will be the <enter> on runcommand/retropie_setup menus.

The mappings will match the configs you make for retroarch.
;-)

[cafarellidigital]

@meleu great, thank you!

[DarkWolf]

@meleu Hopefully this gets implemented into the retropie binarys

[mosi0815]

@meleu I just found out that the buttons don't work in raspi-config. Cursor movement is fine but A and B don't work.

[A Former User]

@meleu said in Looking for testers: custom joystick mappings for runcommand/retropie_setup menus:

Just like Aunt Josephine, I have a great love of grammar.

YES, WE GOT A LEMONY SNICKET FAN! :D

Anyways, back on track, I think this seems like a good idea. Helps to clear up confusion and helps to not trigger grammar enthusiasts.

[A Former User]

Forgot to mention this as well, but is there a way to change the buttons on the main menu to be fit for each controller? e.x. PS3 and PS4 controllers, since they use different buttons.

[meleu]

@itsnitro said in Looking for testers: custom joystick mappings for runcommand/retropie_setup menus:

is there a way to change the buttons on the main menu to be fit for each controller? e.x. PS3 and PS4 controllers, since they use different buttons.

Didn't get what you mean... Which main menu are you talking about?

Anyway, if you configure the circle to be the A on your controller (PS2/PS3/PS4/Whatever), it will be the <enter> on the runcommand/retropie_setup. Is it you're talking about?

[A Former User]

The Emulation Station menu, the one that looks like this:

[meleu]

@itsnitro oh... my changes in joy2key has nothing to do with emulationstation...
if your controllers don't have an uniform behaviour, I think you need to reconfigure them.

[A Former User]

Oh.
Alright then.

[DarkWolf]

@DarkWolf So I was finally able to test the "older" ps4 controller and I have to say "It works, ... kind of"
The input works but has a delay around 5 seconds or something like that
Dunno if this is a problem with the kernel, the controller itself or the joy2key script...