You can use standalone PCSX2 to create 32MB cards and replace the 8MB ones in your RetroArch system folder with them. 32MB is spacious enough for probably 80-100 games each. You can do a 64MB card too, but PCSX2 warns it’s not as compatible with games as 32MB.
4 Likes
Thanks, this worked perfectly.
Created the new cards, formatted them, then exported the save files from the 8mb memcards and imported them to the 32mb ones, and it seems to be loading/saving no problem. Although the in game text still refers to them as “8mb cards”.
It could be all I need as there are only maybe 20-30 ps2 games I’m really interested in, but just for testing the core I launched a good number of them and created save files and that filled up the 1st card pretty fast.
2 Likes
Is that something we could pre-generate and put in the core system files bundle along with the GameIndex.yaml?
3 Likes
Probably wouldn’t be a bad idea to include blank 32MB card files in that. At least until a core option is added so the core itself can create larger memory cards.
2 Likes
Things don’t work like that, it’s not about the i5 i7 i9, it’s about the IPC they have, for example my 12gen i3 12100 destroys any 9gen i5 in performance
that’s how it is
i5 9400 Single Thread Rating…2435
i3 12100 Single Thread Rating… 3386
3 Likes
Why restrict ourselves with fixed size memory cards?
The standalone has an option to use a folder instead of a memory card. So each game simply stores it’s saves there, without any space restrictions other then the size of your own drive.
It’s also the recommended option as it doesn’t have any issues like the 64MB memory card has.
IMO, it would be better to implement that into the core as an option if we need a lot of space.
4 Likes
Could a renaming of the “memcards” directory to the current running game (before running off course) not be an option? I tried it with symlinks in Linux. Go to “retroarch/system/pcsx2/” and rename the directory from “memcards” to let’s say “memcards_doa2”. And create a new directory “memcards_othergame”. Now create a symlink from named “memcards” that points to “memcards_doa2” in example, just before starting the game Dead or Alive 2. Deleting and creating a new symlink is extremely cheap and fast operation.
This way every game gets their own directory for both Memory Cards. I don’t know if this works with all operating systems. In a case where symlinks do not work well, maybe renaming the directory would be sufficient. In that case, its a bit risky, as if the core crashes then we need extra information to what original directory name it was before. With symlinks such an issue would not arise BTW.
Hope I was clear about. Here the example how it might look (off course the directory structure needs to be organized differently, its just testing here):
memcards -> symbolic link points to memcards_doa2
memcards_doa2 -- directory for Dead or Alive 2
memcards_another_game -- directory for Another Game
But how do you tell RetroArch which link to use? Are you going to do it manually for each game through your frontend commands? If you have a ton of games this will be a lot of tedious work. If you don’t have a lot of games you don’t need that solution, a 32MB memory card is probably enough.
I was thinking this as an integrated feature of RetroArch itself. Basically just a proof of concept. So it would do this automatically just before launching the game. Preferably as an option to enable/disable this behavior.
1 Like
Yeah, that’s how the PPSSPP core does it by default too.
I think boardsofcanada didn’t like how the memory card folder code from PCSX2 does a lot of file writes (wear and tear on SSDs) and how it’s harder to implement on multiple platforms.
4 Likes
I would Like to see a new save-format with 8mb or bigger cards, one card/savefile for each game (putted in save folder not system) and then compressing the “empty Part” of the Card If possible to save some disk space.
One ‘card’ per game would probably be the best option, assuming that compatability of saves can be maintained with the standalone.
I have the feeling that Something might wrong with analog Inputs. The Joysticks seems to have a huge deadzone. The deadzone core setting is set to 0. But still, massive amount of deadzone. I use a dualsense with lakka OS and udev Input driver. Otherwise the core works great for me. I am really impressed by the Performance and compatibilty. Many Games runs at full Speed on my older i7 7700 non-k and its igpu (glcore). Games that ran near perfect: NFS Underground 1,2, gradius v, rtype final, Tekken 4+5, Soul Calibur 2+3, Tony Hawk Underground 1+2, gods of war 1+2, jak 1-3, ratchet and clank 1-3, and many more running really well with no or only minor stutter. It’s a technical marvel
2 Likes