Hello all! I decided to try my luck again today with version 7.2.2 but I'm still experiencing the issues described in my previous post when I tried version 7.0.1
Controller works in EmulationStation but not in RetroArch

I flashed a fresh image of 7.2.2, I was able to pair the controller by connecting a USB keyboard first.

• If I don't configure the controller before launching a game I can play (tried NES and SNES) but none of the HOTKEY combos work so I can't exit the game.
• If I DO configure the controller, then it doesn't work in the emulator unless I turn the controller OFF and ON again. I can see the popup telling me the controller has been disconnected/connected.

I also tried downgrading the firmware to v4.00 since I saw other post talking about that as a workaround (could not find a download link to v4.01 on 8bitdo website). Downgrading the firmware, factory resetting the Recalbox install and doing the pairing/configuring again didn't make any difference in the controller behavior.

Any ideas? I would really like to move to version 7 but these are the only controllers I have and using them via USB is not practical.

This is the controller I'm using 8bitdo NES30 PRO (currently working with version 6.1.1) with last available firmware (v 4.10)

In case anyone with this problem find this topic, I can confirm that my NES30PRO controllers are working as expected on Recalbox 8.

In case anyone with this problem find this topic, I can confirm that my NES30PRO controllers are working as expected on Recalbox 8.

I'm hoping I will have some time to test this weekend.

Last thing I did was enable the beta updates and try again (no luck) but I haven't tried downgrading the firmware past version 4.00

I wish I had kept the image for Recalbox 6, the last one where everything was working properly.

@zing Thanks for your quick answer, I just had time to check this today, looking at the es_log I don't think it is the same error, that's assuming I'm reading the log correctly, the -p1devicepath has a value

[2021/09/04 18:28:12.269] (INFO ) : [Run] Command: python /usr/lib/python2.7/site-packages/configgen/emulatorlauncher.pyc  -p1index 0 -p1guid 05000000c82d00002038000000010000 -p1name "8Bitdo NES30 Pro" -p1nbaxes 6 -p1nbhats 1 -p1nbbuttons 16 -p1devicepath /dev/input/event1 -system nes -rom /recalbox/share_init/roms/nes/2048\ \(tsone\).nes -emulator libretro -core nestopia -ratio auto 

Just in case here is the rest of the relevant part of the log https://pastebin.com/Vtx7B2wi

I started with a clean system (no controllers connected/configured), I used the VirtualKeyboard to connect the 8bitdo controller via BT and tried a game before configuring the controller. Same issue as before.
Then I configured the controller and tried again, no change.
Also, when I turn the controller off and on during the game and it starts working inside RetroArch, I see the popup device disconnected from PORT #1 but I don't see anything on the log about it.

Is there any information or log I could provide to help diagnose the issue?

Thanks!

Hello all! I decided to try my luck again today with version 7.2.2 but I'm still experiencing the issues described in my previous post when I tried version 7.0.1
Controller works in EmulationStation but not in RetroArch

I flashed a fresh image of 7.2.2, I was able to pair the controller by connecting a USB keyboard first.

• If I don't configure the controller before launching a game I can play (tried NES and SNES) but none of the HOTKEY combos work so I can't exit the game.
• If I DO configure the controller, then it doesn't work in the emulator unless I turn the controller OFF and ON again. I can see the popup telling me the controller has been disconnected/connected.

I also tried downgrading the firmware to v4.00 since I saw other post talking about that as a workaround (could not find a download link to v4.01 on 8bitdo website). Downgrading the firmware, factory resetting the Recalbox install and doing the pairing/configuring again didn't make any difference in the controller behavior.

Any ideas? I would really like to move to version 7 but these are the only controllers I have and using them via USB is not practical.

This is the controller I'm using 8bitdo NES30 PRO (currently working with version 6.1.1) with last available firmware (v 4.10)

@thanosazlin said in Fresh install and not able to get hotkey to work on BT controller:

so still not working, So i reimaged again, this time i was able to take a 8bitdo snes 30 controller from my pi4 and BT link it to the pi 3 recalbox, and it works fine. i'm able to use hotkey !
That's weird because I'm having the same issue but with the 8bitdo NES30 pro controllers, too bad I don't have a GAMESIR to see if it works for me, maybe then we can just exchange our SD cars!

