Issues with FC30 Pro input after getting bluetooth working

meleu

@jpowell said in Issues with FC30 Pro input after getting bluetooth working:

everything else besides the D-pad loses any functionality when inside an emulator.

I was getting this very same problem with an ipega bluetooth controller. I solved this way (I'm assuming you are comfortable with linux commands and know how to edit retroarch.cfg-like files):

configure your problematic bluetooth controller to be the player2 (input_player2_joypad_index).
configure a working joystick as player1 (input_player1_joypad_index).
launch any game with RetroArch.
invoke RGUI (Select+X on player1 joystick).
go to Settings -> Input-> Input User 2 Binds
configure the buttons as you like (hey look!! the buttons are working!!! :D )
go back to the RGUI Main Menu.
select Save New Config. PAY ATENTION AT THE BOTTOM LEFT CORNER OF THE SCREEN AND MEMORIZE THE FILENAME SHOWED THERE!
go to the shell prompt
open the file saved on step 8 (you memorized the filename, right?)
write down the numbers after every input_player2_BUTTON-NAME_btn (substitute BUTTON-NAME with: a, b, y, x, l, r, start, select, l2, r2).
open the file /opt/retropie/configs/all/retroarch-joypads/CONTROLLER-NAME.cfg (substitute CONTROLLER-NAME with the obvious).
put the numbers you wrote after their respective input_BUTTON-NAME_btn (note that there aren't that playerN string here).
save this file.
start a game to test it.
come back here to this post and let me know if it worked for you too! :D

Cheers!

BuZz

please post the output of

cat ~/.emulationstation/es_input.cfg
cat ~/.emulationstation/es_temporaryinput.cfg
ls -la /opt/retropie/configs/all/retroarch-joypads
for file in /opt/retropie/configs/all/retroarch-joypads/*.cfg; do echo $file; cat $file; done

meleu

for some reason I don't know, the output of jstest tool with my ipega controller doesn't match the numbers that RetroArch needs to the map the buttons.

I noticed that the numbers that RetroArch needs are the "$jstest_output_number + 9", for my ipega controller.

I was looking ~/RetroPie-Setup/scriptmodules/supplementary/emulationstation/configscripts/retroarch.sh, and noticed that the developer takes care of this for 8bitdo users at this line (the script adds +11).

As we can see in the code, it doesn't includes "FC30 Pro" [EDIT: I think "8Bitdo FC30"* should match 8Bitdo FC30 Pro, it's strange...]

BuZz

@meleu That doesn't help with this thread - there are differences between ids with the udev driver vs sdl also with other controllers - we are aware of it, and already have workarounds for some controllers.

meleu

@BuZz Oh, sorry. I may have been a bit wordy mentioning that script... I just wanted to share how I solved this same problem with a bluetooth controller ("everything else besides the D-pad loses any functionality when inside an emulator").

BuZz

on firmware 1.68 our configure script should set up the values correctly for RetroArch.

jpowell

@BuZz Unfortunately the way I've got things set up with the Pi, it would be a manual exercise of running the command you've indicated, then writing down the output and typing it back into a forum post. As I said, I'm very new to this, and I've managed thus far by simply moving my keyboard from the desktop to the Pi in between working on it (not set up on my network yet even). I can work on doing this, but it's not going to be a fun exercise.

To clarify: i already manually input all the button values (obtained via the initial emulation station configuration menu) into the retroarch.cfg file, and everything seems to be the same as had worked previously. The only thing to have changed was that I created / edited the 10-local.rules file to force the pi / controller bluetooth connection.

Is there some potential issue with the button values changing? Is there any way in the 8BitdoFC30Pro.cfg to force it to look at the retroarch.cfg for values?

Thanks for all the responses thus far, I'd be totally flailing in the dark without them.

BuZz

@jpowell you don't need to do anything manually. You can do those commands over SSH btw once networked. You should let the system set up your controller automatically after configuring in es. Perhaps try from a fresh image, your manual configurations may be at fault

BuZz

Also check out

jpowell

@BuZz The manual configurations worked just fine prior to getting bluetooth working, so I don't believe that they are at fault. Unless there is some reason that they would have changed once the auto-connect to bluetooth was set up?

I had watched the posed video as I was setting up the controllers, but because I don't have my Pi connected to my network, I opted for the manual bluetooth connection option, which also seems to have worked, but caused some issues with retroarch obviously.

It seems like at this point it's time to try a fresh install, to see if maybe some small step was missed.

Thanks for all the replies.

jpowell

ISSUE RESOLVED.

@BuZz Thank you for posting the video, as it convinced me to do a fresh install. The new tools that are detailed in the video specifically for 8Bitdo bluetooth controllers have worked flawlessly, and it took far less time to re-install than it would have to troubleshoot.

Thanks to all who posted.