Thank you for the reply but I ended up restoring from a backup. I know I did set the retroarch.cfg in the RGUI to save cfg upon close when this happened. This issue kept happening on anything I ran. Its not a big deal for me now but I am not sure if doing something like I did causes an issue. Either way I am up and working now. Thanks.

Oops, sorry about that. Thanks for moving it.

@rdm190

This problem really seems to defy all conventional wisdom, but before you give up, we don't we try mapping the controller directly from inside the RetroArch gui. If you're up for it, go to the RetroPie menu in Emulation Station and launch the 'RetroArch' listing. From there, go to 'Settings' and then 'Configuration'. Enable 'Save Configuration on Exit' and then work your way back and quit RetroArch. When back at Emulation Station, launch RetroArch again and go back to 'Settings'. This time, go to input and finally, 'Input User 1 Binds'.

Make sure the 'User 1 Device Index' is set to your controller and then look for a listing named 'User 1 Bind All'. Select that and you will then be prompted to move through a mapping process very similar to what was seen in Emulation Station. When you finish, work your way back to the first menu in RetroArch and select 'Save Current Config' just to be safe and then quit RetroArch.

Now, all that is left is to test a RetroArch emulator to see if the controller and mappings are recognized. Two things to remember, if this does work, is that it is simply sidestepping whatever mapping problem you are experiencing in Emulation Station and not resolving it. Also, these mappings are obviously only for RetroArch emulators. If it still doesn't work, there are a few more things we can try, but it'll involve a lot of backseat troubleshooting, as there is no obvious reason why you're experiencing these issues. In any event, I wish you luck.

That's happened to me before and it connected fine after a reboot. Could you try that?

Another note, at some point when disconnecting and reconnecting my N64 controller, the custom settings I set were overwritten. Not sure why this happened, I do not want these settings overwritten.

Is there a way to set the InputAutoCfg.ini file for n64 to read only so that only I may edit it?

In the meantime, I redid my process, and made a backup copy of my file, so if it happens again I can easily replace the file with my settings.

@laxattack

I figured out that it is reading as js0 due to me plugging in my xboxone controller.

Wow, that is indeed a strange issue. I'm surprised just removing the controller didn't solve the problems as the jsX listings are supposed to disappear afterward. Assuming this was the problem, you might still continue to run into the same issue if you don't first consider the order in which you plug your controllers. I believe the order in which the usb ports are read at startup is upper left, lower left, upper right, lower right. If these controllers are plugged in after the system has booted, you should also remember to plug in each controller in order of the desired player number.

@Gators
Not sure what search engine you are using but if I use google for rom set 0.78 I can find a link in about 1 second.

I have 37b5 rom set for Mame and all the games I have tried so far have worked straight from the zip file including frogger without any sound issues. Not tried donkey kong as yet.

Cheers

Paul

@sparecycle said in Questions on saving state with Xbox 360 controller:

I'm attempting to save state on SNES with Xbox 360 controller. I've seen a few different hotkey assignments from the GitHub documentation and in various forums.

such as? there's really only one thing that's worth reading - the official documentation :) https://github.com/RetroPie/RetroPie-Setup/wiki/RetroArch-Configuration#default-joypad-hotkeys

Is save state enabled by default on RetroPei?

yes, if you use a libretro/retroarch emulator. lr-snes9x-next is one of those, and that's the default snes emulator, so...

What Xbox 360 buttons should I be using to save state? I've been trying select + L1, select + L2 and select + Left D-Pad which leads to my next question...

see above link. that does presume you configured your controller correctly, mind.

Is there any form of on-screen confirmation that the state was saved?

yes. yellow text appears at the bottom.

@kjozsa see: https://retropie.org.uk/forum/topic/1649/controller-stopped-working-after-update/14

Besides, since you need to go out and download a more recent full set and rollbacks to build the set you want, you might as well just look for the full set you want and download that.

@mediamogul I used jtest as suggested and Rumblepad is detected and buttons working !!
Still ES would not detect it even if it was working before 3.8 update.
I then rebooted connecting the Rumblepad (as a second pad) together with the currently working Xbox360 Pad. That allowed me to enter Input configuration in ES and, finally, it detected rumblepad and I was able to configure it. :-)
Everything back working now !
Basically for those still having the issue, you can solve it by rpi-update command plus reconfinguring it.
Thank you all for the support!

Thank you for your quick and spot on answer, smoothing out option did it!
The size of the launch message had no link to my issue

jstest is in the "joystick" package.

see this for help on getting it working https://github.com/recalbox/mk_arcade_joystick_rpi/issues/32

thanks for your reply. It works now using the hdmi_drive=2 line in config.txt.
just found out that the pi zero seems to be too underpowered for N64 :(
guess it is just my NES/SNES station then.

It's simply requiring a valid login to reach the shares.

Search the forums. It's been discussed.
https://retropie.org.uk/forum/topic/754/samba-under-mac-3-7-stopped-working

@Concat
in RetroArch you can change the controllers on-the-fly:

Settings -> Input -> Input User N Binds -> User N Device Index

But keep in mind that it can bring some annoying situations, as I described here:
https://github.com/libretro/RetroArch/issues/3014

@BuZz Okey Dokey.Quick Install it is!

also please format your posts on this forum - especially console output/logs etc - see https://retropie.org.uk/forum/topic/3/read-this-first