@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 :)

@abj OK, solved. Upon reinstalling I got a message to copy the es_systems.gfg from the etc/ folder to opt/configs/all/emulationstation/

Thanks for your help! Be well!

@mitu Thank you, youve made a grown man very happy

im not sure how this interacts with retroarch overrides as no video mode was selected in the override .cfgs the log file referenced but all i did was updated retroarch from binary to latest 1.16.0, loaded the same rom and i got a msg on lower left configuration override loaded but can change video mode from the runcommand launch menu and it now works.

i can now can select 50zh video mode and get smooth scrolling on PAL and on Amstrad CPC :)

@mitu Hi, just a quick follow-up that downloading from source (MAME 0.263) has resolved this error for me as well. Thank you!

@mitu I have a raspberry pi model 3b+ and I use this to power my raspberry pi (12v to 5v converter inside unit, 2.5A) while using the joysticks for my arcade machine: https://www.jaycar.com.au/raspberry-pi-retro-arcade-game-console-with-hdmi-port/p/XC9062

Retropie version 4.8

@Thorr69 could you elaborate on what file that would be? When I had used a 16gb USB, the romset I had totalled almost 16GB and it seemed to have been causing issues until I swapped to a larger capacity USB so I doubt it would have been a log file issue?

@sleve_mcdichael that is correct

@Aroenai said in Fresh RetroPie install on Debian 12 x86_64, keyboards not recognized in emulationstation:

Built From: Debian 12 net install (no GUI, installed to external USB 3.1 flashdrive) installation script from https://github.com/RetroPie/RetroPie-Setup

Actually now I noticed this - we don't support nor test running from the CLI on a PC, a desktop environment (X11/Wayland) is required on that platform.

If you still want to run it via KMS/DRM, check if your user is part of the input/video/render groups.