![]() lpl files should really not depend on the working directory of RA. Ideally though, RA should convert relative paths to absolute paths before passing them to cores, because relative paths in. I changed DOSBox-core to convert the relative path that RA passes to an absolute path instead, so that it still works after the core changes the current working directory. conf files together with the game itself and be able to copy the whole directory somewhere else.) conf file is in, so that mount commands in. The -core and -SVN cores change the current working directory to directory the. What RetroArch should really do is resolve relative paths to absolute paths when passing them to the core, because only RA actually knows which directory the playlist file is in. This is only working by accident basically. (I'm on Linux.) So any relative paths in playlists were relative to /tmp. It wasn't working for me because I set /tmp as the working directory in my RetroArch shortcut. ![]() \ part is mandatory for a normal executable, but I don't know how cores get past that, they must assume RetroArch.exe run dir as the working dir, something which DOSBox-core/SVN does not seem to be doing. If standalone DOSBox were to be used as an example, the correct relative path would have been this (assuming cores as the working dir):ĭOSBox.exe -conf ".\roms\DOS\Call of Cthulhu - Shadow of the Comet\nf" The first thing this indicates is that the path has been handled to the core exactly in the same way as every other core, and the core starts the first time around but stops at the DOS prompt as if no config file argument was given. : Using content: roms\DOS\Call of Cthulhu - Shadow of the Comet\nf. Example PATH PATHZ:\ C:\UTILITIES C:\DOS Each element should be a full path (drive letter and sub directories) for clarity, and they should each be separated by a. This is what I get with DOSBox in the log file with a relative path in the playlist: The PATH is an environment variable that instructs DOSBox where to find an executable if one cannot be found in the current directory. It seems that it's the core that does not translate the relative path correctly, I don't think RetroArch has a different handling of playlist paths depending on the core. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |