In my case, the issue seems to origin from the fact that only player 1 can use hotkeys, but for some reason my controller's driver xarcade2jstick is by default reversing the sides of X-Arcade Tankstick, when retroarch is getting input. As a result, the lift side of the stick, recognized as Controller 1, is controlling player 2 in games and vice versa.

I guess that this prevented the Select as hotkey enabler from working. I made it work by fiddling around with the retroarch settings, and reversed the controllers, and not everything seems to be good.

I had my tankstick configured with the default mapping.

What I ended up doing was just adding these lines to the bottom of /opt/retropie/configs/all/retroarch.cfg and everything worked great after launching another game.

input_player1_joypad_index = "1" input_player2_joypad_index = "0"

Here's the mapping I use
bfdb83ad-edd2-4a60-9f37-05c9d7c43bbb-image.png

In my case, the issue seems to origin from the fact that only player 1 can use hotkeys, but for some reason my controller's driver xarcade2jstick is by default reversing the sides of X-Arcade Tankstick, when retroarch is getting input. As a result, the lift side of the stick, recognized as Controller 1, is controlling player 2 in games and vice versa.

I guess that this prevented the Select as hotkey enabler from working. I made it work by fiddling around with the retroarch settings, and reversed the controllers, and not everything seems to be good.

I had my tankstick configured with the default mapping.

What I ended up doing was just adding these lines to the bottom of /opt/retropie/configs/all/retroarch.cfg and everything worked great after launching another game.

input_player1_joypad_index = "1" input_player2_joypad_index = "0"

Here's the mapping I use
bfdb83ad-edd2-4a60-9f37-05c9d7c43bbb-image.png

@roslof Awesome, thanks for helping

@StrangeJaguar copy the theme folder to ~/.emulationstation/themes.

@Dr-Klein it is the difference between running roms from a USB drive vs. transferring roms using a USB drive.

When you run roms from the USB drive they remain on the drive, and are only accessible while it is attached.

You want to transfer the roms from the USB stick onto the SD storage. Name the folder retropie, instead of retropie-mount.

https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/

https://retropie.org.uk/docs/Transferring-Roms/#usb-stick

@Chadmon10 wanted to add that I’m using retrogame to map my arcade controls directly to the gpio. So some keys are being used already.

Thank you all for the answers. Actually I was referring to hypinput.ini but
I didn´t write it right.
Anyways, thank you for the link to docs. I´ve made a little bit of I+D and I´ve
solved the problem. Now the control ps3 and the Zero Delay are working
perfectly.
For those who want to know I´ve done it changing hypinput.ini (traditional
joystick api configuration) which is the one that came by default, by the
version´s (V2.10.1) scheme.

@sleve_mcdichael Sorry but im brand new to using the retropie, so I am not sure how to get the log file, but ill try and do it now :)

@mitu
I solved the problem. It was in the source code of hid-nx....

see here. It was the BTN_0 and BTN_1

I modified the code like this for both controllers and they are now working correctly!

Can be found starting here

static const struct nx_con_button_mapping gencon_button_mappings[] = { { BTN_SOUTH, NX_CON_BTN_A, }, { BTN_EAST, NX_CON_BTN_B, }, { BTN_WEST, NX_CON_BTN_R, }, { BTN_DPAD_LEFT, NX_CON_BTN_X, }, { BTN_DPAD_UP, NX_CON_BTN_Y, }, { BTN_DPAD_RIGHT, NX_CON_BTN_L, }, { BTN_THUMBL, NX_CON_BTN_ZR, }, { BTN_START, NX_CON_BTN_PLUS, }, { BTN_SELECT, NX_CON_BTN_HOME, }, { BTN_MODE, NX_CON_BTN_CAP, }, { /* sentinel */ }, }; /* * N64's C buttons get assigned to d-pad directions and registered as buttons. */ static const struct nx_con_button_mapping n64con_button_mappings[] = { { BTN_A, NX_CON_BTN_A, }, { BTN_B, NX_CON_BTN_B, }, { BTN_Z, NX_CON_BTN_ZL, }, { BTN_TL, NX_CON_BTN_L, }, { BTN_TR, NX_CON_BTN_R, }, { BTN_TR2, NX_CON_BTN_LSTICK, }, { BTN_START, NX_CON_BTN_PLUS, }, { BTN_DPAD_UP, NX_CON_BTN_Y, }, { BTN_DPAD_DOWN, NX_CON_BTN_ZR, }, { BTN_DPAD_LEFT, NX_CON_BTN_X, }, { BTN_DPAD_RIGHT, NX_CON_BTN_MINUS, }, { BTN_THUMBL, NX_CON_BTN_HOME, }, { BTN_MODE, NX_CON_BTN_CAP, }, { /* sentinel */ }, };

@barbudreadmon will try reading it, but thing is i don't have any problem untill i run something outside of emulationstation...
when system boots (and boot use config.ini settings) all is as it should be.

EDIT: i didn't find anything useful in that link :/

@sleve_mcdichael In my searches I also learned that if you create folders for each game in the apple2 rows folder, it will only show as 1 game in emulation station. so rather than change the file extension, just create a folder and dump all roms in there. when you choose a game, it will show the disks, but easier than having a thousand rooms to choose from at the start.

@mitu Ahhh on the keyboard to be PAIRED? No, I did not understand. Thanks, I'll try that.

edit: of course, it now works. I can't quite believe I didn't understand that part of the instructions haha

@MiroKostovBG said in Refresh emulation station games without restarting.:

@sleve_mcdichael And can you do that with a command through SSH ?

Maybe something like:

pkill emulationstatio && emulationstation

(Note the misspelled emulationstatio in the first one -- this is intentional.)

This tries to kill ES and then, only if that worked, restart it.

Also it would be interesting what would happen if a game is running, would that break the game

This I'm not sure but should be easy enough to test using the above.

I'm guessing this is a "No", then?

Thanks. I'll try that when I can save up some money.

Also some other details. When I try to connect it to other devices like my phone or laptop, it also turns off by it's own, and what's more is that Windows 11 says that its a "Driver Error" when reconnecting to the controller.
Also when reconnecting with Android, there is also a pin requirement of "0000".
(Maybe my controller is just the Issue)

Also, Is there a way to run:

Bluetoothctl

and try to re-pair and connect when retropie Starts, Restarts, or Boot up?
Because this might solve my Issue.

@HeineBorel Yes, the naming of the overlay is unfortunate. Note that your link is for the PIZero2W patch, for the CM4 is a separate repository, but it has the same issue (similar overlay name with an existing one, distributed by the raspberrypi-kernel package).

There are 2 workarounds for this

either rename the overlays/dpi24.dtbo file to something else and update the config.txt with the new name when updating RetroPie, skip the kernel and system packages and update only RetroPie's packages.