@gruik said in Retropie on Raspberry pi 5 + 5:4 DVI Black Screen:

Now that I read it again, I feel dumb because it's called "legacy" and explicitly says that the hdmi filter is for the pi 4 only...

Yes, and in this context 'legacy' means every Pi model with recent RaspiOS (Bullseye or up), not just the Pi4.

@mitu

Hey sorry for the long delay, yes it is 64bit

I didn’t have time to look at it for a long time and got back to it, a reboot later and reinstall of retropie yealed me no errors and seem like it installed fine

So no idea why it threw a fit the first time, anyway I love it! Very happy I came across RetroPi!

@mitu I did what you recommended and it worked! The interface is working as it should.

@Sever just brainstorming: do you have "Settings > Latency > Run-Ahead" enabled by any chance?
Just asking because i had a very similar issue a couple of years ago when i started with lr-flycast and this (deactivating run-ahead) solved it.

@mitu Yeah, I figured it shouldn't have any effect on audio output. The only audio settings I've changed are in /usr/share/alsa/alsa.conf, where 2 is the number of my audio device:

defaults.ctl.card = 2 defaults.pcm.card = 2

@MinivanDriver i noticed a ; too many in front of the name [USB Gamepad] in the /opt/retropie/configs/n64/InputAutoCfg.ini file

Example:

; InputAutoCfg.ini for Mupen64Plus SDL Input plugin

; USB gamepad_START
[USB gamepad]
[SWITCH CO.,LTD. Controller (Dinput)]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
Mempak switch =
Rumblepak switch =
R Trig = button(5)

Etc.

Remove it, and try it. I think it prevents the .ini to start the pad configuration

@Lolonois I now have an issue where it's scraping some systems and not others, and when I scrape individual systems, some of the scraped systems are undone.

Could this be because I moved the cache folder?

@sugarfree @capcob
I think I Hardcore derped...

I've yet to open my HAT, but have built and put the pi in the case shown.. ..
This is what I had bought for my SSD
71e8d76f-a25b-4a0e-a517-5887817f85d6-image.png

I didn't realize it went beneath the PI.. will that cause any issues?
I've not bothered doing anything since I am waiting for the PI5 Pre-Made Build

@ExarKunIv thanks. Will look into these unofficial ones you mentioned

I am not sure what to suggest, a Pi4 with 2GB would have been my answer in pre Pi5 times... and still, the Pi4 runs an official image, but the pi5 ain't such a newcomer nowadays and the official image is still based on (IIRC) buster and since then, even before the Pi5 was released, the discussions where about when there will be a "bullseye" image and whether it will be 64bit/32bit or still in support of 32bit ... sigh...

So the official image is missing debian 11, the 64 vs. and or 32 bit problematic still unsolved and now with the pi5 we are over the edge to 64bit and on bookworm as the current debian/raspi OS base...

I would say, it depends... if you want to play straight ahead and use the existing image, go for a pi4 with whatever mem you may need to reuse it after upgrading retropie to a newer device (for retropie on a RP4 2GB is IMHO more then enough, if you want to use it as a terraria or minecraft server afterwards, at least 4GB better 8 would be the way to go).

But if you are totally new to raspis and retropie... well, bad timing, if you simply can afford it, go for the above mentioned route of the pi4 and learn some *nix basics ... but be assured that all you learn for the nowadays official buster based image is void for the next official one, because too much on the underlying OS was changed (just to add a match of buzzword: config.txt vs. cmdline.txt) - if you are willing to experiment and learn on raspberry pi/*nix in general in the meantime, go for a pi5 with the memory you can afford!

@mitu

Okay I understand now, thank you mitu 👍🏻.

@kylen12 said in Connecting Playstation 2 Controller via GPIO Pins:

Do you think it is feasible to have a Python script that would do so?

Probably yes, but I'm not famiiar with the SPI ecosystem on the PI. There's https://github.com/mholgatem/GPIOnext which is a simpler input simulation library (i.e. 1 GPIO line = 1 input/button) and can provide a starting point for the 'virtual' input device creation, but for the SPI part I'm afraid I have no idea.

I got it to work by researching kernel. I ran lr-parral64 and edited a line in retroarch config. Thank you for your help!

had the similar issue and

Here it is, I've updated via setup script

use_art = "0"
disable_joystick = "0"
governor = ""
disable_menu = "0"
image_delay = "2"

@manD0rk Please, start a new topic and add the necessary info, see: https://retropie.org.uk/forum/topic/3/read-this-first.

Try using dosbox-staging instead or choosing a lower resolution for plain dosbox through the runcommand launch menu.

The triggers_to_buttons is no longer applied automatically to the xpad driver , since it breaks the Xbox controllers mappings in SDL and subsequently any applications that use the SDL's GameController subsystem. Existing installs are not affected, but new installations will not get this configuration automatically, though you can manually add it and will stay configured.

EDIT: how did you try to map the Z/C buttons - to which gamepad inputs ?