I've only recently updated my system to the new moonlight-embedded package yet I am having the same error, different controller ID but the same error. I've followed the steps you outlined and cleared the controller configuration but still no dice. Each time I launch moonlight, it finds the controller, yet never loads the correct configuration. Only falls back to the default configuration at the top, which isn't correct. Any help?

You will need to look at supporting sw for gpio inputs, try 'gpioneer'

@maplestory Correct. It doesn't matter. Those lines relate to the extra folders - nvram, etc.

Thanks for reporting! Hope you're having fun.

@msoulier if you havent seen it look at my post with free and dirt cheap dos games on gog.com.

@chadz

This post should do the trick.

@meleu Thank you for your answer.

I've tried it again with all buttons and both methods on the controller. Holding and tapping.
It only works with the 'A'-Button on my keyboard.

I'll try to remove the keyboard and the keybinds for it and see it that helps.

@caver01 provides all details in this great post.

[SOLVED]
What was causing the issue was the ps3 bluetooth drivers, which I realized were disabling the standard bluetooth on the device.

Thanks to this thread: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=148305&start=100

The solution was to simply uninstall the PS3 drivers from the retropie_setup menu.

Also just to note, if I plug my 16:10 asus monitor into my RPi it fills the whole screen with ES like I would expect, but games still have black border all the way around.

Edit: another note is that I did google some on this first and found to disable overscan in the config file. this worked for ES only if I turned off game mode on my TV but games were all still black borders all around.

@golaat Yes and no. Since some of the emulators run inside retroarch, you are somewhat tied to that environment, but with lr-mame2003 you can actually work around it. You COULD go in and set all of your player 1 inputs to “nul” (don’t use curly quotes like I did here). This is unique for this version of mame because it still “listens” to RAW keyboard inputs. You then have to go into MAME and map keys using the ALL games menu as opposed to just THIS GAME and you will have a nice clean input setup which is what I already proposed above.

However, this doesn’t work for other libretro cores. Still, I

@phrazelle you can fix the ES L/R by editing the es_input.cfg file.

go to /opt/retropie/configs/all/emulationstation/ open es_input.cfg and switch the values for right and left. This will only effect the controller for Emulation Station and not effect the emulators.

bump, sorry

Thank you for your reply...it helps a lot! I was thinking about manually naming the folders as well. I guess I can check and see the information that you request. Your post has been more helpful than most I have found in other forums so I appreciate it. Please excuse my "noobness" but how would I find the information that you request? Thanks...

Attempted to do a little more troubleshooting tonight. I'm still mystified as to what's going on, but at least now I have a better understanding of the problem.

After a little trial and error, I realized that InputAutoCfg.ini writes to mupen64plus.cfg, so anything I put in the former will overwrite the controller values in the latter. Thinking that perhaps whatever issue I was having was specific to Super Smash Brothers, I loaded up GoldenEye 64 also using Mupen64plus-gles2 emulator, and voila(!) the game seemed to be respecting my dead zone values. I had set them to essentially be maxed out, and sure enough I couldn't move the in-game cursor without moving the left joystick to the far edges of its range. I had similar results when I tried Mario Kart 64. I confirmed that I was seeing motion when a joystick value exceeded my deadzone threshold as displayed by jstest.

So I guess now the question becomes, why is Super Smash Brothers ignoring my dead zone settings, but the other two ROMs aren't? Oddly enough, there were a few times when I loaded up Super Smash Brothers and it DID seem to respect the dead zone settings--I had to move the joystick to an extreme to cycle through menu options--but there was no way I consistently get to exhibit this behavior. Is there a config file or something similar that's overriding whatever settings I'm specifying in the InputAutoCfg.ini and mupen64plus.cfg?

Ah... Thanks DD_Indeed.

I'll give it a shot tomorrow and see how it goes.

@ncrx please open another topic and give as much info about your setup as you can (like those suggested in the read-me-first post).

@herb_fargus I've read up a little bit on wine. My only thing is I am basicly building a retro all in one game console everything n64 and down of all my favorite games and i was wanting to include some older pc games i.e. quake,nukem,worms,bomberman....so retropie is a must. That being said i dont believe wine is an option unless im wrong

@girlzstalkme02
I am having the same issue... Did you ever get it to download for you? Thanks

Why not set up a file server on the pi3 and have the piZero read from that directory for the roms and game saves. That way it will all be stored on the pi3 for OTG fun. You can have the pi3 host its one access point from the on board wifi and have the piZero connect to it. You can also have the piZero temp download the rom and save the game locally and once the game closes you can have it automatically sync the game saves using something like rsync.

Hope that wasn't too confusing but that all works! :)