@mitu They are registered as axis movements. The gamepad is compatible with Linux and works well for me.

Looks like a bad sdcard or unstable overclock. What 'single commands' mean - running a game or actually starting a program ?

Please add more details about your setup, as asked in https://retropie.org.uk/forum/topic/3/read-this-first.

Could be an emulator issue (regression) or a missing BIOS file ?

Please add more info about your setup, as requested in https://retropie.org.uk/forum/topic/3/read-this-first, and a verbose log from the emulator. Use pastebin.com for posting the contents of the log file.

@texmansru47 did you manually install either of amiberry or lr-puae? The optional packages are not installed by default.

@sleve_mcdichael Ok it will take me a lot of time then, but I am really passionate about this project. It’s called Retro Ally. I’ll use Pygame to incorporate UI and install custom emulators. Thanks for your help

@sleve_mcdichael That was it... Thanks! I just couldn't remember.

tvservice doesn't work correctly with the KMS/DRM drivers, which the Pi4 is using since it was released. Your Pi3 setup and script(s) are not going to work on a Pi4.

Furthermore, the entire legacy GPU stack has been discontinued in recent RaspiOS version, starting with Bullseye (Debian 11) and continuing with Bookworm (Debian 12). tvservice is not even available anymore on the latest RaspiOS (Bookworm).

EDIT: if you're trying to use a 'super resolution', look up the 'SwitchRes' support in RetroArch, which understands KMS/DRM.

@sleve_mcdichael

Sort, thank you

@duglor In the RetroPie docs you will find all the necessary info about the bios files of openmsx: https://retropie.org.uk/docs/MSX/

The only you have to do is to choose the emulator from the runcommand menu.

The issue will be fixed upstream, one way or the other.
As a temporary workaround (until this fix is merged), you can try installing libhidapi-dev manually and then re-run the installation from the RetroPie-Setup script.

@sleve_mcdichael Thanks for your help. Swapping USB ports doesn't work, perhaps because the iCode controllers are all linked to 1 USB connection. The script looks very cool, and I think would solve the problem except for assigning controllers per individual games within rom's (the script handles global and rom-specific, but not individual game setup). I assume it just links to retroarch config, but I'd have to use some method to reassign while within each game I'd like to customize.

@MeduZaPaT nope, not got round to it yet
I got sidetracked by a new build.

@mitu thank you very, very much for the help and information about kernel. :)

@Fantasens said in Sound not working with HifiBerry Rapberry Pi 4 with OSMC:

Is there no way to configure Retropie so that it behaves like Kodi by playing audio from both the TV and the Audio card?

'RetroPie' - or rather EmulationStation - uses ALSA. If you can configure ALSA so that it behaves like Kodi with the default card/output, then EmulationStation - and probably emulators - are going to work the way you want.

The only configuration for ALSA that RetroPie does is the one from the Audio menu, where you can choose between the audio outputs present on a Pi - Analog/HDMI. For more complex configuration you'll need to configure ALSA yourself.

@mitu you're exactly correct. I ran dos2unix on the file and it works as expected. Thought about /r not being a thing in unix files 30 seconds after I posted.
No clue how it happened, both were edited in notepad++.

@Meiner said in Can't start SuperTux:

that means RPi4 has support for OpenGL20 on buster but RPI3 doesn't?

Yes.

@navyseai said in Is Retropie dead?:

python 2

Bullseye Buster was (due to the reason that Python 2 EOL was in 2020 (IIRC)) the last OS that came with python 2 and python 3, Bullseye and Bookworm are Python 3 only (retropie builds fine on each of them (32bit flavour), not sure whether 64bit still includes some culprits (though mine seem to be working fine (Bookworm 64bit/Pi4), but that is just running with a few selected systems)).