It has no "error correction" for e).Īpart from the envisioned interoperability with the libretro counterpart the suggested change uses: a), c1), d), and e). But misses d) which will cause an error when a bladerunnner-final-win.svm file is found but has no peer section in the ini. The upstream implementation uses a), c3) and e). svm files to force automatic -add on launch.Į) The user MAY edit the section names in the scummvm.ini, but SHOULD keep the corresponding. svm file is irrelevant, the filename represents the target (=expected in scummvm.ini)ĭ) The user MAY create empty. svm files and uses as content c1) the game id (as in the ScummVM compability matrix, example bladerunner) or c2) the target as provided by Add Game or -add (example: bladerunnner-final-win) or c3) the content of the. ![]() ![]() svm filesĬ) The user MAY edit new/exisiting. for the games.ī) The user MAY NOT manually edit any generated. Maybe it is advisable to move a step back and align about what a user must/should/could and may not do when deploying ScummVM games?Ī) The user MUST run Add Game or Mass Add. Which IMHO creates a clutter in the roms/scummvm folder and would the libretro implementation to consult the non-libretro scummvm.ini. This requires currently (upstream main branch) to run Add Game in the UI. Which requires a matching in the scummvm.ini to identify the game path. Once a svm file is found, scummvm should just be launching the game I am not done with the libretro part, just removed/rewritten a python-less version. It still contains development output and verbose comments. I have redone the +Start Scummvm.sh script, sharing it here for discussion. scummvm file in the game's folder for the Libretro core and have it launch from there. don't do symlinks in the roms folders, it's not going to work on (Ex)Fat32 drivers when an external media is used.svm files should only be created after the launch is complete, not before. Maybe sha256sum should be replaced with something simpler ( md5sum would be enough, crc32 would be even easier - but it's not a native program). comparing the pre/post game lists - the comparison should be triggered only if the.If the folder path is not found (based on the. once a svm file is found, scummvm should just be launching the game and no extra checks should be done (i.e.I do however find the implementation could be simplified (leaving aside the python helper, which I haven't looked over since I see it as optional). svm file - I think we already had this conversation. I agree with the changes needed to be implemented in order to accommodate the standalone/Libretro core launchers supporting a single. ![]() , see libretrocores/lr-scummvm.sh, emulators/scummvm.sh and supplementary/scummvm/scummvm_helper.py The python part is more ease-of-use and enabling config changes for games to be stored in each scummvm.ini file.Ĭan we craft a solution for this long standing issue? With this structure the game folder can be determined by the romdir-launcher.sh which is sufficient to run the autodetect from libretro for that game. ├── Touche - The Adventures of the Fifth Musketeer.svm ├── Touche - The Adventures of the Fifth Musketeer My approach followed in the branch is to have this folder structure: RetroPie/roms/scummvm/ The identified game folder can then be provided to libretro ScummVM and the auto target is run in that game folder by the libretro implementation. If the Python part is too much, then at least the filestructure should be in a way that from a game launcher file *.svm the matching game folder can be identified. I have updated my branch with a proposed solution to fit into the latest RetroPie-Setup. With a little structure in the filesystem scummvm and lr-scummvm could be used seamlessly alongside. Using ScummVM and libretro ScummVM side by side and run games either in ScummVM or libretro ScummVM does still not fit well yet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |