Why did RetroPie for the Raspberry Pi 4 take so long to come out?
-
DISCLAIMER: The intent with this thread is not to moan or have a dig at the developers.
I am very interested in the differences between Raspberry Pi 3 and 4, and what required changing or re-working in order to make RetroPie work on the Raspberry Pi 4?
Computer: Raspberry Pi 1 Model B (Rev 2)
RetroPie Image: Official
Controller: Keyboard -
I believe the emulators all had to be recompiled and tested to see what changes needed to be made in debian 10 Buster. On the pi 3 they used Debian 9 Stretch as the OS.
-
@Retro New hardware. Go look at their github for their progress.
I've been using retropie on my pi 4 since like August. Anyone was free to do a manual install of it. Tomshardware posted a dirty guide. Most of the popular emulators were already working. It was playable and no instability issues.
Then there were automated builds around feb that eliminated the need of a manual install.
-
I believe it was because the processor was different than the others which made it a little harder to code for it which is why it took so long and also took me almost a year to buy a Pi 4 because i was waiting for RetroPie to work for the Pi 4 (even if it is in Beta i don't mind it as long as it works).
-
also raspberry pi 4 needs programs running in kms / drm mode in order to be able to do hw accelerated rendering outside of x i think it was mainly this dispmanx is not used anymore on rpi4
-
@joyrider3774 There is a lot of factors but all we can do is mainly assume the main reasons why.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.