Hi! Congrats to the team on the release of Recalbox 7!

I finally decided to try the new version today so I flashed a clean install of 7.0.1, my setup is:

• Raspberry Pi 3 Model B
• A pair of 8bitdo NES30 PRO controllers

I turn on my controllers with just the power button and they work fine on Recalbox 6.1.1

In 7.0.1 on the other hand, not so fine.

• I start with a USB keyboard plugged in, I turn the controller on, press the BT button to enter pairing mode (blue light flashes quickly)
• I choose PAIR A BLUETOOTH CONTROLLER, choose the NES30 PRO, connect it works, I can choose OK and go back using the controller already.
• I choose CONFIGURE A CONTROLLER and set up all the buttons, I use SELECT for the Hot Key. I make sure the 8bitdo NES30 PRO is selected as INPUT P1
• I can navigate the GUI with the controller with no issues, the controller reconnects if I restart, power cycle, etc.
• I start 2048 from the included ROMs (Nintendo Entertainment System) and none of the buttons or Hot Key combinations work. The USB keyboard doesn't work either (Esc, Enter, A, S, etc.)
• I turn the controller off, I see the popup notification about it have been disconected, turn it back on, it connects, I can play the game but pressing SELECT will cycle through the shaders, SELECT + START will quit Retroarch but not without switching to a new shader first
• I can also unplug/plug the USB keyboard and it starts working too.
• I launch another game, the controller doesn't work again. Power cycle the controller, it works, I press SELECT + B, the Retroarch menu shows up but the controller stops working again. Power cycle the controller again, it works but it is almost impossible to set up anything in Retroarch since it seems to be reading each key press multiple times, the selection jumps several lines at the slightest press.

At this point I have tried several emulators, and power cycling both the pi and the controllers.

I can't also get the HARD RESET to work with my USB keyboard, I have tried each and both SHIFT keys, after rebooting and power cycling the pi, nothing does the trick.

So I 'rm -rf' the /share/ folder to start over with the default configurations, and try the other controller, same results. I also tried pairing the controller but NOT running the configuration, leaving INPUT P1 as DEFAULT instead of "8bitdo...", tried other Retroarch cores, etc. Tried both of the controllers in case one was faulty too.

I also tried using one of the controllers via USB to remove the keyboard from the equation, with the same results.

Am I missing something? The navigation in EmulationStation works great but Retroarch doesn't take the controller or acts weird when it does.

Edit: I see a similar issue reported already so I guess it is a matter of waiting now:
https://gitlab.com/recalbox/recalbox/-/issues/1378
Thanks for any advice, I would like to be able to use the new version if possible.

Creo que la pregunta más relevante es si actualizaste algo antes de que dejaran de funcionar? Quizás Recalbox te ofreció instalar algún update y lo aceptaste?

Yo tengo mandos de 8bitdo y los míos tienen la opción de usarlos por USB. Si los pruebas por USB el problema persiste?

Ok, I'm going to leave the solution here for anyone who may need it in the future:

https://github.com/libretro/libretro-fceumm/issues/308#issuecomment-560408467

if using the US rom (NES), set User 2 to NONE instead of auto. if using the Japan rom (Famicom), disable User 5 instead.

Further explanation:

on NES, player 2 port acts as expansion port, including arkanoid paddle in this case (using mouse)
on Famicom (when loading Japanese ROMS), expansion port is on a dedicated port which is mapped to User 5 on fceumm.

this should resolve this issue and any other confusion with nes/famicom expansions

Sorry for the double post but the forum won't let me edit my previous message.

I've procured a No-Intro rom set for NES. There where two versions available (headered and unheadered).
The unheadered rom won't launch with any core.
The headered rom launches fine but I get the same results as before.

Is there anyway I can verify I got the proper rom using the checksum or a hash? Like the dat files used for mame rom sets?

Honestly I don't know the origin of these roms, I got them out of a premade image I tested.
Based on your suggestion I found a Japanese arkanoid nes rom and the controls work fine on that one!
The cheat codes included for the US version don't work as probably the memory mapping is all different but that is progress!
So now I will try to get a proper version of the US rom to try or hunt down some cheat codes for the japanese one.
As the people how know keep saying, check your rom set! I didn't thought it was so important for 8 bit consoles but clearly it is.
Thanks for your help!