Homebrew Emulation GameYob, a gameboy emulator for DS

[ShadowOne333]

So, this was with the new build, v0.5-8. Apparently, my changes didn't help much. I still don't know why, exactly, this is happening, but I think you should try the old v0.4.1, since that worked for falconcrest, just for the sake of testing... if that works, I may revert the changes I made to autosaving since then.

Can you make the changes from v0.4.1 with the bonuses from v0.5.8 and provide a build exclusively for this beta testing?
I volunteer to test it and see if the issue still persist, and of course will let you know about anything that happens and provide feedback for that build.

 

[falconcrest]

Looks like I failed to mention it but 4.0 is the working version for me.the 4.1 build still corrupts my saves.

 

[Drenn]

Looks like I failed to mention it but 4.0 is the working version for me.the 4.1 build still corrupts my saves.

While this does narrow down the problem, I don't understand how my changes in .4.1 would cause this...

Anyway... falconcrest and ShadowOne333, here is a test build which uses the less intrusive method of autosaving. It causes some in-game lag when I use my old SD card, but my new one is just fine.

bobmcjr, I have no idea what to do about your issue. If all else fails, I would try with another microSD card...

 

[crea]

[...] 0.5-8 is superior for I/O operations in general[...]

I could not find the smaller-step release numbers, are they available somewhere? If not, I have this minor request, to add release numbers for small releases also, to not confuse the different releases/updates. Is this reasonable or are there reasons against it?

 

[Drenn]

I could not find the smaller-step release numbers, are they available somewhere? If not, I have this minor request, to add release numbers for small releases also, to not confuse the different releases/updates. Is this reasonable or are there reasons against it?

He's referring to the latest build, which you can get from the first post. You can see the version number either from your flashcard's menu, or from the "version info" option in gameyob's debug settings. The number after the dash is incremented after each git commit.

 

[ShadowOne333]

While this does narrow down the problem, I don't understand how my changes in .4.1 would cause this...

Anyway... falconcrest and ShadowOne333, here is a test build which uses the less intrusive method of autosaving. It causes some in-game lag when I use my old SD card, but my new one is just fine.

bobmcjr, I have no idea what to do about your issue. If all else fails, I would try with another microSD card...

Ok so I did the same steps I did in the previous build you uploaded.
When I opened up Pokemon Yellow again after switching roms, it loads the save file fine now.
I toggled between Autosave on and off, and the games both seem to be loading fine.
Tried with Super Mario Land 2, Pokemon Yellow, Crystal, RE Gaiden, and they appear to be loading just fine.

Let's see if this helps with the issue that bobmcjr has too.

Thank you Drenn for your help!

 

[bobmcjr]

While this does narrow down the problem, I don't understand how my changes in .4.1 would cause this...

Anyway... falconcrest and ShadowOne333, here is a test build which uses the less intrusive method of autosaving. It causes some in-game lag when I use my old SD card, but my new one is just fine.

bobmcjr, I have no idea what to do about your issue. If all else fails, I would try with another microSD card...

Incidentally I did switch between sd cards twice. This one is worse still, Warioland 3 wouldn't even load.

 

[Drenn]

Ok so I did the same steps I did in the previous build you uploaded.
When I opened up Pokemon Yellow again after switching roms, it loads the save file fine now.
I toggled between Autosave on and off, and the games both seem to be loading fine.
Tried with Super Mario Land 2, Pokemon Yellow, Crystal, RE Gaiden, and they appear to be loading just fine.

Let's see if this helps with the issue that bobmcjr has too.


Thank you Drenn for your help!

Excellent, excellent.

Incidentally I did switch between sd cards twice. This one is worse still, Warioland 3 wouldn't even load.

Most likely that's because it performs a write operation upon loading the rom, since the first write operation can take longer, in my experience.

And it's only gameyob that does this? Very weird. If you're still up for testing, I'd ask that you try gameyob v0.3 next. It does nothing unusual in terms of write operations. If it still doesn't work, then, I just don't see what could be causing it.

 

