Awesome, thank you!

Ran the test and determined only the standard 4 buttons are registering. The additional buttons from the 6 button pad do not appear.

I did have this working on previous RetroPies, and also just tested it on my PC and confirmed that all buttons are being registered there. Perhaps I'll reach out to RetroUsb and see if there's a recent compatibility issue.

Appreciate the help.

@DavidDraper I'm sorry to hear that it is not working for you.

First off, you definitely shouldn't edit the .bak file, stick with only the .cfg file. Sorry if I wasn't clear there. I'm not sure what the .bak even does, or how to revert it.

Second, remember to only overwrite the button mappings. For example, in the .cfg file there are 2 lines above the mappings that I left intact. For me it reads:
input_device = "SealieComputing N64 RetroPort"
input_driver = "udev"

This of course would change depending on what controller you are using.

If you've done all of the above correctly, then the only other thing that I can think of is that it might be because you are using a "Generic USB" controller rather than an original N64 controller with an adapter.
Perhaps this means your buttons are in a different order, or are labeled differently, I'm not really sure as I don't own a Dragon Rise controller to test with.

Still, if you'd like, feel free to copy what your original dragon rise.cfg file was (prior to copy / pasting my info), and I'll see if I can translate it into something that may work for you.

Otherwise, good luck, and I hope that other solution works for you!

Good to hear, and thanks for sharing the outcome, as even "I overlooked something" can be an important hint for others. 👍

Sorry took so long but thanks it worked amazing you are the best.

@psyke83

Thank you a ton, your advice worked perfectly for Sigil. I actually am interested in having individual launcher files for Brutal Doom for all of the Doom versions just because I like the simplicity of being able to select each game version separately, even if it is more work. But it isn't working like Sigil did. I created another folder under the doom folder called "brutaldoom," just like with Sigil, then edited the emulators.cfg file with the addition of an emulator called brutaldoom. This new entry had /addon/* changed to brutaldoom/*, the same as I did with Sigil.

I placed the doom wad in that folder, and the brutal doom .pk3 file. I set up a "Brutal Ultimate Doom" launcher directing the location of the doom.wad file in the doom/brutaldoom folder. It launches it perfectly fine when I set "brutaldoom" as the default rom launcher, but for my launcher for the normal Ultimate Doom it will then be set to use the brutaldoom launcher as the default rom emulator as well. If I change the normal ultimate doom launcher back to lzdoom to play vanilla doom, the default emulator for the brutal doom launcher will then automatically be changed to lzdoom as well. So changing the emulator for one ultimate doom launcher changes it for the other, whether its brutal doom or vanilla. I assumed that was because I used the doom.wad file in the brutaldoom folder without changing the name, so what happened to one "doom.wad" changes it for the other because they have the same name, despite being in different folders.

So I tried changing the name of the doom.wad file to brutaldoom.wad in the brutaldoom folder, and kept the original vanilla ultimate doom in the doom folder unchanged, but then it won't even launch the brutal doom version. So it seems to have to keep the original wad name. Since what I did what worked for Sigil I'm lost as to what it is making the two doom.wad files, in different folders, linked. You know so much about how it works, is it obvious where I went wrong? I feel like it must be something small that I just keep missing.

on arcade games in its intended resolution there is black bars at top and bottom because its on 1280x1024 when I try drop the resolution lower on launch options the game wont load up for some reason, just the sound and a black screen.

I can go into option during the game with the 1280x1024 and change the screen to fit but I have to do that for all games it's a bit annoying.

Retropie 4.6 on a raspberry pi 3B with a 128gb Card.

Playing with the sourcecode, I usurped the 8:7 PAR to be just 8:7 like 4:3. The switch that controls this is a boolean and I haven't the time to change it right now (and then I would need to make a github account to request a pull for the changes).

I realized I can use my USB2-A meter to test the output from the USB2 ports. Problematic PSU causes it to have 5.3V and the better one has 5.1V. Hopefully it helps anyone else having problems with a stronger PSU.

@Mikeymac02 All I did in my cabinet was run the power coming in through a toggle switch first then to a outlet inside the cabinet. Then I just plugged in a good surge protector to my switched outlet to power everything. To turn on just flip the toggle switch and it boots up. To turn off, properly shutdown retropie from the menu then flip the toggle switch to kill everything else.

@NewAtThis Can you try updating the ti99sim emulator from source and check again if the resolution handling is better ? It's been updated to the latest version, which was a major update.
Try to remove any video mode set through the runcommand launch menu.

@mitu This was it! I have a script that controls an LED light/Power button on my case, (as well as shows heat/fan speed, etc) and it seems that the new update doesn't like it. If I delete the python line, the retropie command line and the RetroPie UI work as expected. Not sure what the conflict is, but it's clearly to do with the script on my end.

Below is the autostart.sh if you're curios. Thanks so much for your help!

python /home/pi/scripts/picontrol/picontrol.py&
emulationstation

@zrs6v4 Try testing the hotkey combo with jstest and see if the buttons register ok when pressed at the same time.

Please add some info about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

What emulator are you using for arcade emulation ? We have several mame versions included - are you using mame2003/mame2003-plus/mame2010 ?

Just for someone else experiencing the same problem, make sure you have free space left on your sd card. Check if the expand fs ran successfully at some point.

@studysession double check your GPIO connection. Also try switching to unsafe shutdown (switch in the case PCB) if you have that and see if you have it to power on.

This is a common problem for arcade emulation, so you maybe want to read and understand how that works first, from https://retropie.org.uk/docs/Arcade/.
If the ROM doesn't work, then you'll need to find the correct ROMset version for your emulator and get the ROM from that collection version.

If the issue appears only for arcade ROMs, then most likely your retroarch.cfg for that system is incorrect. Find the file \\retropie\configs\arcade\retroarch.cfg and replace its contents with

# Settings made here will only override settings in the global retroarch.cfg if placed above the #include line input_remapping_directory = "/opt/retropie/configs/arcade/" #include "/opt/retropie/configs/all/retroarch.cfg"

Try again to boot an arcade ROM and see if it works.

Thanks for the responses to my question!!

I've already tried to downclock the device, that didn't help a lot though, yes I have overvoltage set to 6, however I tried to disable it for testing purposes, sadly it didn't help.
I actually only used gles2rice since my games then run at 1080p, all of the other options run at a realy low res, and when I look into the menu where you can change the video output, it's set to 1080p.

So I think my new question would be then how to set the "real" resolution for one of the better emulators to 1080p.