Crash by Scanning CEMU

[Admiral Fleischfrühling[ger]]

GameSave Manager freezes & crashes while scanning CEMU entry.

[InsaneMatt]

I'd imagine this is due to a large file count.
You can configure GameSave Manager to skip troublesome entries via the "/ignore" commandline.

[Admiral Fleischfrühling[ger]]

Originally posted by InsaneMatt:

I'd imagine this is due to a large file count.
You can configure GameSave Manager to skip troublesome entries via the "/ignore" commandline.

Oder ihr macht einfach euren Job und behebt das Problem.
Die ganzen Ordner in AppData\Roaming\Cemu\mlc01\usr\save sind nur 3,22 MB klein.
Denn ICH hab keinen Bock darauf nach der Neuinstallation meines BS nochmal neu Anzufangen weil ihr das CEMU Problem nicht hinbekommt!

[InsaneMatt]

You're confusing file size with file count.
Scanning thousands of files, each at 1 KB in size, would take far longer to achieve than scanning a single 10 MB file.

For the record, GameSave Manager is searching two potential locations...
1. "...\mlc01\usr\save\00050000" (relative to the path defined in "HKEY_CURRENT_USER\Software\Classes\discord-460807638964371468\DefaultIcon\(Default)")
2. "...\AppData\Roaming\Cemu\mlc01"

If either of these directories have a large file count (read: not size!), then that is why it's hanging.
As I previously mentioned in your other thread--which you deleted around the time you made this thread--all "work" in GSM 3x is performed within the "UI Thread". This means that any interaction with the UI / Window can and will cause hangups for the program.

There's two "fixes" available to you:
1. Opt to skip the troublesome entries (via the aforementioned "/ignore" commandline)
2. Start using the 4x Prototype available through the project's Discord server (note: this is an incomplete build, likely with bugs and doesn't receive 'Definition Updates')