This is occured infrequently and is likely some little bug. I've had it happen only 3 times and 2 were the first two times i was in the desktop and explorer. Only happened once in the last 40 or so times since. lol.

@mitu Will do - but will be later - am not currently home.

However - before I left - I did copy in a quick test - atari 2600 roms and bios.

Seems to run fine.

Will grab the logs later

@Chef-Otis said in Hdmi banner flashes everytime I load and exit a game:

It forces the fullscreen, even though it was saved.

Fullscreen is set at runtime by runcommand, as a an additional configuration. I guess the 'fullscreen' video mode may be different than the 'current' video mode (even if 'current' video mode may have an identical resolution) - that's the reason I asked for the results of the tvservice commands, which should display all video modes reported by the monitor.

@mitu said in pi5 CEA 1920x1080P impossibile to set:

Can you please post the output of the command I asked in my last reply ?

Hi MITU I finally solved problem with HDMI on Pi5 with Retropie:
First of all i have bought this KVM EDID Standard Emulator

https://a.aliexpress.com/_EzdWnJX

Second problem are margins:
So I have modified
/boot/firmware/cmdline.txt
From:
video=HDMI-A-1:1920x1080@60D

To:
video=HDMI-A-1:1920x1080@60mD, margin_left=56,margin_right=56,margin_top=28,margin_bottom=28

And now finally my Pink (english) TV CEA works at 1920x1080p 60hz 148.500mhz
And EmulationStation is Centered and fit the screen (also in terminal).

So I think that KMS driver VC4 inside of Raspberry pi5 isn't compatibile with all possible vsynk + and hsynk - or inverted parameters of polarity, is only compatible with vsynk+ and hsynk+.
The KVM emulators (around 3 dollars) solved all my problems.

@mitu Right on. Thanks so much for the info!

Emulator crashes on the Pi5 (which is still pending support) are usually caused by the 16K page kernel used by default in RaspiOS. TL;DR: modify /boot/firmware/config.txt and add kernel=kernel8.img at the end.

If you wish to run the standalone emulator, you can modify the controller bindings by starting the GUI and using its configuratoin menus. Install the desktop, then start it and then execute /opt/retropie/emulators/dolphin/bin/dolphin-emu to get the emulator's GUI/menus.

Awesome thank you for that, now connected via bluetooth :)

sudo nano /etc/bluetooth/input.conf
ClassicBondedOnly=false

@YFZdude you rock, thank you!

@dandaman Hm, I wonder if you haven't activated something like Turbo mode in RetroArch for P2.

@CDNSailor ok, so after getting home and opening my Pi up, I tried plugging the controller directly to the system. Lit up and was picked up immediately. Still can set it up, but I did run a jstest. It's definitely my splitter that is causing the issue with the pi seeing the controller. That said, now I'm going to fiddle with the drivers and see if I can get that one to work. Of that works, I'll be half way there. I just wish I could know exactly what the splitter is doing that is choking it off. If it's power or data throughput.

@Alessio2001, I ran into this same problem on my last Arcade conversion. The issue ended up being on the CRT side. You should have a control board with 6-8 knobs. Mine was a small square one, but they can be different. This controls the image on the CRT. You can use this to change the Vertical Hold (height), Horizontal Hold (width), and contrast, and some have R/G/B knobs. One of those, when you change it in one direction, made my image duplicate, flicker, and rotate on the screen. When I turned it in the opposite direction, it solidified into a single image rotating from top to bottom. Eventually, it would slow down and stop in the middle of the screen.

The RetroPie image doesn't fit in just 1 partition. It's based on a Raspbian Lite image, which has 2 partitions - one for boot (formatted as Fat32) and one holding the Linux installation (formatted as Ext4). So creating just 1 partition on a drive will not be enough if you intend to boot/start the RetroPie system from that drive.
You can start by writing the RetroPie image on the drive, then boot it once to run the re-sizing step, then resize the 2nd partition to a sensible size to hold a RetroPie installation (15Gb ?) and then create the rest of the partitions you want to have on the drive - one for ROMs at least and possibly others.

Do note that if you have a large-ish drive (4T or larger I think) that requires a GUID Partition Table (GPT) then booting from it is not supported by Raspberry Pi boot loader.

@RapidEdwin08 said in GZDoom and OpenGL error:

but it may not be the best option for a Raspberry Pi.

Depends on what you are doing with it.

I have gzdoom installed on my pi4 which is a little OC and as long as I don't have heavy mods going. It plays very well.

Some slow downs for sure but if you edit it right and use the right mods. You definitely can have fun.

On a pi3 though I can see it being more of a problem

The runcommand dialog prompt which you get is actually present since the game start, it's just obscured by the emulator that starts and overlays on-top of it. The dialog being present after the game ends means that the emulator hasn't actually exited/stopped - in order for EmulationStation to pick-up and start - and it's stuck somewhere.

This may be a sdcard issue - emulator tries flush some state to the disk on stopping the game or saving the options file and not being able to will block the emulator. Your log file is strangely formatted (did you copy/pasted from a SSH session or OCR-ed a photo ?), but it doesn't show the emulator actully stopping, which would show something like:

.... ^C[INFO] [Core]: Content ran for a total of: 00 hours, 00 minutes, 04 seconds. [INFO] [Core]: Unloading game.. [INFO] [PulseAudio]: Pausing. [INFO] [Core]: Unloading core symbols.. [INFO] [Core]: Saved core options file to "/opt/retropie/configs/all/retroarch-core-options.cfg". [INFO] Threaded video stats: Frames pushed: 244, Frames dropped: 0.

If you have SSH available, you can the emulator through strace and the post the strace log archived somewhere (it's going to be too large to post the contents as is), just to see where it's stuck. Stop EmulationStation and run:

strace -f -o strace.log /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fbneo/fbneo_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/frogger.zip"

then exit the game. When it gets stuck, then save the strace.log file and upload it somewhere.

EDIT: strace is not installed by default on RetroPie, but you can install it by running sudo apt -y install strace. I also advise to update RetroPie in order to get the latest version of RetroArch and OS packages available.

@terr0rgasm Enabled is the default, otherwise RetroArch's controller profile would not be created.

@insx said in Is there a simple way to make DragonRise controllers work with Daphne??:

@DirtBagXon

I'm pretty sure I did exactly this, I tried it several times to make sure I hadn't typed something wrong.

git clone https://github.com/grant2258/daphne-emu.git tmp/build/daphne

Let me append to my previous answer.

...or the repo doesn't exist :)

@10vorne said in Dosbox CD not found:

I was actually aware of case-sensitivity, but I had the feeling that it didn't matter when it came to directory information in the conf files.

Yes, you'd expect (DOS) commands run via autoexec to behave similarly to real DOS (i.e. case-insensitive), but imgmount may be one of the exceptions since it's used to interact with the host (Linux in this case) filesystem.

Yup, all good here now :)