nespcbuild Posted August 8, 2016 Posted August 8, 2016 Retroarch stores all save states and memory card files in the correct directories when launched outside of Hyperspin/RL. However, whenever I launch a game in Retroarch through Hyperspin or RL, the save files are always created in the same directory as the rom or image. This creates a huge problem for me because all of my roms are 7z zipped so the save files are deleted automatically when I exit the game because they're located in the same temp folder where the rom is being extracted by 7z. If I check the directory settings inside of RA when it's launched by HS or RL, the save and saves directories are both always set to <default> If I change to the correct directories within RA after launching it from RL or HS, the changes don't stick. They'll be gone after the next time I launch RA with RL. I've tried enabling config per core, saving cfgs for each core and each system but nothing seems to work. I feel like I've also tried changing every possible module setting for RA in RLUI but I've made no progress at all. I suspect that there's something in the module that retroarch sees as invalid and thus it's resetting those paths to <default> each time it's launched from RL. If you were to enter something invalid in the .,cfg file, RA will change that entry back to default once it's launched. This happens each time I launch RA through RL I'm usually pretty good at tinkering with modules in a text editor but I just can't seem to get this one to work right. I'm thinking I need to either modify the module or somehow change the default save directory for RetroArch. If I could get RA's default to be the save, srm, or saves folders inside the RA directory set as the default, it wouldn't matter that the RL module is causing the .cfg file to reset to default every time. Any ideas? Maybe someone who has this feature working can explain what they did to get it working and/or what version of RA they're using?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.