Post Update:
With this command I can display without problem "image-test.gif" in this case, I think the problem is something in the retropie configuration that I can't see

pi@raspberrypi ~ $ sudo apt-get install fbi pi@raspberrypi ~ $ wget https://ozzmaker.com/piscreen/image-test.gif pi@raspberrypi ~ $ sudo fbi -noverbose -T 1 -a -d /dev/fb1 image-test.gif

config.txt.PNG
(/boot/config.txt)

@buzz another good guy here full of legal stuff :P

https://www.amigapple.com/categories/raspberry-pi-solutions/822348

@buzz if you can report this one

https://www.amigapple.com/categories/raspberry-pi-solutions/822348

@muldjord thanks for answering my question.

@mitu Alright, moved those over and everything seems good! Only issue I'm running into is that in any game I get a pop up that says "✔️ USB Gamepad (121/17) not configured" even though I moved over the config for the same controller.

@sleve_mcdichael hey thanks for the speedy reply! it worked! thanks again! GAME ON!!!!

@clyde ah, I hadn't considered converting them directly in the cache. That would save the trouble (and the bandwidth) of downloading them again just to do the same conversion anyway.

Pi Model or other hardware: 3 B
Power Supply used: inland 5.25V 2.4A Micro USB
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): I think 4.1?
Built From: Standard; haven't added any images or anything like that
USB Devices connected: Button converted to usb, keyboard
Controller used: none (unless you cant the button and joystick)
Error messages received: no error message, the screen just looks off
Verbose log (if relevant): idk what this means
Guide used: (Mention if you followed a guide): am following and using the parts from this youtube video:

Also looked up how to screen tilt (did the screen rotate 3) and remove black bar (took out the # in that code)
File: Don't think a file is the error, as it works fine on my monitor but not the arcade1up
Emulator: (Name of emulator - if applicable) using the retropi with atari and nintendo
Attachment of config files: don't think its a files issue as per the reason above
How to replicate the problem: to replicate the problem use one of the machines with a vertical screen (Ms. Pacman, for example) and use the parts that are listed in the youtube video: HDMI LCD Controller Board: https://amzn.to/2QlKKfr , Arcade Sticks Buttons and Encoders: https://amzn.to/2ItwRt5 , Pi 3 B

@br23z I guess my first question would be "What is the difference between Ape Escape and your other games?"

What format are you using? BIN/CUE, ISO, ZIP, M3U? According to the docs ZIP files are not recognized. Do the images work on your PC? I'M NOT ASKING FOR THIS TO BE ANSWERED OUT LOUD 🤫 just ask yourself in your own mind - are they all from the same source? Did you rip them all the same way? Etc?

I'm no LINUX programmer so I can't suggest anything that way BUT my common sense tells me that if one works they all should if supported. My troubleshooting sense tells me to look at my images first then move out from there.

@clyde I thought about doing just that but I have exactly enough SD cards right now to run the Pi setups I own so I don't have a spare to test on.

So I agree - the best way is to test it, yes, but the easiest thing to do is ask if anyone has already done it. Avoids the whole "re-inventing(re-testing?) the wheel" thing. I figure if I don't hear from anyone in the next few days I'll attempt it on my next day off and report back. :)

@dankcushions Thank you.

I found the solution:
RA changed recently the way the "Digital to Analog" operates.

switch ATD mode to "Left Analog (Forced)", as in input_player1_analog_dpad_mode = "3".

That works!

@gaz I am out of ideas here, and having never used the Lightgun outside of the Raspberry Pi, I would definitely suggest bringing this back to the Sinden Lightgun discord, as Andy will likely be able to best help troubleshoot the scenario.

Specifically, if the gun works in other software such as the test apps, it might be something simple that I am not knowledgeable enough nor experienced enough to detect. The Linux-specific channel there might be the best to get to the bottom of this, but do share whatever you find here, as if there's something that we can change on our end I suspect we'll be happy to accommodate.

Sorry about that.

@pmdci

One thing that Iv'e read should improve (some)things is editing this file,

sudo nano /etc/systemd/system/bluetooth.target.wants/bluetooth.service

look for a line like the following and make it like below.
(maybe make a backup copy of the file first if you want)

ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=sap

Iv'e been messing around with RPi4 bluetooth and my DS4 controllers recently and that is now part of my setup steps.

They were on the latest update.
I already figured it out for myself.
I've uninstalled the xpad and xpadneo drivers from the RetroPie setup utility.
Then I installed the latest neoxpad driver from github, with this patch applied: https://patch-diff.githubusercontent.com/raw/atar-axis/xpadneo/pull/283.patch
Finally I edited the /etc/modprobe.d/99-neoxpad-bluetooth.conf file, comment out the disable ertm thing and make sure to load it with xpad emulation enabled:
# options bluetooth disable_ertm=y
options hid_neoxpad xpad_emulation=1

Reboot and pair both controllers in xpad mode.

Setup both controllers in emulationstation and skip the non-working left and right triggers.
When done simply close emulationstation and add the triggers manually:
input_r2_axis = "+5"
input_l2_axis = "+2"

Et voila!

Both controllers working in x-input mode, without the shitty startup delay when launching retroarch and working rumble for my psx and dreamcast games.

You can disable any hotkey enabled functions - and leave only exit - by modifying the controller's configuration file, which you can find in \\retropie\configs\all\retroarch-joypads.

@stuckinthe90s If Mitu's suggestion to check "in emulator" or "in game" for overriding video mode settings doesnt work, I had a similar problem the other night on a Pi Zero..... i had a message floating across the screen saying something to the effect of the input signal is not compatible. I ran raspi-config and found "Display Options" then "Resolution". When i opened it was set to something in the middle of the list.... I arrowed up to the top of the list and found "Default Monitor preferred resolution". I selected that and rebooted. IDK if the Pi4 has the same config( i only have a ZERO and a 3B+... and am also quite green in the ways of Pi). That change fixed my issue. Not sure if that is the best way, and i haven't done much testing to see if there are other issues caused by that fix. Best of luck. -D

Did you modify any of the core options ? You may want to remove them from the core options file and try again.

RetroArch's version is pinned in the install script, installing from source will still get you the pinned version. If you update your RetroPie-Setup script, the latest version available will be 1.9.7.

If you wish to build the latest master or and another version, you need to modify the retroarch package script and change the branch used here. Note that RetroPie applies some patches to the source (here), if they don't apply correctly to the version you want to build, you'll need to comment the patches before installing from source.