cloudropis

I've fixed the issue. I started doing tests my moving my saves around, swapping the local one that works with the ones i upload here that don't etc etc Well, turns out the solution I use as fast and dirty cloud storage, and that I've been using to move saves now, is very funny and quirky and basically, every time I uploaded my BB save, it didn't actually upload it again - since it sucks at properly hashing the files, it just saw that I've been repeatedly uploading a save file of the same name, so it kept forwarding the chronologically oldest file of the same name without telling me. In other words, I uploaded "BB.dsv" on that cloud on May 5th, then "BB.dsv" on May 7th, then "BB.dsv" on May 12th, and instead of uploading the proper file every time, it kept feeding me back "BB.dsv" from May 5th implicitly telling me "yo bro don't worry you already uploaded this file, it's safe, see I'll send it to you again to make you know that you don't need to upload it again, see it's here already". And that's the one I kept using on PKHeX and that I sent here, it's the very first Blaze Black save I've ever upped there. So yeah, my bad, when making sure I'm actually uploading the file (by changing name/size or whatever it uses to hash, or by using switching to real cloud storage instead of Telegram chats) PKHeX works great.

So wait, which one is it? Is the emulator failing to write on both blocks properly on the right save file, or is this just a wrong save file? I double checked every possible save location for another copy that might be the one that actually gets updated on save, but there's none. So the .dsv is the correct one. It's the way the data is written on it that is borked then?

Damn, I imagined it was something like that becuase I knew the Pokemon games had a .bak slot to revert to in case of save corruption. How did you see this info on blocks? Through PKHeX? Do you know if it's the main block or the backup block that works? Any idea on how to force drastic to save on the correct block?

There you go. Blaze Black 3.1 save file. If the save file loads correctly, you'll see me at Striaton's PKMN Center with 2 and something hours of playtime. If you see an 8 minutes playtime just outside the player's house with just Snivy in the party, that's the incorrect load that Desmume and PKHeX are giving me Pokemon Blaze Black V3.1 Full.dsv

I loaded my Drastic save on Desmume and Desmume also sees it as an 8 minutes in save, same as PKHeX. Weird as hell, looks like only Drastic sees it properly at my current progress instead of this old snapshot. Any tips?

This is on desmume right? I'm on Drastic. I'll setup desmume and try through that method tomorrow

This doesn't seem to have worked. I saved twice in-game. I didn't get the "saving a lot of data" message, I actually never got it in my two hours of playtime, I still saved a third time just in case. I soft reset, and closed the emulator without loading the save or anything. Moved the dsv back to pkhax again and it's still the same incorrect 8-minutes-in snapshot

I'm playing Blaze Black 1 on Drastic and I decided to use PKHex to edit the mons I capture. What I did: - Made an in-game save (I barely use savestates, so i save incredibly often with real saves as much as I would on a real console - Moves the .dsv file on my PC - Opened PKHeX on illegal mode (so PKHaX) - Loaded my save from the menu on the top left Instead of seeing my pokemon at their current level, I get a snapshot of very early in the game, 8 minutes of playtime, just my starter at level 7. I have no idea why. I reopened the game (it loaded my current progress just fine) on Drastic, made a new save, made sure the Battery folder didn't have older copies of my saves, moved the new save to my PC again - nothing, PKHaX still loads this very old version through the same save that loads normally on the emulator itself. I dunno if it's decisive, but I made a test save before my current playthrough. Meaning, I had to return to the main menu and press Select + Up + B to go through the save deletion procedure in order to be able to save for my actual playthrough. I'm still pretty sure this weird old snapshot isn't that old deleted save, it's indeed from my current playthrough.