@superomegabeto , where you able to make it work with a newer version?
It does not work with 4.7.1.

I solved it..

done in raspi-config

Issue 1 can be easily solved by using the Audio menu in RetroPie and choosing your default output (Analog Jack/HDMI).

For #2 - The Headphone value can also be chosen in the EmulationStation settings, since it has been updated in June 2020 following the RPI OS changes.

@ginkage bullseye isn't supported yet.

You can use our weekly buster based image for the zero 2. Use the rpi2/3 image. https://files.retropie.org.uk/images/weekly/

@flagrant99
Just delete the file
\hostname\configs\all\videomodes.cfg

@redbatman based off my experience, the pi 4 is borderline just a tad too slow for n64. No game runs at 100% speed at all times. Your tolerance for minor slow downs will make or break your experience. But it’s Not that the cpu is too slow, just the way n64 emulation works, the bandwidth of the pi is just not there.

@jigidyjim if you have a USB card-reader, you could boot one and mount the other and diff them on the pi.

Otherwise, you could copy the "configs" folder off the two cards over the network share and then diff them on your PC using Ubuntu for Windows.

In the PC's search bar (on same network as the Pi), type:

\\retropie

(Use back-slashes.) This brings you to the network share on the Pi. Copy the "configs" folder to your PC. Repeat with "configs" on the other SD card.

Install Ubuntu for Windows through the Microsoft store. Right-click where your two "configs" folders are. Choose "Open Linux terminal window here." diff the two folders.

@protocultor This fixes the problem, thanks!

Sorry for the late reply BTW. I decided to gather up all my Pi stuff and take a couple weeks break from touching any of it!

@mitu I suppose this function stretch_fix_raspbiantools (in ~/RetroPie-Setup/scriptmodules/supplementary/raspbiantools.sh) won't have done anything since I'm not on stretch & never have been (Pi 4), is that right? And besides that, looks like it's, as you said, just an update && dist-upgrade, which is what already I did a week ago. No harm no foul then, eh?

The only remap I saw was for saves. Here is my runcommand.log file:
https://pastebin.com/7v67SJe0

the last line of the file (shown below) repeats well over a thousand times but I cut almost all of them out of the log file i put on pastebin for sanity's sake.
[libretro INFO] [MAME 2010] 'maincpu' (FFA649F0)[libretro INFO] [MAME 2010] (no context): unmapped program memory word write to 01D01070 = 0000 & FFFF

Thanks!

@busywait said in thebezelproject script doesn’t work:

@pscotto1234 I don't know, I used 'rm' from the command line, and ended up just downloading the few bezels I wanted "by hand" from the bezel project github and other places mentioned in this forum.

However, this got very tedious, so if you don't need the GB of space, just leave it there? The problem for me was that my card got totally filled and things like updates started to fail in way that I didn't notice :(

I think to do this:

from terminal ls > system_name.txt in each system folder to obtain a file containing roms name; rename the listed file extension in .png ; from terminal ls > system_image.txt in each bezel folder to obtain image list; compare files for the same system to mantain only image name for roms not present in my collection; with command cat system_name.txt | xargs rm I can remove not useful image;

I hope you understand my method :)

@nunna78 hi there. I must complète this Thread:

XpadNeo: Xbox-One Controller does not fully works on SteamLink. X and R1 Button are not recognized

Xboxdrv: Xbox-One Controller work perfectly on SteamLink.

So if you want to play SteamLink i'll recommand Xboxdrv instead of Xpadneo

@mitu and to any future readers - I fixed it!

After much searching, I found this link https://github.com/goodtft/LCD-show/issues/278 for an issue with an LCD display I tried to use years ago. Apparently, it updated my /boot/cmdline.txt file to put ttyAMA0 in my console, instead of the default serial0. Swapping it back to console=serial0,115200 and rebooting, and now bluetooth works again!

ended up flashing the pi3 version and setting up ssh and it seems to work well now.

thank you everyone for the help!

@protocultor said in Problem with gamepad in ports (Duke\doom\quake):

Enter in "Options" -> "Go to console", and in this console type:

Ооооооооо, great, thanks!

Well, with doom all fine, now need to find out how enable pad in lr-tyrquake
And have dealings with the right stick in quake 2\3 and duke

Maybe for those games need some same console command like in doom?
( i still not understood how work config in quake 2 - I'm change those values and the game apply it, but after quit from game - config stay the same original. And in game right stick only not work left direction, other up\down\right work well, and in option menu function "turn right" bind as trig_left, so maybe in console i need to write something about left-direction as trigger_right?? In options menu it's unable to bind to x axis left)

@levelkro
Hi, I am having same issue. I was unable to get LCD from gamepi20 running at all, not even with different distro.
If you got anything out from waveshare, would you mind to share it across?
Thanks.

fbi works! Thanks.

Using python evdev lib to read joystick button input

pip3 install evdev

The following python allows my to display any pic and wait for Joystick button press.

In this case I wanted to be able to display my Emulation Station Control and Attract Mode Button mappings on demand.

import subprocess import time import evdev devices = [evdev.InputDevice(path) for path in evdev.list_devices()] for device in devices: if device.name.startswith('DragonRise Inc.'): device_path=device.path dragonrise = evdev.InputDevice(device_path) print(dragonrise) subprocess.Popen(["fbi","-a","/home/pi/py/MyCtrls.jpg"]) for event in dragonrise.read_loop(): if event.type == evdev.ecodes.EV_KEY: keyevent = evdev.categorize(event) if keyevent.keystate == evdev.KeyEvent.key_down: print(evdev.categorize(event)) break