@Skullborn For RetroArch emulators, there's hierarchy of configurations supported - see https://retropie.org.uk/docs/RetroArch-Configuration/#config-hierarchy. If you saved a content folder override for the configuration or used 'Save Configuration', I would expect that some configuration would be different, depending on your options set for each system. But - for each system - RetroArch has the same auto-configuration for joypads (created automatically after you configure your gamepad in EmulationStation), so I expect that if a gamepad is detected in one system, it should work in all systems. As for advmame, it doesn't obey any config hierarcy, so I would also expect the same configuration to apply for all systems.

Some psx games are not compatible with Dualshock controller . You have to change the controller, from quick menu, to standard.

@gordonfreemanjr do you have any other controllers plugged in? Did you map your keyboard as a controller? It may be worth going into RetroPie-setup and resetting your mappings and then remapping just to see if that fixes the light issue.

@ibonihs You could try increasing the cycles to 20000, 25000 etc. If this doesn't work then could you post the contents of your config file dosbox-SVN.conf at a site like pastebin.com?

im running retropie 4.3 and im swapping the micro sd card from one pi to the other so my thinking is the usb port is broken? seeing it works ok on other pi.

Thanks Buzz, that worked perfect. Playing PoP on the keyboard works great but not so well with a controller. They have a fully working menu to save, load, settings, exit, etc. now. You can jump, duck, etc. no problem but for some reason the analog and d-pad does some weird things when trying to move. I'll post over there and see if they can address it. On a side note I was looking at the Dreamcade that is taking pre-orders now. I am on the fence because really if they sold their interface you could install it on an Intel NUC (looks almost exactly the same) and have the same product. They do have about 16 years building full arcade cabs so their interface is streamlined and polished. They originally were going to make it look like a retro style Atari-ish case but the final product is just a micro PC. Anyway I was just trying to view some video of the actual interface and product working and it's crazy the number of videos talking of being "RetroPie killer?" "Better than a RetroPie?", "The next RetroPie?", on and on. All I can think is they [RetroPie] is doing it right! :)

Solution found! Just install retropie again. I couldn't find anything on how to fix it but reinstalling worked

Well, I don't think that this issue's gonna get fixed but because I was impatient I decided to flash regular Raspbian and I think that I'm gonna just dual-boot Lakka (Since it uses more of RetroArch functions natively).

I did try the Xarcade2Jstick driver, but wasn't happy with the results. I did not follow the instructions at https://github.com/RetroPie/RetroPie-Setup/wiki/X-Arcade, but rather chose the driver from within RetroPie, if I remember correctly. I know I never did a sudo make or sudo make install. Although the other method I followed was much more time consuming, I'm very happy with the results. My retroarch.cfg never had any commented lines to begin with, so I'm not sure why it was different than what I found on GitHub. I used the 4.2 SD card image directly from RetroPie.

Hey Poltro, I just created the script to make things easier to install and setup Moonlight-Embedded. I have just updated this script today BTW to include a new menu based structure for an even easier solution. In regards to the controller mapping, this is now all stored in a txt file within the Moonlight program. It's called gamecontrollerdb.txt and contains the mapping for over 100 different gamepads. Here's what I could see in that file: xwc,X360 Wireless Controller,a:b0,b:b1,back:b6,dpdown:b14,dpleft:b11,dpright:b12,dpup:b13,guide:b8,leftshoulder:b4,leftstick:b9,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b10,righttrigger:a5,rightx:a3,righty:a4,start:b7,x:b2,y:b3, AND 030000005e0400009102000007010000,X360 Wireless Controller,a:b0,b:b1,y:b3,x:b2,start:b7,guide:b8,back:b6,leftstick:b9,rightstick:b10,leftshoulder:b4,rightshoulder:b5,dpup:b13,dpleft:b11,dpdown:b14,dpright:b12,leftx:a0,lefty:a1,rightx:a3,righty:a4,lefttrigger:a2,righttrigger:a5,platform:Linux, If Right Trigger is Start, try changing righttrigger:a5 to righttrigger:b7 and start:b7 to start:a5 Let me know if that fixes it here and also, let everyone know what model your controller is and the model of the receiver as that may offer some clues as to why your mapping is different :) Latest Video is here btw :

@matamualomia also try "button(6), button(7)“ or "button(6)/button(7)“

@pjft I had actually changed my hotkey for the RA menu in-game to be R/L/down/Y, which was working before, but isn't anymore. Maybe I can use the keyboard to get in and then go from there. I installed xboxdrv after this started, hoping it would fix the issue I was having with the 360 controller. It didn't appear to change anything.

https://retropie.org.uk/forum/topic/3/read-this-first 3. Search this forum to see if your question has already been answered.

Thanks for the reply but i dont find any of these options