It's a configuration used for convenience and consistency, and pretty much every other emulator will do something similar. The issue is that on actual hardware, power-on states of the RAM cells can be somewhat random. Many games will explicitly zeroize RAM addresses they intend to use, but plenty of games just take them as-is and assume they will be 0. This is why the RNG manipulation in Hagane works only some of the time, or why feasel has to wait long "cool-down" periods between attempts on FF1.
People have gotten out of the area without crashing on Snes9x and console, but not on bsnes. I haven't gotten the opportunity to try it on Bizhawk yet, which is what I'm currently progressing towards. edit1: More confirmation of it working on console under various conditions over in the SDA thread by DLDarkLink. He's hammering out attempts at the glitch from a save in Act 2 before anything in act 3 is triggered (hopefully) and at least once during a full attempt. The bad news with this is that he's reporting that waiting until the sound glitches stop, then proceeding, seems to be working. Perhaps something going on during the actual sound glitches is what causes the lock? Once the glitches stop you can hear Ebon Keep's music in the background. Now, even IF we have to wait around for a bit for the sound to calm down for it to work, I still think we've got a nice amount saved. Now to get that version of the TAS to that point, which hopefully will happen tomorrow or sometime before the weekend.
Also, I just downloaded BizHawk 1.6.0 and immediately after unzipping the files, my anti-virus software (Norton 360) deleted a bunch of them. Do these files pose a threat to my computer's safety? If not, why does my anti-virus software identify and delete them? Finally, are these files integral to BizHawk's ordinary operation?
Well either Shinespark doesn't damage him or it's just weak. I used like 3 Shinesparks on him and I didn't even see change in the colour of his belly.
current_RerecordCounter = 0;
for i = 0 to (Frames.Count - 1)
current_RerecordCounter = max(current_RerecordCounter, Frames[i].RerecordCounter);
WriteToFile(InputToString(Frames[i].InputData) + "|" + IntToString(current_RerecordCounter));Well if you can view the different branches of your input, then surely all the rerecord counts can also be viewed separately, and thus paired off with the appropriate sections? As such, it'll never say it took you 2000 rerecords for this particular frame, when actually that was just for your previous strategy at that particular point. See crude diagram: http://s29.postimg.org/nx5zwxe87/Rerecord_Count.png Naturally we would want the rerecord count to be at the appropriate section, but how exactly would you view that information? A complete graph for your run would have literally hundreds of thousands of branching pathways, each of which representing a different savestate. Most of which would only last a few additional frames, but is this really what we want to see? If we do that what would the final rerecord count, IE the total along the bottom, actually be? Basically the amount of different places you chose to create a savestate in I guess.
the rerecord data that was saved
As usual, it's greatly depends on the game. If you bruteforce 1 scene for 64721378 times and find a trick that obsoletes the previous strategy, all those rerecords for that small frame range gets "wasted", and viewer will see "lol 482194128k rerecords for going right".
edit: didn't even mentioned entertainment hex edits.
I don't know if I would enjoy watching a graph of rerecord per frame statistics when I know that there can be lost data everywhere. And then I look at the total rerecords and see 246089 and say, ok.
I can't get Microsoft Update to work
The run already abuses glitches already. Might as well go all out and do that.
There is a trick to steal and not die, even after you enter the shop post theft. Steal the item Return to the shop After the shopkeeper starts the death attack, press A+B+Start+Select at once. You should get the Continue or Save and Quit Menu. Select Save and Quit. The game clears the "kill" flag and you can still have no deaths.
/sno
