it does work on the DSi browser, seems to run out of memory sometimes tho

also, the memory stats at the bottom are server-side memory usage (how much memory the server took to complete the request), which is unrelated to how much memory your browser takes to render the page

____________________
Kuribo64

I don't recommend you use savestates for regular game saving.

also, if you're running in DSi mode, we don't support DSi mode savestates yet.

____________________
Kuribo64

dunno how that works. I doubt the user settings actually get lost (they're stored in the same memory as the firmware code, so that'd suck big time)

I think it's a flag in the RTC or something in the like. (as far as removing the battery to reset settings is concerned. dunno about the factory-reset part)

____________________
Kuribo64

yup, that's it -- there might be some 'time lost' bit in the status regs.

edit- yeah that's bit7 in status register 1, probably

____________________
Kuribo64

I guess you know how to make a better emulator

____________________
Kuribo64

the .ml* files aren't encrypted, they just contain all of melonDS's state

the save data might be in the NDCS section

____________________
Kuribo64

Posted by itzsplash

or is there a way i can export the .ml* to a .dst in DeSmuMe, then import it back into melon because its better?

I don't think so, savestate files contain a bunch of emulator-specific state that would be a pain to translate to another emulator


also, are we doing savestate-fixoring black magic? that's dope

(although it'd be more dope to figure out the actual issue and fix it. I should look into it someday)

____________________
Kuribo64

as Generic said -- audio generation in melonDS is synchronous to the emulation, so if it's not running fullspeed, the buffer underruns will result in shitty audio quality

the only non-shitty option to avoid that would be implement timestretching. I hope it can be done without introducing a shitton of latency.

____________________
Kuribo64

melonDS takes raw .sav files. the .dsv files can be easily converted to raw .sav (open in hex editor, chop off the end until the size is exactly a power of two).

it's important to ensure the file has the exact good size, melonDS relies on the file size to identify the savemem type.

____________________
Kuribo64

also, make sure MAC randomization is disabled. savefiles might not work because they might be tied to the console's MAC address (which may be different between melonDS and DeSmuME).

____________________
Kuribo64

normally clicking the Browse buttons would bring up a file picker thing. I don't quite see why that wouldn't work...

____________________
Kuribo64

can you give more precisions about this?

____________________
Kuribo64

can you post a screenshot of your cheats dialog?

____________________
Kuribo64

the problem with that is that it prolly works in Dolphin because Dolphin intercepts API calls that reference NAND files themselves

whereas on the other hand, with melonDS, we need to emulate the NAND hardware itself, and basically deal with raw NAND sectors

using an extracted NAND would require somehow building a FAT structure on the fly and somehow retrofitting the changes to the files themselves

I hope I make sense? I'm high don't mind me

____________________
Kuribo64

i want to do some NAND explorer thing eventually yea

____________________
Kuribo64

whenever I get the motivation, yeah

____________________
Kuribo64

not yet, it only feeds a placeholder picture thing

____________________
Kuribo64