Snes9x.com

there's no difference in battery saves; if they're not working, your save path is probably defined wrong. save states aren't guaranteed to be compatible across versions; however, i haven't seen anything to suggest the 32-bit and 64-bit builds generate different output. if they're the same version nu...

all you have to do is rename the srm to match, nothing more. if that's not working, either:

• you typoed something, or
• the srm you renamed isn't actually the one you've been using (can happen if the path isn't defined) - do a full search for *.srm and see if it's actually in a different location.

what version of snes9x are you referring to?

the developer of the Android and iOS versions no longer frequents these forums; you're better off contacting him directly.

they're either *not* in the right directory (check the Saves tab under Emulation -> Settings) or the filenames don't match.

don't try to open them directly. rename them to match your ROM, leaving the extension intact (e.g. if you have gamename.smc, the saves should be named gamename.001, gamename.srm, etc). place the files in the save directory you have defined. *.srm files are the battery save files (i.e. the game's bui...

what are the path to snes9x, the save path, and what is defined as the save path in snes9x?

make sure the filename matches the rom image (i.e. for mario.smc, the save should be mario.srm), and place the file in the location defined in the "SRAM" page of Emulation -> Settings...

unfortunately, you're far more likely to get a helpful response from the developer than here.

for the record, Snes9xEX+ current version (1.5.28) works for me on a Moto X (2014) running 6.0, so i can't reproduce your problem.

enter each line as a separate code (which is what they are - they just happen to have the effect you're looking for when applied simultaneously).

this was fixed in the 2012-09-12 testbuild; you can use any newer version from here.

if a code isn't working for you, then either 1) it's not entered properly or 2) it's not valid for the exact ROM you're using. Game Genie codes patch specific values in ROM; different revisions of a game release may have values shifted around and therefore require different sets of codes. also, you ...

first, this is the wrong place to ask. rakashazi handles the iOS and Android ports, and he doesn't frequent this board anymore. second, not to be a wet blanket, but trying to do offsets on the individual graphics layers would fail miserably on many (if not most) games. for the games that DID have th...

you have to enter each code separately.

fyi - if you lost your saves, it's because you deleted them. they're not integral to snes9x itself.

that being said, you can always just try deleting snes9x.conf if something gets hopelessly broken.

search for "MarioPatch.*" and rename all resulting files "KaizoMario.*" (without modifying their extension).

you've disabled some of the graphics layers via the 1-5 keys; pressing one of them will toggle the corresponding layer and show an onscreen message as to whether you toggled it on or off.

the SNES Mouse is an alternate controller, used in Mario Paint and a handful of other games - it doesn't do what you're trying to do.

you'll need to use a decompression utility like ZArchiver to extract the ROM files from the archives you downloaded.

taufan99 wrote:

odditude wrote:you can use the patch available here. keep in mind, if you're not using the 10-09-2012 testbuild or newer, the issue will continue to recur.

Using the v1.53 build here. What should I do?

...use the latest testbuild?