of course nintendos implementiation does what it's supposed to do for nintendo. store screenshots and installed data.
it doesn't have all that fancy writeing and rewriting that retroarch needs. and it certainly doesn't crash as often while saving some config or savestate and whatnot.
the problem with exfat corruption is, it happens slowly, bit by bit over time.
you might not even notice the broken files for weeks if you're lucky.
it might just hit some of the smaller gameboy games you never play anyways, or savestates you never load again.
but eventually it'll hit a cfw file or an installed title and then you'll notice.
anyways, when i got a new sd card, i finally made the jump the fat32. with splitters and all that around, there was little reason not to go to the more durable file system.
it doesn't have all that fancy writeing and rewriting that retroarch needs. and it certainly doesn't crash as often while saving some config or savestate and whatnot.
the problem with exfat corruption is, it happens slowly, bit by bit over time.
you might not even notice the broken files for weeks if you're lucky.
it might just hit some of the smaller gameboy games you never play anyways, or savestates you never load again.
but eventually it'll hit a cfw file or an installed title and then you'll notice.
anyways, when i got a new sd card, i finally made the jump the fat32. with splitters and all that around, there was little reason not to go to the more durable file system.