@Krakatoa everything is plugged in the exact same way. Nothing different.

@mitu yeah, reading some docs makes no sense. Maybe it's only working due i changed emulator. Thanks for helping anyway.

@ultramagnus_tcv said in Auto 1 Auto 2, etc. in RetroArch: It sounds like there's some kind of library of controllers that Retroarch knows about? Yes, at the link I posted previousy - https://github.com/libretro/retroarch-joypad-autoconfig Is that pulled from the Internet or does a group of them exist inside the Retropie installation? Neither. When you configure your gamepad in EmulationStation, an auto-config file is generated automatically by RetroPie and copied into the right place, so it's loaded by each libretro core (RetroArch). I guess what I'm getting at here is: If I were adventurous, could I create my own autoconfigure entry for my particular controller since it doesn't match up with anything currently in there? I don't plan to do this. It's a curiosity. Yes, you can - https://docs.libretro.com/guides/joypad-autoconfiguration/ - but, as I said, an auto-configuration is generated for your when you configure your gamepad in EmulationStation, so you don't have to. Another question: Let's say I want to get an N64-style controller. Is there a way for me to look up whether a particular mfg's controller exists inside RetroArch's known controllers so that wouldn't need to manually remap? You can look it up in the RetroArch's joypad repository - link posted above.

@mitu That's how I originally started out and it didn't work. I have weeks of work into this image now and don't want to wipe it out on a whim until I know that every avenue has been explored. And as I said earlier, it's happening on multiple different images.

After JsTest, when i press the buttons, as i said the corresponding number is blinking ON A,X,RShoulder = 1 B,Y,LShoulder = 3 Any ideas else then s*tty controllers?

Thanks, I'll try that. It sounds like it is basically a bug since it should automatically invert an axis if I map the controls reversed. Some people want to flip joysticks around and use them left-handed, so the software shouldn't really assume a "correct" orientation.

@RetroNerdman Nope, you go there : https://www.bountysource.com/issues/69769485-feature-request-input-mapper-macros . Also having a github account to reply "i opened a bounty" to this issue is a good idea though.

I have a similar issue: Having 2 PS 3 controllers, yesterday I performed sudo apt-get update and sudo apt-get dist-upgrade. After that, the controllers still paired, however auto-logon failed. Then I chose to update all packages from the Retropie setup. After that I rebooted, and then the controllers didn't pair anymore. I will roll back to my last image, anyway I think some mess was being built into the latest update components. Obviously I'm not the only one having logon and controller pairing issues after the recent updates...

@mitu said in Questions about controller buttons, logins, and Steven Scraper: but when we're talking about custom tags, Thanks for the quick response. I'll try the autostart and login. I don't have any custom tags...I just want to make sure that the redone videos aren't overwritten by the original videos. I'm not too worried about the favorite/playcount/etc stuff right now. I just want to get this all up and running. I ordered a replacement SANWA JLF-TP-8YT-SK joystick to swap into my controller. The stock stick is not very accurate, but I got it super-cheap and couldn't pass it up.

I tried to config the buttons through the main input config area while retropie was running and found that retropie recognizes the Ultimate OI board by Ultimarc as one game controller. Seems to me it has to be configured through the script manually. I'm trying it tonight to see if I'm successful. Did you ever get yours working @EspenT ? Thanks.

@clyde i just tested marks update it does appear the offsets are wrong now for what you choose im sure mar will fix it soon enough.

@Freakadude yes, the scriptmodule compiles MT-32 support into the lr-scummvm core, but is not enabled by default because the RPI is not very powerful for it in some games. If you want to try it, go to the BIOS directory ($HOME/RetroPie/BIOS) and in there you will find the configuration file scummvm.ini. Once in there, set these options in the [scummvm] section (if not there, add them): mt32_device=mt32 music_driver=mt32 To return to the default (disabled), delete the options from the config file. Edit: forgot to add an option to the list :)

@Mikey123 So.., right now do you still need help or have you figured out how the core remapping works ?

@cargorunner said in Not working after update all packages: Other game controls were right stick clicked as a button. So totally messed up mapping There are 2 caveats during the upgrade The xpad driver is overwritten when you select 'Update OS packages' and should be re-installed after the update. See https://retropie.org.uk/docs/Xbox-360-Controller/#xpad-driver. The auto-login is broken - because of Raspbian upgrades for the systemd. This should be taken care by the procedure you performed (i.e. enabling auto-login in Raspi-Config). For the other errors, or why you're not stuck with that message, I don't know.

@mitu said in RetroPie controller set up issue: @ranma The problem in this topic is specific to the xpad driver, which powers the Xbox 360/One controllers, it's not a general one. Basically, after an update of kernel, the xpad RetroPie driver was not installed and overwritten by the default one, which is sometimes incomplete depending on the model. This has been reported after the 4.4 was released, but was fixed some time ago https://github.com/RetroPie/RetroPie-Setup/commit/f6e5a6d70512fc796a4fb535ddf1b44ea985db47. Oh I see. I assumed as the Logitech F710 switch had to be set to X input rather than D that this issue was effectively the same as mine. I'll start a new thread when I decide to have another attempt and if the problem resurfaces. Many thanks. :-)

@kerflug Read this topic on why this is not advisable and can cause problems.

@mitu Thank you for the help! It didn't work, but then I got to thinking, just for the heck of it, why not take out the keyboard and dongle. That fixed everything. Thanks to the community for putting up with a noob.