![]() ![]() So I suggest adding a small check when OPL scans and mounts the file systems at startup to check the temporary VMC and the folder saves that would result to make sure they aren't in a partial flush or unflushed state. There would be a chance with this style of handling things for a user to turn off the console while the VMC is being flushed and leave their save in an undefined state. The VMC systems that run in-game would need a little modification so that whenever the VMC is saved to it could flush that data back to the folder to update the main saves. Instead of storing the temporary VMC within memory (which I understand can get pretty tight), a temporary VMC can be auto-generated before launching the game using the same methods PCSX2 does but saving the VMC within the folder and utilizing the current VMC systems in game. (Warning I haven't fully grasped the VMC system as it currently stands) I think OPL should be able to handle this method with some modifications. I believe there are some automatically generated sets out there that can be found but the ones I've seen had automatic names that didn't correlate to the games that used them, and I was unable to confirm if games that needed to share cards were properly set up to. A user could use PCSX2 to convert a standard VMC into a folder VMC for use with it (slow, usb drive or hdd method) or they could create a script that would detect updates to a standard VMC file and extract the save data.Įither way, these solutions are only half measures and the save data would need to be reconverted back to a standard VMC after using it in PCSX2 or any other editing the user would like to perform.Īlso neither method removes the problem of managing large numbers of VMCs (and could even add to it) since you would still need a VMC for each game and each set of games that need to share a card. The only alternative I've been able to think of would only work halfway. ![]() It also provides direct access to the save data for editing, modding or sharing. This effectively creates one memory card that is as large as the drive you are saving to without causing issues with memory card size. When loading a game it will dynamically recreate a VMC by loading in the relevant game folders (probably using a lookup table for games that need to share memory cards). ![]() If I understand correctly, it creates a VMC that, after being written to by a game, will take the save data out of the virtual FAT filesystem and put it in the save folder. I would like for a Folder Save format for VMC that is compatible with PCSX2. This adds another layer to the complexity of a large library and managing the large number of VMCs that could be created. In the case of virtual memory cards, you could create individual cards for each game to prevent running out of space on one for saves but that breaks games that look for other games for content (such as Ratchet and Clank series games looking for saves from previous games in the series). Managing memory cards, virtual or otherwise, becomes tedious as a game library increases in size. Is your feature request related to a problem? Please describe. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |