I'm going to try with rejoystick (http://rejoystick.sourceforge.net/)

Do we know it?

@iandaemon I'm in the exact same boat. I think the last new game I finished was Red Dead Redemption.

The quickest way I have found to setup 5200 controls in RetroPi is

open a 5200 game then enter the retro arch quick menu.

From there you want to go down to options. Then set the Atari System to 5200. After that go back to the quick menu.

Now select controls.

Go down to Port 1 Controls and click it.

Change Device Type from RetroPad to Atari Joystick.

Back out to the controls menu.

you may want to set the Device Type to Atari Joystick for
Port 2 controls if you're playing 2 player games.

From the Controls menu Save Core Remap File.

Go back to the Quick Menu.

Back out to the main menu.

Open Configuration File and Save Current Configuration.

Back out to the Main Menu and Quit RetroArch.

Now your controller should work with 5200 games

@iandaemon thats exactly what i did and didnt catch thank you

And now I was also able to connect the controller!

Thanks so much, topic can be closed.

@cousinsfan

and now all the names are the right names - not the romnames - meaning....did it take time to "read" the names from the xml and this took time (overnight - but probably quicker of course)??

No, it's instant. Maybe you had two different gamelist.xml's and deleted one and didn't realize the other had the correct names?

forcefilename is the only thing I can think to change...would that work?

Yes. :)

Anyone? Please?

@mitu ok but yes, i tried different roms and the bios is there and correct, validatd the hash. it is getting recognized by mGBA too. i thought maybe it's related so i answered in this thread. It really seems like a BIOS problem though because at first start there is no gba intro only after the restart and the following restarts the intro appears, really weird problem. Are there other known gba roms with skip-intro problems maybe so i could test those?

@gordonfreemanjr said in 8bitdo FC30 not pairing via Bluetooth:

@jplank Was that it?

Someone suggested I SSH into the retropie and go to bluetoothctl and then scan now. I did so and neither of the controllers showed up. I rebooted and tried again, same result. Then I tried one last time to load emulation station and pair the controllers - and it worked right away.

The thing is that I had about 15 tabs open with any youtube tutorial and help thread that I could find and I was trying anything I could find. For me, it wasn't that I changed setting X and then it suddenly started working. I "think" the last setting I changed was when mitu suggested changing the pairing mode. I changed it back to default and had to try a few more times to connect before it finally did. There might have been some resetting in there. All in all, I spent hours trying to get it to pair. I hope you manage to get yours fixed in less time. I hope that helps a bit. Good luck!

@avendosora ok that worked! I just copied the gamelist.xml from the .emulationstation fodlers for each system and now they all have video! thanks so much for you help in figuring this out its been driving me nuts.

@folly Thanks for chiming in, I'll look into that!

Yeah from what I've seen so far, a lot of the menus still have enough English to be playable, with the worst of it generally being not being able to read/understand the characters for games where you'd have to make up a name for yourself. With an RPG like Esper Dream however, the language barrier was definitely going to be an issue (but fortunately a translated ROM exists). Just don't want to have it inconvenience me later on.

Anyway, hopefully I can get someone who can answer some of these other questions...!!

@yfzdude Ty for the fast response, ill keep trying to make it work¡¡

If you're in lr-mame emulators you can just hit TAB to get to the "mame menu" and most (not all) games have a difficulty setting.

@scenariol113
OK
I figured it out with some off site help.

I was able to compile it by editing the supermodel directory /Src/Input/inputs.cpp

in the input.cpp file you edit the UI Controls line (1st line) for "uiExit"

where it says INPUT_UI, "ESCAPE" you change it to INPUT_COMMON, "NONE"

Then you run the -config-inputs command and map your keys.

The UI Exit should be in the list now to map it.

Now you can exit supermodel from somewhere besides a keyboard.

Here is a youtube link and the guy that helped me. Read the comments and you will get a better understanding

@offlercrocgod Xbox360 controllers do not have Bluetooth and will require a usb adapter to work. 3rd party adaptors are sold on Amazon and work just fine.
If you wanted to go the Bluetooth route, you need an Xbox one controller WITH BLUETOOTH. Not all have it. Or get a ps4 controller.

@dizmodawg Use KIOSK mode would probably be easier to still have those available in FULL mode. You could just jump back and forth when you need to edit something. The stuff would still be there, but "hidden" in KIOSK mode. You just have to set the "hidden" flag on each entry in each system and the system won't show up. You can use KID mode like this to. You can flag a handful of ROMs as "kid friendly" and then that's all that will show up.

They're kinda opposites. KIOSK mode will show everything except flagged. KID mode will show only flagged.

I know this topic is really old but i had the same problem myself and solved it. I noticed that the button mappings in RetroArch interfered with MAME 2010's mappings. One button could mean one thing in RetroArch but another in MAME so RetroArch would say to MAME something like - Hey! We also want to press this button!

What i did was that i blanked out the button mappings in RetroArch so they're seen as ---. After this my MAME mappings worked straight away. Then saved it as a content (game) specific configuration.

@mitu Good call! I'm not sure how much power it's pulling, but setting over_voltage to 2 definitely makes it last longer, though not completely staying on all the time. Trying with setting it to 3 right now and that seems to be going strong!