0.4.2me sram data, and speedhacks

[astar617]

Hi, great work on the port, thanks for the ongoing effort.

My questions:

1) Is there a way to disable speedhacks by default? I find they cause most games to crash after a few minutes and often run slower. Final Fantasy II is an example of this.

2) Is it me, or does snes9x TYL only write save game SRAM data to memory stick during the program closure process? There have been a few times where I will save my game in Final Fantasy II but if I do not close the emulator properly (the battery dies, for instance, or I use the "Home" button to force quit ungracefully), all in-game saves performed since the last graceful shutdown of the emulator are lost. At the time of the saves it doesn't appear that there is any memory stick I/O activity based on the LED, so this would seem to be evidence of my observation.

Note that I'm referring to original in-game save functionality, not emulator-level state saves.

I'm running 0.4.2me on 3.90M33 w/1.50 kernel add-on. No other plugins running. Any insight is appreciated--thanks.

-A

[manias]

the save-thing is odd, haven't noticed.. but a simple solution is to use savestates! (which could introduce the sound bug thing.. lol)

[exenteth]

There's 2 ways to disable speedhacks

1 is to go in the misc options and disable it manually, for making it "by default" you can try the "make settings DEFAULT" option from the main menu

2 is to manually delete the entry for the game in the specific file snes9xTYL\DATA\snesadvance.dat
Open it with notepad, look for the line specifying you game (probably 23084FCD|Final Fantasy II) and delete the entire line - that should remove all speedhacks permanently (note that if you ever want them back, you'll have to make a backup of the file, or just get the old file from the download of snes9xTYL 0.4.2me/user)

I haven't had a chance to test #1 but #2 would definitely work

EDIT: for the sram thing, make sure autoupdate SRAM option in the save state submenu is enabled, it updates the SRAM everytime it's changed, as opposed to only on program closure