@buzz

My was setup:

Raspberry pi 4 model B Rev1.2 (Stock Clocks) Raspberry Pi4 Argonone Case Retropie 4.6.8 43' 1080p TV 8bitdo controller Using 5ghz Wifi

Only occurs on stuff like SNES, NES, and similar 2D platforms, but as i mentioned before using a custom aspect ratio with 1 less pixel on Y & X axis than core config seemed to fix it. Bilinear Filtering, and Interger-scale also fix the tearing aswell not sure if there are other fixes though. V sync is on any everything.

Added pause overlays for Neo Turf Masters. and Windjammers

snapshot.png

@yoc1983 said in Retroarch audio problem (digital/I2S):

Built From: Pre made Image, Wolfanoz Raspberry Pi 4 Supreme Pro

We don't support 3rd party images - use the image from retropie.org.uk/download if you want support here.

@BuZz Thanks for looking into it. I saw that you have implemented a temporary fix until it's fixed upstream. I will test this and see how it works.

@bascoumans said in Having problems configuring ipac2 with retropie:

in keyboard mode and followed the extended guide on this forum. In this mode ES wont recognise it as a gamepad so I cant configure it in the menu.

That is strange! Because, even if ES configure Input Menu is telling you it hasn't detected a gamepad, pressing a "keyboard" key should get you through the configuration of the controls for player 1 (same as with only a real keyboard connected)! Have you tried pressing a button (mapped as keyboard key), or does the message that no gamepad was found had mislead you to assume that a keyboard cannot be configured via the UI? Going through that should give you a valid retroarch.cfg (as said for player 1), to add player 2 controls you still have to edit the file.

It might be helpful to provide some details about what you're trying to do - which emulator/system, how are you trying to add palettes, etc.

@dankcushions Thanks, I'll head over there.

@etheling said in Update retroarch.sh to enable KMS/DRM on x11 platform?:

Other than patching files under RetroPie-Setup, is there some way to achieve this that I didn't realize?

No, you need to patch the scriptmodule to have both vulkan and KMS support.

@saccublenda said in Netplay help:

@UberLumby You can follow the instructions here.

Thank you
"Create a symbolic link to the RetroArch core you want to use for netplay in the directory where the core info file was stored, for example
ln -s /opt/retropie/libretrocores/lr-fceumm/fceumm_libretro.so $HOME/.config/retroarch/cores"
This confused me a bit but I think I understand this creates a link to the existing .So I was copying and pasting them into the retroarch cores folder last night lol ops...

@UberLumby I have the same problem on Retropie 4.7. Did you ever resolve this?

@Shenmue-is-life what do you mean the 'appdata' folder? isn't that a windows thing? retropie runs on linux - the save folder is typically the rom folder. please fill out https://retropie.org.uk/forum/topic/3/read-this-first

Just wanted to say Thanks for this question and answer. I had been struggling to get my 8bitdo Ultimate Wireless controller working in the games also and it turned out to be the same issue.
Adding /opt/retropie/configs/all/retroarch-joypads/8BitDo_Ultimate_wireless_Controller.cfg from https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/udev/8BitDo_SN30_Pro%2B_BT_B.cfg worked.

As a total RetroPie/EmulationStation/RetroArch newbie, how is anyone supposed to know that they needed to manually add these controller configs? Is it supposed to be an automated system that's just not working correctly because I never saw any documentation anywhere that pointed users to the libretro GitHub.

I'm not sure the download location has changed, I don't see the doc page reference a precise location for each system. The cheats are downloaded from the Libretro buildbot AFAIK, not directly via git, the archive is generated from https://github.com/libretro/libretro-database. Both have been restored after the hack incident a while ago, so it shouldn't be an issue.

The only thing that would have a say in this are the kernel/firmware updates. What kind of Wi-Fi setup do you have (2.5ghz, 5ghz) ?

