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 ?

Should be fixed now.
We don't support Dolphin on RPI (the system is not powerful enough to run it) and also RasPi OS bullseye support is still in beta.

@sirhenrythe5th Yes we can certainly see that with all the annoying “no retropie for raspberry pi 4 yet” posts that happened.

@busywait said in Missing shared library libstdc++.so.6 for redream from 64-bit installer:

/opt/retropie/emulators/redream/redream.elf

That's an error in the RetroPie's package - it installs the 32bit (armhf) version of redream. Since there is no 64bit ARM version, it should probably just say that the package is unavailable. We'll fix this.

@retropieuser555 I usually test sonic adventure 2 since the slowdowns are seen right at the first level. CPU 2000/GPU 750. There are a lot of framedrops on that downhill. With vulkan those are almost eliminated.

Without vulkan, the standalone version of flycast is faster than the included retroarch version. Cmitu has a wip script if you want to try it. Loading games from ES loads to flycast's menu instead. https://github.com/cmitu/RetroPie-Setup/tree/flycast-standalone

I'm not sure what's up with redream. Overall, it's way faster than any version of flycast but the huge frame drops to the point where it can make the game freeze for a split second makes me go back to flycast.

@buzz Thanks, I'll try this, then.

Cheers!

@elvis said in Raspberry Pi OS 64bit version:

Definitely backs the choice of SDL without x11 as the preferred video output. Fairly similar upper bounds on each, despite no-video runs different by a scale of almost 3.

it's strange then the findings of @George in that thread - but maybe the retropie environment has an additional affect (again, we use a custom version of sdl)

Is there any comment on what future improvements to VC4/V3D drivers will bring to these speeds? Or are we seeing internal bandwidth limits here?

i would have thought the simple stuff like blitting to screen is about as good as it's ever going to be, but like i say, check out that thread - there may be a compounding issue for retropie. i'm currently building mame on my 64-bit x-less retropie install so will be able to test myself on some of these games. will be using ddp3 to try and recreate @George's findings.

(maybe we should continue this discussion there)

@warpath0007 Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@MrCoolSpan If you change the
gitPullOrClone "$md_build" https://github.com/rofl0r/openbor.git
to
gitPullOrClone "$md_build" https://github.com/darknior/openbor.git
and follow this guide
[Tutorial] OpenBOR - the complete guide
you get openbor to launch games directly from Emulationstation
the only problem i hade is that my ps3 controler did not work with the pre config so i needed to set it up en every game.

and remember to change every /home/pi/ to you username like / home/username/
also in every file downloadet

The RetroPie SDL fork is at https://github.com/RetroPie/SDL-mirror, for the Raspberry PI it uses the rpi-3 branch. In your case I'd try first an updated xpad driver and making sure the device is in Xinput mode. The xpad driver used by RetroPie is at github.com/paroj/xpad.

Sorry, thanks, fixed.

I installed Ubuntu 16.04.1 64-bit , installed RetroPie via script, and everything seems just fine.
this is a different laptop than last time, but I am happy as can be.

thank you very much