Updating RetroArch to 1.10.3

[mmascher]

I run the update tool on my RetroPie deployment and I got RetroArch to 1.10.0. I see this is the latest branch available here.

Is there a way to update retroarch to 1.10.3? Maybe a develpment repo and branch I can point in rp_module_repo in retroarch.sh?

[mitu]

You can modify the retroarch.sh script and change the upstream repository from retropie/retroarch to libretro/retroarch, then modify the tag used from v1.10.0 to v1.10.3. Updating from source would get your the 1.10.3 version, but this unsupported in RetroPie.
Is there any change from v1.10.3 that you're interested in ?

[sirhenrythe5th]

One thing that would be nice: support for DC/NAOMI-chds concerning Retroachievements using lr-flycast.
As usual i wait for an official support by retropie.

[mmascher]

@mitu Thanks for the answer! I was thinking of trying that but I am a bit worried about the retropie customizations on top of the upstream version:

https://github.com/libretro/RetroArch/compare/v1.10.0...RetroPie:RetroArch:retropie-v1.10.0

It does seem something I can live without though. What do you think?

I installed 1.10.3 on all my android devices (tablet, phone and retroid pocket 2+), and the main reason to move to 1.10.3 is to share the savestates across them (if I create a savestate with swanstation on 1.10.3 then I cannot load on 1.10.0).

Edit: Well, I hope this is going to fix my issue :)

[mitu]

@mmascher said in Updating RetroArch to 1.10.3:

It does seem something I can live without though. What do you think?

The only important patch is the default save path patch, without it the saves/state paths are no longer set to the ROM folder, but somewhere in $HOME/.config/retroarch/. If you're willing to move your saves/states to the correct folders (which may depend on the core name), then you can use the upstream version. Of course, updating to the RetroPie's version of RetroArch would switch the save/state paths back, so you're going to have issues when switching.

.. the main reason to move to 1.10.3 is to share the savestates across them.

I would expect save states to not depend on RetroArch, but on the core itself, which provides the save data. Save states may not be compatible because of the architecture (or 32bit vs 64bit) and not because of RetroArch.

[mmascher]

@mitu Thanks a lot, I am specifying the save path in my retroarch.cfg, so I think it's going to be ok.

ot depend on RetroArch, but on the core itself, which provides the save data.

Aren't the cores going to be updated if I launch the update procedure using that retroarch upstream tag?

Save states may not be compatible because of the architecture (or 32bit vs 64bit) and not because of RetroArch.

Indeed, I am using the 64bits version on Android.. Bummer, getting the 64bit retropie means reinstalling everything..

[mitu]

@mmascher said in Updating RetroArch to 1.10.3:

Aren't the cores going to be updated if I launch the update procedure using that retroarch upstream tag?

No, the cores included in RetroPie have their own packages, updated independently from RetroArch. swanstation is not one of them, though, so YMMV.

[windg]

Try to avoid save states especially for Ps1, they are creating issues( graphical glitches, crashes) .