As a diagnostic, run dmesg | sudo tee /boot/dmesg.txt and post the dmesg.txt - you can read it from the PC if you put the sdcard in.

@mitu ugh... got it. I see what you mean now.. "save core preset". That worked.

Thanks... and I also jumped on the bandwagon for the safe-shutdown script while I was at it. Works great as well... no more text when I shut down.

you're top dog for sure!

It has worked!

In a bit more detail:

I didn't add entries for P3 and P4 on retroarch.cfg because, what would I set them to if I only have two controllers? 4 and 5, assuming that I could be plugging in additional ones?

Anyway, I tried to re-add the two physical Logitech controllers to EmulationStation; it detect 4 controllers, but it would keep detecting the button presses as coming from the emulated Xbox controllers.

I then reset the controller settings for EmulationStation on the Retropie menu and again, it would detect 4 controllers, but it also would keep detecting the button presses as coming from the emulated Xbox controllers.

I had to disable xboxdrv and then it would only detect 2 controllers and the button presses a coming from the physical Logitech controllers. The conclusion here is for EmulationStation the physical and emulated controllers don't clash; the emulated ones take priority and the button presses are understood to be coming from them.

I then checked that on the Retroarch menu the emulated controllers were assigned to P1 and P2 and removed the physical controllers that were assigned to P3 and P4. And then everything was fine. The crux here appears to be that I had a clash, as both the emulated and physical controllers were assigned to players and probably registering button presses. Something that support this hypothesis is that on games where you have a grid to select your character (e.g. Mario Kart) it was fairly obvious that when I was pressing once to move one cell to the right, for instance, the selection box was moving two cells.

Thanks again for all your time helping me figure this out.

@BrtsZ said in Retroarch Quick Menu Inconsistency Between Emulators:

I'm using a rPi 4b with retropie version 4.6.7 on an old CRT TV. Because certain menus can be challenging/impossible to read in Retroarch with the default theme (XMB I think?), I've changed the theme style to RGUI, as it's large, clear, and legible with my limited resolution.

RGUI is the default in retropie. did you delete any .cfg files? please fill out https://retropie.org.uk/forum/topic/3/read-this-first?

but then in the following emulators it appears as the default that I can't read (XMB I think?):
-SNES (lr-snes9x)
-NES (lr-fceumm)

again, suspect you've deleted or messed with .cfg files. please provide a verbose log for these, as per my above link.

@mitu said in Trouble with RetroPie after updating from Stretch to Buster:

@keks24 said in Trouble with RetroPie after updating from Stretch to Buster:

Could you elaborate this and provide some references, please?

I think every new Raspberry Pi OS (was Raspbian once) mentions this in their release notes. For instance, for the Buster release:

We do not recommend upgrading an existing Stretch (or earlier) system to Buster – we can’t know what changes everyone has made to their system, and so have no idea what may break when you move to Buster. However, we have tested the following procedure for upgrading, and it works on a clean version of the last Stretch image we released. That does not guarantee it will work on your system, and we cannot provide support (or be held responsible) for any problems that arise if you try it.

Ah, thank you for the link!

In my opinion, they are making it a little bit easy on themselves here, but I guess, that they do not want to let the (normal) user go through the entire partitioning resizing process of /boot/ here.

They also increased the partition of their official images, due to the large kernel files of Debian Buster:

$ fdisk --list * | grep "Device\|img1" | column -t Device Boot Start End Sectors Size Id Type 2020-12-02-raspios-buster-armhf-full.img1 8192 532479 524288 256M c W95 FAT32 (LBA) Device Boot Start End Sectors Size Id Type 2020-12-02-raspios-buster-armhf.img1 8192 532479 524288 256M c W95 FAT32 (LBA) Device Boot Start End Sectors Size Id Type 2020-12-02-raspios-buster-armhf-lite.img1 8192 532479 524288 256M c W95 FAT32 (LBA) (retropie) $ df --human-readable /boot Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p1 512M 47M 466M 10% /boot

Yes, that's correct.