Wish i saw this earlier but yeah downgrade to 1.68. I had the same issue with 1.69. Once you're on 1.68 and map the buttons through emulationstation, retroarch should pick up those controls.

@theroamer said in 8bitdo FC30 pro controller mapping getting messed up in emulators:

What controller firmware are you using? I had that problem with my NES30 Pro on 1.69, downgrading to 1.68 and re-pairing fixed it.

@theroamer not trying to hijack this thread but have you got your NES30 Pro working with kodi yet? it seems i can't get the d-pad/analog to work correctly.

Ok got it to recognize my cono roller, by modifying the retroarch.cfg, but not I'm always forced to be player 2, andon't thus have no hot keys. Ideas?

Good to hear.

@RetroResolution
After changing the kernel.
The problem "CCurlFile::FillBuffer - Failed: Could not connect to server (7)" left.
And another good thing, the bletooth frezers too.
Source: https://github.com/raspberrypi/linux/issues/1360#issuecomment-218519761

No problem. I hope everything goes well. Let us know.

I have to agree with Pifan. $92 isn't much of an investment for something that is almost every game system created. Keep in mind you get what you pay for. The better quality parts are going to last much longer and function better.

Hello, this past Sunday I updated retropie from 3.6 to 3.7. The installation seems to be ok but I did get the same issue as @vretro. Most of my configurations for the n64 were kept but I did have to redo the hotkeys. I do see a .eep file but I am not sure if I had a .srm file before. I would have to reflash 3.6 back into my sdcard to check that out but the other .srm files such as the ones that I have for Playstation and Gameboy Color are still there. This seem to only happened to n64 and I have it set to be running Mupenplus64 with Glide plugin. @vretro have you figured out anything since this first happened to you?

@brianinkc I have used my controller with both xpad and xboxdrv, and honestly I prefer the way xpad handles controllers. Yes, you get a blinking light, but that's nothing a little hardware modification can't fix. :P

https://github.com/RetroPie/RetroPie-Setup/wiki/First-Installation
https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-the-XBox360-controller

@Rion said in Accidentally remapped lr-mame4all internal settings menu:

I have f***up my install many times and came to the conclusion that I needed to make a backup for every major change I did.

I was fortunate enough to learn that lesson prior to RetroPie, but I considerate it of the utmost importance here. I can't recommend this policy highly enough when maintaining and servicing a complex system install like this one.

I Found the wiki page for it shortly after i posted it. Thank you though.

@herb_fargus 1 last question sir...i understand the raspeian os and how to install...but if i wanted to try windows iot how do i put tht image and retropie image on same sd card...i promise this is last question...TIA

@Prindle19 hum... the first one i can succesfull pair, but the second just work wen it is on the cable.
I cant pair the second controller wiresly .

Didi you have this trouble too, wen you was trying to resolve this?

I didn't understand very well your post, but check this if you are using a Kodi config backup:
https://retropie.org.uk/forum/topic/314/can-t-get-kodi-to-run-with-retropie-3-7/16

If not, there is a high chance that you are experiencing this bug:
https://github.com/raspberrypi/linux/issues/1360

You can try to update to kernel 4.4 and see if that fixes your problem. You can test it by running the following command,reboot in the end and test again:

sudo rpi-update

WARNING: I am not responsible if this breaks your installation more than it was, try it at your own risk.

Thank you. I will try that tonight.