You are not logged in.
Pages: 1
Some weird happened, when I accidentally dropped my phone on the keyboard, where it happened to hit the F1 key, which sent me back to a savestate. I was an idiot, so I didn't save right before I was going to battle Volkner (The last gym leader), but the savestate only set me back about 10 minutes or so via speedup, so it was fine. The strange thing was that my Pokemon save file had gone from 513 to 1025 KB for no reason, and now, I can't use PKHex (a Pokemon save editing program) to hack moves back onto my Pokemon that I got in those 10 minutes. Any help would be appreciated asap. Thanks!
Offline
Well, that's more plausibly a desmume bug than most of the other pokemon save file desmume bugs we hear about, which are more likely user error due to inept cheating and hacking, but there's nothing you can do about it. Thanks for writing here though, it's a useful clue that somehow maybe savestating pokemon platinum can wreck the savefile. Can you tell me exactly which desmume version you're using (what URL you downloaded)?
If this all went down exactly as you describe, then you're -screwed- and will need to load an old 513KB .dsv or old savestate from backups, else you run risks from proceeding with corrupted files.
Offline
my most recent save state wont load. any way to salvage it ? i think it has something to do with me leaving the computer on and the game time exceeding 999 hours...
Offline
i dont think so. but why are you invading someone else's thead?
Offline
I downloaded the most recent version on the Desmume.org site. Here is the link. https://sourceforge.net/projects/desmum … p/download
Offline
that's not the latest desmume version, but thanks for saying which version you used.
Offline
I downloaded the most recent version on the Desmume.org site. Here is the link. https://sourceforge.net/projects/desmum … p/download
This is the latest currently: (2019/02/06 – git#4281747)
URL SNIPPED
Last edited by zeromus (2019-02-11 21:42:05)
Offline
Sorry, I'm not going to let you link to random builds on google drive when we have a buildbot making all the latest up to date builds. Link to that instead.
Offline
that link is from desmume download page directly. which uses google drive. it wasn't some random link just saying.
Anyways i could take a look at the save in a hex editor. it might have simply added extra space and i can remove the extra space to fix it
Last edited by fintogive (2019-02-13 06:01:05)
Offline
Sorry, I'm not going to let you link to random builds on google drive when we have a buildbot making all the latest up to date builds. Link to that instead.
Dude.....Why not check the link next time, it was a direct link to YOUR git build that you posted on the main download section of the DeSmuMe site genius. The time I posted it BOTH the nightly build and the autobuild sections had the same gits, so it didn't matter at the time, now you are just calling bad shots here. The other thing is you have had a lot of regression builds recently, it's a smarter idea to sit behind a bit until it's fixed, since the most recent update was six days ago, obviously I did the CORRECT thing and linked the man a proper build provided by you.
Last edited by DeadSkullzJr (2019-02-13 06:25:47)
Offline
I'm not going to check a link to a random google drive URL against the html source of the downloads page to see if it's listed there. Even if I had thought to do such a random thing. And neither will anyone else. Thanks, but next time link to the download page instead
Offline
I don't know if the guy who offered to check my file for extra space through a hex editor is still here, but it is worth a try.
https://drive.google.com/open?id=1hJMsw … fglk_-z3U_
I don't know of a way to upload files directly onto the forums, so I apologize for using google drive.
Offline
lol, the file is apparently two legit ~512KB dsv files with the 2nd one glued to the end of the first. It's possible desmume did this somehow by writing it out twice if two keys got mashed at the same time or something like that. I'll have to keep my eyes open for the same thing happening some other time. It's also possible your computer barfed.
For now using a hex editor you can delete after the |-DESMUME SAVE-| (delete everything after the2nd pipe) which is around 0x800000
Offline
That worked out perfectly. Thanks so much
Offline
Pages: 1