Ezio_PS, thanks for all the work you’re doing here. It’s amazing how nice it feels to have an updated emulator core on PS3. I have two things to note, one is a possible regression, one is a (hopefully very very simple) feature request.
[ol]
[li]The first is that the rewind function between RetroArch 1.0.0.2 and 1.3.6 has changed, and seems to have issues writing to the ram(?) somewhat. OpenGL related? [/li][li]The second is a request for Retroarch to check a text file at runtime for content path and core, and load that content and core. [/li][/ol]
The rewind issue I noticed while comparing between the Retroarch 1.0.0.2 core included in RetroXMB, and the current build. Activating Rewind on 1.3.6 causes massive slowdown until the granularity is taken way up. Not sure why this is the case, but this is with default 1.3.6 settings on Donkey Kong Country 2 in both cores. If this is inevitable for the time being due to other changes, then that’s that. I’m not complaining just wanted to make sure you’re aware.
The second request might need some explanation, but put simply, I’ve been talking with the developers of webman mod and other projects, and it seems there has been consistent difficulty with directly launching emulator core .self files from XMB on Playstation, and that passing arguments to them is rather difficult in the event you can. It seems to do so for a content collection would require making a “rom booter” application that sole purpose is to load itself, form the command, and then attempted to launch a specific retoroarch core, adding 18 or so seconds to boot time, and introducing a lot of dependencies for anyone using this.
If instead, retroarch had a “look here first” file in the root of the folder perhaps (bootcmd.cfg, run.cfg, etc), then it would be simple to have other apps write to that file, then launch Retroarch itself and let it handle loading the core and content as it is well equipped to do. This might be something worth a pull request into the main code as well, as it would be contextually useful on other platforms I believe.
Doing it this way would also do away with a related issues with the working directories and .cfg files on PS3. (If you load a core independently, such as from a file manager like multiman, retroarch naturally assumes the working directory of the file manager is Retroarch, and maps all the asset directories, etc, to that folder, and creates empty ones. This is normal behavior of course and not a bug, but the only solution I know for launching cores from a different working directory is to make a copy of a retroarch.cfg in the file manager’s root folder with hardcoded paths to the assets and other folders. This generally resolves things, and enables launching from multiman and other apps directly that allow configuration.)
Edit: someone filed it to github after I told him about it, haha https://github.com/libretro/RetroArch/issues/4092