@mitu said in Display frontend on VGA666 CRT instead of HDMI with Pi4 and KMS:

Thanks for taking the time to answer!

I'm surprised this configuration worked with fkms, but I think it's no longer going to work on kms alone. I've seen your - similar - post on the RPI forums, the definitive answer if this configuration is supported should come from a RP engineer (6by9 is their expert on this).

Yeah, that's the first place I asked. I was hoping it was some stupid mistake on my side.

EDIT: one thing to note, the RetroPie image is currently based on the legacy RaspiOS buster version, a lot of work has been done on the pure KMS driver on the current Linux kernel. You can get the current RP Linux kernel with rpi-update (not recommended) or by manually installing RetroPie on current RaspiOS bullseye (still in beta at the moment), my recommendation would be the latter.

I did try a rpi-update as an extreme attempt, ready to start from scratch. Unfortunately the situation didn't change.

The other idea is to have a second Pi driving the marquee, which is a solution I have mostly working with one last annoying quirk that I wasn't able to iron out yet.
It would be great to do everything from one device though.

I guess you're using the RetroArch master for the switchres support added after v1.15 ?

Yes that's correct. And it seems to work great, possibly much better than the "old" Pi3-style runcommand trickery based on fbset and vcgencmd.

@mitu thanks foru tour answer, in fact i compiled manually attractmode when 'attractmode' was not available in retropie downloads script for raspberry pi 4 but anyway it's working like a charm.
So i guess if is there a way

Try updating RetroPie-Setup and installing attractmode again.

@mitu Thx. Never thought of that. Exiting one will just start the other and each will shutdown/save properly. Nice :)

@mrnoholster what happened is you updated fb-neo which requires a new rom set. The old roms are not for newer versions.
FYI. Updating arcade emulators to newer versions is risky as there is no guarantee that the update will work with your roms. Don’t update them if you have a working set of games. Most roms may be fine in if you just go up to the next update, but if you keep updating, there will reach a point where fewer and fewer roms run.

@mitu By saying that I use Archlinux, it was to say that I understand how it works. In the end I found the "xpad driver" bug. I could already see myself doing a new installation.

The only thing that doesn't work for me is when I run .sh to run retroarch, generate favorites ... from ssh yes. But it is a lesser evil that will have a solution.

My next system with retropie will already be a minipc with ryzen. That although I have all the consoles, I love to emulate.

I use the hotkeys for my retropie on tv...but for the arcade I find it much friendly without. When I need hotkey I just grab the wireless keyboard. The volume switch is already on the cabinet I’m using.

I have also notice on the new retropie image on retroarch hot key binds they added a double tap of the exit. Not sure if code on that can be adjusted as a hard press instead?

@BuZz Ah that makes sense i have a rpi4.

thanks,

@fullauto2009 An upgrade in place is not recommended, as it's not supported even by Raspbian. Note that attractmode is not compatible yet with the Pi4.

Hello,

Here is the solution I found :

1/ In the file /home/pi/.attract/emulators/Multiple Arcade Machine Emulator.cfg :

executable /opt/retropie/supplementary/runcommand/runcommand.sh args 0 _SYS_ mame-libretro "[romfilename]"

2/ In the file /opt/retropie/configs/mame-libretro/emulators.cfg

lr-mame2003 = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2003/mame2003_libretro.so --config /opt/retropie/configs/all/retroarch/retroarch.cfg %ROM%" default = "lr-mame2003"

3/ In the file /opt/retropie/configs/mame-libretro/retroarch.cfg

input_remapping_directory = "/opt/retropie/configs/mame-libretro/"

4/ In the file /usr/sbin/rgbcommander/rgbcmdd.xml , section MAME, place :

<emulator binary="mame-libretro" name="Multiple Arcade Machine Emulator" active="Blue" inactive="DimGray" arcade="1" retropie="1" retropiebinary="retroarch" reference="arcade">

5/ To continue using overlays (example for the game 1943)
Create the file 1943.cfg in the directory /home/pi/RetroPie/roms/mame-libretro/roms :

input_overlay = /opt/retropie/configs/all/retroarch/overlay/arcade-artwork/1943.cfg input_overlay_enable = true input_overlay_opacity = 0.900000 input_overlay_scale = 1.000000

and in the file /opt/retropie/configs/all/retroarch/overlay/arcade-artwork/1943.cfg :

overlays = 1 overlay0_overlay = 1943.png overlay0_full_screen = true overlay0_descs = 0

And the overlay image must be placed in /opt/retropie/configs/all/retroarch/overlay/arcade-artwork

6/ In the file /opt/retropie/configs/all/retroarch/retroarch.cfg, set the parameter config_save_on_exit :

config_save_on_exit = "false"

What specifically is it doing with Emulation station? Is there someplace in the scripts where I can swap out the executable from ES to attract?

No problem.
Oh and i would suggest testing out most of your games using fbalpha first before going to mame cause i found some games works better using fbalpha over mame.

@lamaman1971 Thanks for sharing. Definitely share your feedback on bezels, filters and the like with the community - there are plenty of people here in search for the perfect set up as well, so the more the merrier!

Cheers.

Thanks again.. i was working within emulation station to make sure things worked before bothering with attract mode.. but i did an update from binary and it seems my problem was fixed. Never woulda thought it woulda been a corrupt install from the start. That fixed a huge issue for me, and i shall now move on to the next. Thank you for your help. I build mame machines all the time so i understand the mechanics of mame and emulators, but using pi hardware introduces some curveballs.thank you again