How so? L and R work for the menus too if you didn't know.
How so? L and R work for the menus too if you didn't know.
They don't wipe out for all games but just some of them that is related to change with spacing and character, so backup your save with named - "Game Name" updated 2, so you would able to figure and move saves from old folder to new folder that is created by JKSV.Why did updating jksv wipe out all my saves? Is there a way to get them back?
It didn't wipe them. People requested changes to the code that handles sanitizing game titles for the SD card since it doesn't support anything besides ASCII characters. It made sense to me. The old code wasn't exactly robust, I guess you could say. This came in two steps:Why did updating jksv wipe out all my saves? Is there a way to get them back?

If you really want to get technical, JKSV is how I did the learning. It's programmed very much like a game, I guess you could say. It's just doing fun stuff with what I learned.The best way to learn, enjoying what you are doing.
Do you still happen to have the latest jksv nsp?@impeeza
I don't mind, but mine was an actual nsp, not a forwarder. It also used a variation of JKSM's original title ID IIRC. I had a custom boot gif and logos too. I'll see if I can dig it up.

JKSV DO NOT HAVE A NSP VERSION. may be you are talking about Forwarders, but they are no related with JKSV, you can create yours on https://nsp-forwarder.n8.io/?advancedDo you still happen to have the latest jksv nsp?
I do not think can be done, because the savegame of a running app CAN NOT BE READ OUTSIDE THE APP.Also any c hance of getting to do an overlay menu for jksv or automatically backing up saves?
That will be a sysmodule and will require a lot of coding.Would be really convenient if you could make saves automatically on game close
https://github.com/J-D-K/JKSysVThat will be a sysmodule and will require a lot of coding.
I have same problem and ended up use different save program for just one game.Hello guys! Today I tried to backup my FireRed save and JKSV froze when I clicked on the game. This is the second time I'm trying to backup my save, it worked the first time just fine. Does anyone know why this happened?
I had to run the MTP to inject the save in Switch's NAND for Pokémon GBA game.It's because of this: https://github.com/switchbrew/libnx/issues/714
You can still move files around with file mode. Anything that attempts to render the title to screen is going to crash. JKSM menu mode, backup menu, and title information are going to crash when it tries to render the title because it's trying to render compressed data as text. I haven't looked into the specifics. I just dumped the control data from my Switch to check to confirm my suspicions.
I wasn't sure. I actually have GBA carts of Fire Red and Leaf Green I bought as broken and fixed for < $10 a piece and had no interest in paying Nintendo $20 for ROMs they downloaded off of the internet and packed into an emulator.
what other program did you use bro?I have same problem and ended up use different save program for just one game.
DBI MTP Responder.what other program did you use bro?
The not being able to show the names thing here could be the same problem, actually. It could just be feeding the same compressed data to Windows or whatever OS you're using. I wrote JKSV's font handling stuff myself. I could have sworn it had code to bail on bad characters, but until now, I never had it happen to be sure.Pokémon GBA saves are in weird folder name with just ??? or square box but you will easily notice that is Pokémon based on file name - FireRed or LeafGreen.
Is the JKSV program yours? Did you make it?The not being able to show the names thing here could be the same problem, actually. It could just be feeding the same compressed data to Windows or whatever OS you're using. I wrote JKSV's font handling stuff myself. I could have sworn it had code to bail on bad characters, but until now, I never had it happen to be sure.
Unfortunately, I overhauled the hell out of JKSV's SDL2 C++ wrapper a month or two ago. Getting JKSV 100% up and running using it won't be a trivial thing to do either. It's not structured the same way at all. It's all wrapped to be 100% RAII AKA initialize and forget about it.
There's a pull request for this in the libnx repo, but they don't seem to be in a hurry to merge it?
At this point, it's wait and see, I guess. It's not that I can't fix it. It's the time investment.