[bobmcjr]

0.3 is good. I can save and load games/settings no problem, savestates seem fine even on heavier games like Shantae. There are only two other homebrew I recall having I/O issues. Aperture Science DS level creator (consistently freezes when saving), and DSCraft (same as ASDS). jEnesisDS, NitroGrafx, NESDS, and all native dstwo plugins seem to work fine.

 

[Drenn]

0.3 is good. I can save and load games/settings no problem, savestates seem fine even on heavier games like Shantae. There are only two other homebrew I recall having I/O issues. Aperture Science DS level creator (consistently freezes when saving), and DSCraft (same as ASDS). jEnesisDS, NitroGrafx, NESDS, and all native dstwo plugins seem to work fine.

This might be a longshot but... perhaps it has something to do with the menu you're using? I know at least one DSTwo user, Nebuleon, who never mentioned these kinds of issues. If it's not your SD card that's the issue, then something must be different about the flashcard, or the software...

That said, it must have something to do with the "flushFatCache()" function which I didn't use in v0.3. I'm thinking, maybe it affects something other than the save file.

Edit: Oh, and DSCraft, that's something that uses the filesystem in an unusual way. I remember, when reading Smealum's blog, he said something about accessing each sector on the SD card individually, similar to what I was doing for autosaving... (but not in v0.4.1)

 

[Drenn]

I've just started experiencing deleted save files with v0.5... also, this:






I'm not sure why this is happening just now... but a v0.5.1 may be in order once I make sure it's fixed properly... =/

 

[bobmcjr]

I've just started experiencing deleted save files with v0.5... also, this:
I'm not sure why this is happening just now... but a v0.5.1 may be in order once I make sure it's fixed properly... =/

I always noticed decay of sorts in I/O operations (version>0.3). After a fresh install, it seems to work fine for a while and slowly starts to get weird/freeze more. The strange thing is, last time I checked the md5sum of gameyob.nds on my card was identical to a freshly downloaded copy.

 

[Searinox]

Since the file checksums don't mess up or get corrupted, it could be an issue of FAT cluster thrashing, crosslinking or such?

 

[Drenn]

Since the file checksums don't mess up or get corrupted, it could be an issue of FAT cluster thrashing, crosslinking or such?

Possibly. I was just reorganizing my flashcards' setups. Then, at exactly the same time, both of my flashcards started getting savegame corruption... It could have something to do with me moving my games outside of the "/lameboy" folder...

But then again, bobmcjr is having a fairly different kind of issue, so maybe the causes are different.

 

[Acidflare]

Drenn may I ask what NDS you are using or have I have a problem with my DS phat and need some help

 

[Drenn]

Drenn may I ask what NDS you are using or have I have a problem with my DS phat and need some help

Just say what the problem is. I test with a ds phat, dsi and 3ds.

 

[Acidflare]

I have a R4i Gold 3DS RTS from r4ids.cn I hit 3DS setup in wood after pressing start about a week ago and not realizing that the "B" button initializes the setup and pressed "B" now I have a semi-bricked DS and can't find a way to fix it, I can still boot my card play online and everything just no firmware when I turn it on without a card

 

[Drenn]

I have a R4i Gold 3DS RTS from r4ids.cn I hit 3DS setup in wood after pressing start about a week ago and not realizing that the "B" button initializes the setup and pressed "B" now I have a semi-bricked DS and can't find a way to fix it, I can still boot my card play online and everything just no firmware when I turn it on without a card

Haha, that's a terrible idea. Actually I did that myself once

Install flashme to fix your ds phat.

 

[Acidflare]

i'm actually looking at linfoxdomain right now and it's has a bunch of different versions here take a look, http://www.linfoxdomain.com/nintendo/ds/

 

[Drenn]

i'm actually looking at linfoxdomain right now and it's has a bunch of different versions here take a look, http://www.linfoxdomain.com/nintendo/ds/

Any version of flashme v8a will fix it. The site I linked to is the official one, and it describes the differences. Just use the vanilla version, unless you really want the health & safety screen...