@Omay said in Jack of all trades controller needs:

What buttons would I need to be able to run just about any game that RetroPie supports?

Supporting 'any' game is a tall order, since imitating a PS1/Xbox style controller may not work so well with a cabinet style panel - operating 2 joysticks for 3d game while at the same time having to push buttons is a bit cumbersome.

For an arcade style cabinet you may want to use a traditional arcade cabinet with an analog joystick + 6 buttons for actions (A/B/X/Y + LT/RT) + 2 buttons for Start/Select. Optionally, you may want to add a separate button for the 'Hotkey Enable' button used by most libretro emulator - that one can function also as a 'Menu' or 'Exit' button for other (non-libretro) emulators.

You can also use an external (Wired/Wireless) gamepad for more modern games - i.e. PS1/Dreamcast games which require a joystick + D-Pad.

@brucetablett said in Raspberry Pi 4B, Retro pie registering D-PAD as analogue stick:

do you know any gamepads that works fine? Should I buy a 8bitdo-controller perhaps and not some 20dollar knockoff?

I have a Logitech F710 that works well. Other people seem to like the 8bitdo controllers but I've not used one myself; look for one with a 2.4gHz wireless dongle, as the built-in Bluetooth tends to be less-than-stellar, I have heard.

@sleve_mcdichael said in Can I configure two turbo buttons?:

Use classic mode and whatever your main "fire" button is.

Well, of course... It's so simple, it's genius. Wish I thought of that! Anyway, this way works a treat, so thanks for your insight.

This works fine if none of the buttons have a "hold to power up" feature but if they do, it'll be difficult (or impossible) to use effectively.

AFAIK, In The Hunt doesn't have that, so I'm good.

@10vorne said in Samba and /opt/retropie/configs:

@sleve_mcdichael Just to be sure, the config folder shared by Samba by default is the config folder under /opt/retropie/configs?

That's correct. You can look inside it and verify.

@Robinson No, you copy the ROM files directly into the folder, and that's true for each system - you don't have to create separate folders for each ROM.

@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.

@duglor Hi, on the Apple 2 emulator, when you hit f9 to change palettes, can you save the change on a per game basis or only the entire system? Be well!

I found a keyboard with an F12 key and was now able to call up the menu. I also managed to change the hotkey so I`m able to access the menu via the attached joypad. However, I can't move around in the menu with the joypad, and buttons don't seem to be perceived in the menu either. In the game, on the other hand, the joypad works perfectly. I've been through every menu and have really tried a lot. Does anyone have an idea how I have to set something where so that I can use the vice menu with the joypad?

@mitu yes, each controller works if it's individually pluged

you can close the discussion, I solved the problem, I don't know why but I had to overwrite the tos file in the bios and everything worked again

@Robinson https://retropie.org.uk/docs/Logitech-Controller/#directinput-xinput-switch

Xinput is newer, and recommended.

@mitu
Nevermind i think that i am missing the dc_boot.bin thanks for trying to help

Please don't double post - I deleted the previous post.
As to your problem - the Bluetooth pairing configuration is mainly geared towards input devices (i.e. gamepads) so it might not work 100% with other device types. You can still pair it using the bluetoothctl command line utility (see https://wiki.archlinux.org/title/bluetooth, the Pairing section).

@roslof That looks awesome. I'm glad I could help and be part of it.

I had more than 500+ attempts with Piston Hurricane on the Pi 4 and somehow could not figure out what all I was doing wrong.

Fired up your suggested Bizhawk tonight.

Landed this money shot on only my second attempt.

alt text

Tied for world record!

Next, I'm coming after you Bear Hugger. :D

Thanks again for the help through this, Mitu.

@barbudreadmon Been a while, found another: retofinv

@antsgamingau Additionally to retropie's arcade documentation, you might want to read the more detailled libretro's arcade documentation.

It's a bug, but something that shouldn't affect many users since it wouldn't occur without this symlink loop. It's probably affecting also the reading of the ROM/game folders, which would make EmulationStation freeze on start-up in this kind of scenario.

The functionality provided by the fbtft module has moved to an overlay in 5.10, you can try to use the overlay to configure your display.
The 4.7.1 is using the 5.4.72 Linux kernel version, if you need an earlier version you may try the 4.6 version, though I'm not sure which Linux kernel version is used in 4.6. Older versions are unsupported, but from 4.6/4.7 you can upgrade to the current RetroPie version and skip any Linux kernel updates.

My advice would be to try and use the overlay method to configure your screen. RetroPie uses a RaspiOS Lite (buster) as a base, so any instructions that apply to RaspiOS (Raspbian) Lite should work on RetroPie also.