Hi @substring and others.
The master branch of my reicast fork should work fine on a Pi. I tested it and made sure to keep performance to an acceptable level. It adds a number of features compared to upstream reicast: shadow volumes, clipping, render to texture, multipass rendering support and a number of bug fixes.
The OIT branch (fh/deferred-shading) on the other hand is very experimental and require desktop-level cpu and gpu (and OpenGL 4.3). It also only works with NVIDIA gpu at the moment and has a couple of bugs, but I intend to improve this in the coming weeks.

@harrym said in MAJ reicast/libretro:

des jeux nds sur rpi3 cool! sinon il existe un moyen pas trop difficile de mettre a jour soi-même le core reicast sur le rpi3?
je n'ai pas trouvé d'autres topics sur ce sujet...

Tu peux essayer mon fork: https://github.com/reicast/reicast-emulator/tree/fh/mymaster
C'est une version standalone qui tourne sur Pi avec tous les bug fixes et features possibles pour cette plateforme.
Malheureusement NAOMI crash au boot.

@substring said in NEW Reicast Cores in RA:

@flyinghead Hey ! Welcome on board, glad to see you here

Thank you!

how does your reicast fork work compared to skmp's in terms of performance ? like ... does the date finally get saved ? We've also spotted a bug of improper exit of reicast with some dirty die here and there, not cleanly deinit-ing SDL2 which can cause some problems on some boards using GBM rather than FBDEV.

Performance should be similar to skmp reicast although most features I added do have a slight performance hit.
I also integrated fixes for clean exit, so that the date and VMU are properly saved on exit.

@gaetan Malheureusement, non. Les jeux Worms utilisent Windows CE, qui n'est pas supporté pour le moment.

@barbudreadmon j'ai un verify failed dans le dynarec ARM au boot. J'ai rien vu d'évident dans les logs.

@Substring cette branche est la base du core libretro non-OIT, donc elle tourne sur Pi même si quelques fonctionnalités ne sont pas disponibles sur cette plateforme.

@gaetan si tu n'es pas familier avec ce genre de procédure, je te le déconseille. Perso je connais pas recalbox et il est fort possible que des outils ne soient pas installés par défaut.
Je te conseille de laisser qqn d'autre essuyer les plâtres avant

@gaetan ce n'est pas le core libretro, c'est un fork de reicast original, qui lui tourne sur Pi.
git clone https://github.com/reicast/reicast-emulator.git reicast
cd reicast
git checkout fh/mymaster
cd shell/linux
make platform=rpi3 -j4

Salut @barbudreadmon et merci pour ton aide sur reicast!

@harrym said in MAJ reicast/libretro:

des jeux nds sur rpi3 cool! sinon il existe un moyen pas trop difficile de mettre a jour soi-même le core reicast sur le rpi3?
je n'ai pas trouvé d'autres topics sur ce sujet...

Tu peux essayer mon fork: https://github.com/reicast/reicast-emulator/tree/fh/mymaster
C'est une version standalone qui tourne sur Pi avec tous les bug fixes et features possibles pour cette plateforme.
Malheureusement NAOMI crash au boot.

@gaetan I believe the problem with Shenmie 2 is that it has self-modifying code, which breaks the recompiler. I haven’t made any change is this area unfortunately.

@substring said in NEW Reicast Cores in RA:

@flyinghead Hey ! Welcome on board, glad to see you here

Thank you!

how does your reicast fork work compared to skmp's in terms of performance ? like ... does the date finally get saved ? We've also spotted a bug of improper exit of reicast with some dirty die here and there, not cleanly deinit-ing SDL2 which can cause some problems on some boards using GBM rather than FBDEV.

Performance should be similar to skmp reicast although most features I added do have a slight performance hit.
I also integrated fixes for clean exit, so that the date and VMU are properly saved on exit.

Hi @substring and others.
The master branch of my reicast fork should work fine on a Pi. I tested it and made sure to keep performance to an acceptable level. It adds a number of features compared to upstream reicast: shadow volumes, clipping, render to texture, multipass rendering support and a number of bug fixes.
The OIT branch (fh/deferred-shading) on the other hand is very experimental and require desktop-level cpu and gpu (and OpenGL 4.3). It also only works with NVIDIA gpu at the moment and has a couple of bugs, but I intend to improve this in the coming weeks.