I read the following on the MAMEDEV.org-FAQs:

"To save the state of a game, use the default save state sequence of Shift + F7. At this point, you will get a prompt asking you to select a slot. Type a letter from 'a' to 'z' and the game's state will be saved.
...
To restore a saved state, use the default load state key F7. Again, you will prompted to select a slot to load from, and the state will be loaded."

So maybe i can assign another button as a substitute for a letter on the keyboard?

I changed my tv input and it is not doing it anymore. Must have been a setting on my tv.

I had black bars on all 4 sides. Then after enabling overscan, it would seem that the bars at the top and bottom were a little bit wider so the image didn't vertically fill my entire screen area. But all is good now :)

you need to also update retroarch via the same process.

That's just not smart.

Thanks :-)

@saiyan78 said in original Xbox Arcade stick:

i found this on amazon, HENGSHENG USB 2.0 A Male Plug to 2 Dual USB A Female Y Splitter Hub Adapter Cable.
anyone think it might work?

It can't hurt to try it for $6. One side is signal and other power only but it does seem odd that the USB port isn't supplying sufficient power for the lights. I have to say if you mean the original Xbox controller I didn't think it had any lights it's well over 10 years old now? :/

@Floob watching it now. thanks!

Thanks and good evening!

@DavidBowman

@g0nz0uk I ran into this over the weekend as well.

I didn't know how to revert the update, or even what changes I could tweak afterward to make it stable again, so I had to just reinstall fresh: https://retropie.org.uk/forum/topic/1555/gamepad-woes

try adding the hotkey commands to both /opt/retropie/configs/all/retroarch-joypads and also in /opt/retropie/configs/EMULATOR NAME/retroarch.cfg. I had a problem with mine not working until i put it in both.

the code should look like input_enable_hotkey_btn = "button #", and input_menu_toggle_btn = "button#"

@heinb Make sure you have all the bios files, respecting the filenames (capital or lower case names, as stated in the wiki)
Did you tried a specific rom only or with different roms?
If you can't run any roms, try looking for other bios files from different sources...

Surprisingly, this is not something that comes up often. There are quite a few emulators that don't have native controller support and rely primarily on the keyboard. I don't run any of the MSX emulators on RetroPie, but I assume this is the problem. Even if RetroArch allowed core remapping for MSX, I doubt it would allow f-key mapping to controllers.

If you really want to achieve this, you'll need to familiarize yourself with a keymapping program. This technique is completely off the beaten path, but has been achieved in RetroPie by others. Below is the link to a guide that explains the process as it relates to KODI. You'll need to adapt that information to the keyboard controls you wish to map for MSX.

http://blog.petrockblock.com/forums/topic/mapping-a-game-controller-in-kodi/

I'm currently working in this direction with a few emulators in my own setup, so if you have any further questions, I may be able to help.

The binaries have been updated.

I see time in time again that people are trying to get their controllers from a game system working on their Pi (no wonder: you're used to them, they cost a small fortune and they are of great quality). Those controllers often use a proprietary way of "communicating" w/ other hardware. They are often not compatible w/ general open standards or need to be switched to "standard compatible mode" or something. That is, even though they have a USB wire or are said to connect through Bluetooth they do not comply to general computer standards. Sometimes, like for the genuine Sony branded PS3 controller or the genuine Microsoft branded Xbox 360 controller, there is a solution, workaround or driver for these pieces of hardware for RetroPie (click the links in this post!).

Maybe it should be communicated a little better (sticky? homepage?) that these controllers are NOT standard compliant and that support for them is limited. It might even help to complain about this to Microsoft or Sony. There is no reason to "reinvent" the way that devices communicate via USB or Bluetooth, so they shouldn't.

Succes w/ setting up proprietary hardware y'all. :-)

I got the games to launch now..but i have no control settings so im guessing i have to go back and add controls to prboom :/

No, since they require a newer firmware/kernel to support the RPI3.

Nice job!

I didn't correctly understand you earlier that you are going to be physically covering a widescreen monitor.

I think you should be able to force a 4:3 video mode following the "elinux" link Floob listed earlier. You may then still need to adjust a setting on your TV to prevent it from stretching the input to widescreen as well.