Updating issues with RetroPie on RPi 4 issues?

djchewmacca

@George-Spiggott Probably won't be that much of a significant difference. I was only able to overclock my GPU to 600MHz anyway. If I tried to push it further it would clock at 500MHz anyway. As long as I can still overclock the CPU i am not that bothered. I have the CPU in mine clocked at 2147MHz. Runs perfectly fine with the active cooling i have got going. :)

quicksilver

@George-Spiggott I have tested many N64 and Dreamcast games using (GPU) 500 vs 600 MHz and while monitoring the fps I could not find any significant difference. I'm not so sure that the pi 4 GPU is a bottleneck like previous pi models. Or at the very least 100 MHz doesn't make an appreciable difference.

@IceChes1 said in Updating issues with RetroPie on RPi 4 issues?:

Yes to both questions. For your first question, only on newer consoles like N64 and PS1. For your second-
There are nightly pre-made builds here

Makes no difference for pcsxrearmed, it's pretty much completely CPU driven (iirc). This is why it's worked so well since the pi 2. I'm also not convinced that it's that big of a help for N64 either.

George Spiggott

Thanks guys

I'm running a 3rd party Retropie image at the moment and I'd like to come back to something that is official ASAP The weekly builds will be just fine in that regard.

How about PSP? PSP is certainly the most graphically advanced of the higher end systems that Retropie supports? Although if Dolphin/Gamecube is any indicator of how the Pi4 handles higher end graphics it is probably worth noting that increasing the resolution on Gamecube games has little effect on the emulation speed (very slow doesn't get much slower).

IceChes1

Wait, you put dolphin on a Pi 4 with RetroPie?

quicksilver

@George-Spiggott I have tested a few PSP games and many run well on my pi4. A few others I had to turn on a little frame skipping to keep the games from slowing down. Hopefully once the new Mesa drivers are incorporated into retropie we can start getting some more optimized builds of PPSSPP, mupen64plus etc. No clue if it will make much of a difference but here's hoping.

IceChes1

PSP games run very well.

George Spiggott

@IceChes1 said in Updating issues with RetroPie on RPi 4 issues?:

Wait, you put dolphin on a Pi 4 with RetroPie?

Sadly not. I have a Gentoo 64 build with Dolphin on it. Playing Dolphin/Gamecube on a Pi4 is like playing the slowest N64 game on a Pi3.

quicksilver

@George-Spiggott said in Updating issues with RetroPie on RPi 4 issues?:

@IceChes1 said in Updating issues with RetroPie on RPi 4 issues?:

Wait, you put dolphin on a Pi 4 with RetroPie?

Sadly not. I have a Gentoo 64 build with Dolphin on it. Playing Dolphin/Gamecube on a Pi4 is like playing the slowest N64 game on a Pi3.

Thanks for being a guinea pig. Means I don't have to bother with trying it. ;)

IceChes1

I'm planning on getting it anyway. And when I do I am going to overclock.

George Spiggott

@IceChes1 My Gentoo/Dolphin setup is overclocked @ 2k on the CPU and 600 on the GPU. I rarely get over 20FPS on any games I try. If I turn frame skip up (a lot) I can make Bloodrayne and Legacy of Kain 2 run without lag but that's the best I get out of it. I'll keep the build and update it when changes happen just to see how things are progressing.

I'm pretty sure that CPU speed and or the JIT are the bottlenecks for running Dolphin/Gamecube on the Pi4. I don't see Dolphin coming to Retropie anytime soon as it needs a 64 bit OS and apart from the performance benefits for 64 bit code and maybe Play! (which will also be very slow for now) there seems to be few benefits to making Retropie fully 64 bit at the moment.

djchewmacca

I'm not sure if it's allowed therefore remove the post if it's not. I made the latest version of the weekly RetroPie build into a NOOBS compatible image. There's absolutely no ROMS or added BIOS's with it. It's simply the latest version of RetroPie (26/Jan/2020).

Dropbox link: https://www.dropbox.com/s/u8n6khpokmswli7/RetroPie_RPi4_NOOBS.zip?dl=1

mitu

@djchewmacca There's no need for this, especially since it's not an official release, but an un-tested image - if it's the same image, what's the point ?

jimmyjudd

@IceChes1 if you search the official Raspberry pi forum page (not retropie) there's a code you can run that will backdate your firmware on your pi. this will then allow you to overclock your GPU once more

IceChes1

Thank you so much.

djchewmacca

@mitu It's for those who with to dual boot their Pi with RetroPie. I have mine multibooted with multiple OSs. I'm using PINN which is a variant of NOOBs. When the official release of RetroPie is released I will be able to replace this dev build with the full version and keep my multibooted OSs as they are.

djchewmacca

@djchewmacca wish to dual boot*

George Spiggott

I've installed the latest weekly build (retropie-buster-4.5.11-rpi4.img.gz) and have discovered that my PS3 pad does not show up on bluetooth. This used to be an issue with retropie back in the summer? Is this still the same issue with the same fix? Or was it resolved and came back in the weekly builds?

Thread with the old problem.
https://retropie.org.uk/forum/topic/22312/latest-update-and-ps3-sixaxis-controller/81?_=1580935831242

mitu

@George-Spiggott I don't think it's the same problem, though the symptoms might look similar.
Try installing the latest test Raspbian Linux kernel/firmware with

sudo rpi-update

and then re-pair the controller via Bluetooth and see if there's any difference.

George Spiggott

@mitu Thanks. I've just tried that. No change. I have since removed and reinstalled sixaxis just to be sure it was't that. I still can't see the PS3 pad on bluetooth.

rejesterd

@George-Spiggott - Is the pad fully charged?

Try removing it and re-adding it from the command-line..

$ bluetoothctl remove <mac address of pad>
$ bluetoothctl connect <mac address of pad>

If that doesn't work, see if bluetoothctl can detect the pad..

$ bluetoothctl 
Agent registered
[bluetooth]# scan on
Discovery started
...

If it can discover other bluetooth devices but not the game pad, then there might be a discovery filter that's blocking it. To check it, do..

$ bluetoothctl 
Agent registered
[bluetooth]# menu scan
Menu scan:
Available commands:
-------------------
uuids [all/uuid1 uuid2 ...]                       Set/Get UUIDs filter
rssi [rssi]                                       Set/Get RSSI filter, and clears pathloss
pathloss [pathloss]                               Set/Get Pathloss filter, and clears RSSI
transport [transport]                             Set/Get transport filter
duplicate-data [on/off]                           Set/Get duplicate data filter
clear [uuids/rssi/pathloss/transport/duplicate-data] Clears discovery filter.
back                                              Return to main menu
version                                           Display version
quit                                              Quit program
exit                                              Quit program
help                                              Display help about this program
export                                            Print evironment variables
[bluetooth]# duplicate-data
DuplicateData: off

You can see mine is off, so there's no active filter. If yours is on, then try running the 'clear duplicate-data' and 'duplicate-data off' commands.