I ended up fixing the problem on my own.

The issue was that Drastic and Retroarch were trying to render the resolution at 640W x 480H, which would cause squishing issues.

By adding in:

hdmi_cvt 480 640 60

Into the config.txt, I was able to give drastic another resolution to render at, solving the issue. For retroarch, I made the auto fullscreens resolution the 480W x 640H that the display was native to, which also solved the squishing.

Is the controller configuration saved in /opt/retropie/configs/all/retroarch-joypads ? Do you see a .cfg flie there for the controller ? If yes, can you post the contents of the file surrounded by code tags here, in the topic ?

@abj Thank you SO MUCH, I was super lost when it came to this but it worked <3

@mitu The "full" config would have been that stock one, with that other HDMI bit added. The pi is on the stock config now. If you wanted something different let me know, maybe I misunderstood you.

Thanks for those ideas. I'll see when I can get around to them.

@wtstreetglow1 Just letting anyone in the future know that after my research. Final Burn Neo games still go in the fba rom folder and mame 078 go in the mame-libreto rom folder

@13ooty

I'm also new to posting on forums so I'm sorry If my writing and information is sloppy xD

@sleve_mcdichael said in Oricutron key mapping - is it possible?:

It can be a lot to process. How far in before you got lost?

Look for an entry that represents your device. Scan for the line marked H: Handlers=, and make note of the event number. Example:

pi@retropie:~ $ cat /proc/bus/input/devices I: Bus=0003 Vendor=046d Product=c21f Version=0305 N: Name="Logitech Gamepad F710" P: Phys=usb-0000:01:00.0-1.2.2/input0 S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/input/input73 U: Uniq= H: Handlers=event0 js0 B: PROP=0 B: EV=20000b B: KEY=7cdb0000 0 0 0 0 0 0 0 0 0 B: ABS=3003f B: FF=1 7030000 0 0 I: Bus=0003 Vendor=046d Product=c315 Version=0110 N: Name="Logitech Logitech USB Keyboard" P: Phys=usb-0000:01:00.0-1.2.4/input0 S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4:1.0/0003:046D:C315.0030/input/input74 U: Uniq= H: Handlers=sysrq kbd leds event1 B: PROP=0 B: EV=120013 B: KEY=10000 7 ff800000 7ff febeffdf ffefffff ffffffff fffffffe B: MSC=10 B: LED=1f

Truthfully? Here.

(But thank you very much for trying :))

Delete this, I just view the answer in one of my other questions.

@mitu yes, each controller works if it's individually pluged

@mitu Alright, that sucks to hear but guess i'll get to fixing it the physical way then. Thank you for the responses!

@dookieshooter You should delete/rename es_input.cfg and then re-install the emulationstation package, this would generate the correct es_input.cfg file. You'll have to re-configure your controls next time ES boots.

@bluecoffee said in Two MAME games, one works 2 player one doesn't:

Forgive my ignorance but how would I tell a single rom to use FBNeo?

You can use the runcommand launch menu to choose which emulator runs a rom.

Looks like the configuration is not properly saved, though it's not clear for what reason. Can you add more info about your setup, as asked in https://retropie.org.uk/forum/topic/3/read-this-first ?
Make sure your storage/sd card is not full.

@duglor

Just use hypseus, save yourself the headache.

Thanks you I'll give that a try.

@mitu Well, as always thanks for the help. I don't think it's underpowered given my new 3.5a CanaKit PSU made specifically for the Pi4 and it's a powered USB hub. But I can't rule out an unseated cable or something because now it's back to working correctly. I'm going to keep the USB HDD connected directly to the Pi, since if that isn't seen on boot, then it won't have access to the romsets which explains why they wouldn't show up, and if the USB cable to the hub got jostled then that would also explain why the gamepad wasn't detected.
#OccamsRazor

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

Post your /boot/config.txt and /boot/cmdline.txt.

BTW it's like I'm hitting F12 using the right dpad button. :/

@bbilford83 said in Yabasanshiro exit game:

@shavecat OK great. That I think I can help with. Go to \retropie\configs\all\emulationstation\ and you will see an es_input.cfg file as well as an es_temporary.cfg file. If you open up the former, you'll see a list of all the controllers your setup currently will recognize and their mapping. Each one will be introduced with a line that looks something like this: " <inputConfig type="joystick" deviceName="8BitDo SN30 Pro+" deviceGUID="05000000c82d00000261000000010000">." Now open the temporary one, and you will see it will only list one controller. Replace whatever is in there now with the correct controller info from es_input.cfg, then save.

At least for me, that fixes the emulator mapping in yabasanshiro so I can exit again, but I've had to do it again anytime I connect a different controller to my pi.

Thanks, I'll give it a try.

@jimmyfromthebay that's weird because I run my game-override configs from the "configs" folder and I've not had any issues.

What's this?:

configs.hdmi

...is it supposed to say that, or...? That's not standard, I don't think...