If your IPAC configured as keyboard, did you check that the buttons register as keys - either in Windows or Linux ? What files did you modify for configuration ? It would be helpful to know something about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@YFZdude Alright man you are the winner, I had been doing config edits all day yesterday and tried both HDMI-D ports during those edits, and at some point at the end of the night when I did the hdmi_group 1 and hdmi_mode 16 edits I did not test the cord in the primary hdmi-d slot as I had thought. It figures the one edit I added in that actually works is the one I stopped testing both slots on. I have the pi 4 in a case so remembering which slot was the primary was my user error. What a nightmarish night for something so simple, thanks again to everyone in here that helped out. It runs in 1080p now. Edit: The resolution to the problem was having the hdmi cord plugged into the primary slot (nearest the usb hub) on the pi 4. User error.

@zerojay You're welcome, I'm glad it helped you. I hope having a clear topic like this addressing this issue helps others as well.

@alt126 said in Arcade & Mame resolution: What I have to modify to have a better resolution? Resolution is fixed, you can't change it. The only thing you can do is apply filters, which is exactly what your first screenshot is about : there is a blurry effect on it. It's probably retroarch's bilinear filtering, you can find it in retroarch menu : Setting > Video > Bilinear Filtering. Well, i think that blurry effect is horrible tbh, it feels like i need glasses, but i guess everyone has their own tastes.

Thank you! I have also discovered that moving all the ROMS from /arcade/ to /mame-advance/ did the trick it seems too. Thanks again!

@mitu I added: hdmi_ignore_edid=0xa5000080 to the config.txt in the boot partition, just above #config_hdmi_boost=4 on line #35. That seems to do the trick. Excellent, thank you.

Ok, seems it only happens with Damaso images. I have tried a different one, and no troubles so far. :( Sorry for bothering everyone in here

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 ?

@oskeeeddie Re-install/Re-enable the RetroPie shares from the RetroPIe-Setup script and see if you get all 3 shares back.

I have just fixed the Fault runcommand-onstart and runcommand-onend scripts Runcommand can execute an user script before the game launching (runcommand-onstart.sh) and after exiting the emulator (runcommand-onend.sh). Both scripts must be placed at /opt/retropie/configs/all/. These were the settings. I changed them to 1024 768 fbset -g 320 240 320 240 8 fbset -g 320 240 320 240 32 Not sure how these are changed, but hey :-)

@KRAKATOA you are a life saver. It worked to perfection. Thank you!!!!

@mitu Yeah -- there's no error message readily available when the runcommand dialog isn't shown. I should probably just do a clean install since that is the recommended route, likely something didn't upgrade correctly at you say.

@Clyde I’m not angry at anyone here. But this does further solidify my anger with the vendor. I see now that this is a topic discussed often here. I find it interesting that the company is willing to sell “kits” with pre-loaded RetroPie but their contact number explicitly states that they don’t support 3rd party products. I’m sure there are many people who buy these thinking they are basically plug ‘n plays as that is how they are advertised, essentially. That’s why I initially purchased a 60-in-1 JAMMA board, as I was intimidated by the apparent complexity of working with a Raspberry Pi, having only basic computer knowledge. I will consider just reinstalling the actual RetroPie image, but will need to chat with my friend to see if he will be able to assist me. I will probably save the few ROMs I want to keep, as there is a lot of useless stuff I don’t care about. Thanks!

Hey dank, thanks for the heads up; I kinda figured they would be, yeah. I'm just using them as a basis to create my own such that the screen gets positioned right, ie. for the x and y values. I certainly wasn't gonna just lump them all in there. While I'm here, did Naomi get borked in the last few weeks? Suddenly the ROMs I have for that don't work (since I had to reimage I mean). You know what, never mind, forgetting so many things already done several times over: BIOS!

OK.. I fixed the issue, but this is a little odd. Apparently, Controller 1 (Player 1) has to be in USB1 on these 3040's, Controller 2 (Player 2) in USB2, etc, etc. Is this a unique situation for the 3040 or is this a universally known fact in RetroPie land? If it is, then I apologize for not doing more research. This may just me being a little more Windows oriented than Linux oriented, but does it really matter which slot the controllers are plugged into? I'd think that the programming of the controllers would follow the unique ID and not care about the USB Slot at all. Thoughts?

@ScoobyAA Slightly late reply. I have only just come back to this project. I finally have TwisterOS running well and Retropie does work. However, even using controller keymapping software I cannot use those controllers. This issue is clearly much deeper than just retropie because no software recognises the left and right arrow keys, unfortunately. I really appreciate all of the help from the forum though. Thanks!

Normally the Pi should switch to composite if the HDMI port is not connected, but you can force PAL by adding sdtv_mode=2 to the config.txt configuration file. Assuming your composite cable is correct and you've switched the TV input to the RCA input, you should get an image.

@mitu After running lsusb, I can see the adapter as follows: Bus 001 Device 004: ID 1292:4154 Innomedia Retro Link Atari cable Using the vendor and product codes from above with 0x appended to each to look up 0x1292:0x4154 with the search term quirks, I found documents referencing this is the option that corresponds to the vendor and product info for my device: options usbhid quirks=0x1292:0x4154:0x040 Some of these include the following sites: https://github.com/libretro/Lakka-LibreELEC/blob/master/packages/libretro/retroarch/modprobe.d/usbhid.conf https://github.com/msteinbeck/hid-retrobit/blob/master/DETAILS.md I edited the /boot/cmdline.txt file and added the following to the end of the line of text: usbhid.quirks=0x1292:0x4154:0x040 After rebooting, I can use the following commands to test that both controllers are working: jstest /dev/input/js0 jstest /dev/input/js1 Thanks for the help!