Dingoonity > News

DingooSNES 1.1 For The Native-OS

<< < (5/5)

wy_scorpio:

--- Quote from: DiegoSLTS on March 22, 2012, 05:44:38 PM ---That's not a bug, and it wasn't a bug in the GB emulator, every emulator does that. You just do or expect some really weird stuffs with save states and internal save.

Internal save is the SNES ram while the game is running, Save States are states of the emulator (RAM and processor registers and everything else they use) at the time you saved each one. They are not supposed to be used together, they come from deferent "worlds", the first is an emulation of the real behavior of the console and the second is a feature that can only be achieved with emulators.

When you open a ROM it loads the internal ram from a file, but when you open a save state it uses it's own saved ram (from that state, that may be older than your internal save), and then the internal ram is overwriten with older info. That's the proper and logical way they have to work, you should use internal ram only, or save states only, not both.

--- End quote ---

i see..
but if only can use one.."auto sram" set at on or off is the same,then "auto sram" has nothing in it
but ohboy20120224 now can use inside game's save function and dont lost it...
there..when you set auto sram on at dingoosnes..and save state use inside game's savestate then save state use slot..there will  generate two save's files...one named romname.sav0 ,another named romsname.srm..
when you load slot savestate it load romname.sav0,and when you load inside game's savestate it load romname.srm
i think the two files should not mutual interference...
if they not mutual interference...inside game's savestate will not be lost..
ohboy now resolve this problem..i think this can be do.. :)

madmatt2024:
The original download link for this is broken. Here is another.
DingooSNESv11.zip

Navigation

[0] Message Index

[*] Previous page