8Bitdo NES30 Pro Bluetooth controllers not registering right analog left and right positions properly

ExarKunIv

@mitu i really hate to ask, but how do i install it.

i hate to say but it is above me on how to go about getting it installed, sorry

mitu

@ExarKunIv In this case, I have a simpler test you could perform.
On your 4.4 clean image, update RetroPie's installed packages - but without updating the OS and it's packages. This should also update your RetroPie script and put it up to the current 4.4.11 (?) version. Try mapping again the controller and see if it works.
After this test, re-do the update, but this time choose to update the OS and packages. It will take considerably longer - but try again after that to map the controller.

Btw, if jstest shows the right joystick as working, a simple workaround would be to try and replace the controller's .cfg file with the one I posted earlier (https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/udev/8Bitdo_Pro_F30_BT.cfg) - this should get you a functional right joystick in RetroArch.

ExarKunIv

@mitu ok so i updated just the retropie and NOT the OS.

i tried mapping the controller and -2 axis would not work. so i just started hitting anything to get pass the mapping.
so the hell of it i went back in and this time it worked. i was able to map -2 axis to anything. so i got it done and i went back in and again it worked.

not sure if this is normal or not. ( i just never payed close attention to it. but the mapping that failed was gamepad 1.
and next was gamepad 2, which worked.
and then gamepad 3 which worked.

is it this right. the gamepad number goes up as you map the controller even if it is the same?

im updateing everything right now. ill let you know what i get

mitu

@ExarKunIv said in 8Bitdo NES30 Pro Bluetooth controllers not registering right analog left and right positions properly:

is it this right. the gamepad number goes up as you map the controller even if it is the same?

The number is indicative of which controller you're mapping. If you have 2 identical controllers, there's no point in mapping the 2nd one - the config would be the same.

ExarKunIv

@mitu very odd

i have only one controller im messing with but yet it says gamepad 3 when i map it now.

i have updated everything now and i have able to map the controller correcly. i did it 4 times and each time it says gamepad 3.
but everything came up.

now why it mapped 3 different controllers i dont know.

think ill do a clean load. then update everything and see if i get a bunch different mappings like i have now.

mitu

I would suggest to reset your game controllers on the image that you started initially and try again to map your gamepad(s).

ExarKunIv

@mitu
i reset the controllers settings through Emulationstation

now its back to not seeing the -2axis on the right stick. i have done everything i can to see if i can get it to do the same thing as the other day and no luck.

also this is the 3rd Pi i have this problem with. and my NES30 pro is doing the same thing on my other build. so i know its not me being dumb :P

think ill try dropping the config you post earlier, but there is still a problem with something in Emulationstation i think

ExarKunIv

UPDATE

editing the .cfg and the ES input file for the controller and still nothing. the - axis for the right stick just will not been seen by Emulationstation

i also have tryed my NES30 pro. and that is also the same.

BuZz

I have two FC30 Pro on firmware 4.1 using a fully updated RetroPie

They both map fine. I power on in the default mode by just pressing power button. Note that make sure you have them "registered" when they were in the right mode.

ExarKunIv

@BuZz
when you mean registered, that they show up with the correct name when im in the mapping menu?

BuZz

@ExarKunIv when you register/pair them via the Bluetooth config.

ExarKunIv

@BuZz yes i have it registered through the bluetooth menu, i have the udev rule setup. both my controllers are running 4.10
i have updated the retropie with the latest 4.4.11.

i had the controller working find with the base load of 4.4, and then i did a full update, retropie and the OS. the controller was still paired, of course i needed to remap and just like before the left axis for the right stick will not be seen by the mapping.

this is the 3rd board that i have tried this on. kinda lost on what is going on

also it is also doing the same thing for my NES30 pro too

BuZz

@ExarKunIv Which mode did you register them in ? What do the controllers show in the connected devices in the bluetooth menu ?

mitu

@ExarKunIv So, on an updated RetroPie image, the mapping works, but on your original image, it doesn't. Is that correct ?
What packages do you have on your non-working image ? Run the following commands:

find  /opt/retropie/ -maxdepth 2 -type d
dpkg -l | grep libsdl2

and post the output on pastebin.com.

ExarKunIv

@BuZz
8bitdo FC30 Pro
8bitdo NES30 Pro
8bitdo N30 Pro2

all of them are in android mode, and all are doing the same thing.

but heres the kicker. i was able to map the left axis on the right stick....sometimes. so as of right now i have 2 of three i was able to map it right, but the mapping will not always work right.
also when i was able to map it right. it was coming up with gamepad 4 and 5, yet i only have 3 controllers

im so very very lost on what is going on

ExarKunIv

@mitu
it is intermittent. right now no image it what i call working. unless it is the base 4.4 with no updates

ExarKunIv

@mitu

packages

mitu

@ExarKunIv Doesn't seem to be something out of the ordinary and you have the updated 2.0.9 libSDL2.

ExarKunIv

@mitu yea
i understand if it just does not work, but there are times that it does map perfectly and when once i reboot. poof....it stops working

ExarKunIv

@mitu
now to make things even more confusing.

if i power on my system. all three controllers will not work. ok we got that.

but if i go to the retropie menu and run show ip. once i back out....they work. i can map them just fine. granted they will come put as gamepad 4, 5, 6

i know that the ip has nothing to do with it, but something about running a script seems to do something with the bluetooth.

well thats all i got a the moment.