Try using the Gnome on Xorg session to log in, instead of the default (Gnome on Wayland). The issue occurs because of the Wayland session and SDL's fullscreen mode, which doesn't cover the entire screen.

@lostless thank you so much for the reply as I am new to the retropie community am bit of a bit of a noob to retropie and the ins and outs but I can get a keyboard and a cheap laptop tomorrow then what steps do I take thank you again
**

@mahoneyt944 ok that sounds easy enough. Thanks!

@DTEAM Please open a separate topic and post a verbose RetroArch log, along with the details of your system.

@mahoneyt944

Great info, thank you sir!

@ganatbasa please add some more info about your system as detailed in https://retropie.org.uk/forum/topic/3/read-this-first

It sounds like you may have acquired a system pre-configured and "ready-to-go." Note that, because it is not practical to troubleshoot a system that neither you nor we have any idea how is configured, third-party builds are officially not supported in any capacity. If that is indeed the case, you'll need to start over with the default, official image from https://retropie.org.uk/download. Start here: https://retropie.org.uk/docs/First-Installation/

(Unofficially, it sounds like your aspect_ratio_index may be misconfigured in /opt/retropie/configs/all/retroarch.cfg or possible elsewhere.)

@mitu
Ok, I solved the issue.
The pad has a switch on its back to commute between different modes (Windows, Mac and so on).
It must be set to 'X' in order to be used with Raspberry; I found this suggestion on a Reddit post, since it wasn't mentioned in the walkthroughs I read on the web (or at least I missed it)...
By the way, I paired the controller again and tested it successfully with several games!

Thank you all very much for your help. Everything turned out updating the script retropie_setup.sh . Thanks a lot

[..[
already tried on samsung, and tried second hdmi port.
will show up list of starting services.
show splash screen.
show again list of starting services.
then blank screen.

Seems like when the resolution change or a busier GPU/system results in the black screen.

[...]
well, i feel it's firmware.

already tried batocera (2 different version), lakka, recalbox, retropie (3 different version & my backup 2 *.img from (2019)).
the symptoms are same.

Then the issue is not software - but a hardware one. It's strange because the hdmi_safe should boot with a very low resolution, which should help with wonky HDMI cables that fail on 1080p. Having the image shown on boot means the HDMI port is ok. Since you get the voltage drop icon, I'd say it's the power that's faulty.

pls don't try sudo rpi-update i don't want you guys get like me.

That's not recommended for regular updates and you shouldn't use it, especially since Buster based system may not getting the same testing by the RPT teams, with the latest kernel/firmware.

[...]
i'm curious with you guys, can help me with run uname -a, sudo vcgencmd version and run via ssh emulationstation --debug where it can run emulationstation. so i can compare and will try figure out

The EmulationStation log is the same, the firmware/kernel version are probably different on a system where rpi-update hasn't been run. The version will not help you much, but if you want to revert the rpi-update changes, you should reinstall the kernel/firmware by running

sudo apt-get install --reinstall raspberrypi-bootloader raspberrypi-kernel

Screen tearing is a issue of the Raspberry Buster Lite that the current RetroPie image is using. The upcoming version i think it will get rid from this issue.

Some users solved this issue, in the current version of RetroPie, after they use the experimental kms driver, but this add other issues. If you search in the forum about screen tearing you will find a lot of info. Also i recommend to read the wiki about the used of 4k TV with Rpi4: https://retropie.org.uk/docs/Pi4/

@kiwiglen said in Help with wiring my arcade:

Retropie menu key, coin, and the 1/2 player

1 Player would be P1 Start, 2 Player P2 Start... same for coins P1 select and P2 select, the menu is somewhat tricky ... if you want to put that on a single button (without a hotkey), the hotkey must be disabled (AFAIK) and then EVERY function you want to use (save/load/save state select/volume/etc.) must be mapped to its own "key"/"button" within the retroarch.cfg config-file. Another possibility would be to connect the "Menu"-button to P1 Select (hotkey (default), or to whatever "button" is configured as the "hotkey") AND to a the "Button" which is configured to open the menu ("X" is default) - as you still need to connect the select and x button on their own, you need to build/rewire/crimp the plug/connector(s) to the controller.

Edit: IMHO with that "encoder" going without a "hotkey" and forfeiting a dedicated menu-button is the less troublesome route here.

@sleve_mcdichael mupen64plus-gles2rice = "49-36"

Yep that was it! Was getting my Select and Start buttons confused.

Setting the Hotkey to the same key that I had assigned to Select (and not Start) fixed it.

Cheers

@Tanzbärli did you manage to get a more recent kodi update?

@mitu Ok. Thank You.

.. and now the needed EmulationStation changes are available in the stable ES branch. Thanks @BuZz !

@hopwon https://www.sindenwiki.org/wiki/Barebones_Compatibility is the best resource for games compatible with sinden guns. HOTD2 works best on Dreamcast lr-flycast.

@Striderx99 It looks like updating the .cfg with those settings and uploading it did the trick. I guess that wraps this issue up. I tested it with three games and they loaded up fine. If anything like this happens with any other emulator, I'll know what to do. Thanks for your patience.

@mitu
Yes, I will try changing the ROM file. I am using lr-stella2014 as the emulator.

EDIT: I figured it out. On the retroarch menu settings the controller was set to stella adaptor paddle controller. I set it to gamepad and it works now! I remember one day I was trying to use a pc mouse as a paddle, and I must have changed controller setting to paddle and kept it by accident. Sorry about that! Thank you!