Outstanding. The return list glitching suprised me a lot Oo The luck manipulation was stellar as usual. Amazing how such an unforgiving RNG can be manipulated so well. I know it was unintentional, but major style points for glitching Viron's name to V ron. Much cooler XD I was a proponent of a glitched run obsoleting the published movie. But that is when I thought it would be just glitching a few orbs into the inventory. This skips most of the game. As such, it deserves its own category. Encoding in process.
This is why I hardly visit this forum anymore, nor did I really get involved with it in the first place; everything becomes an arguement. Why can't people just chill out and discuss things without getting into an arguement over something they'll probably forget in a week?
Where a game has multiple difficulty levels, it is preferred to play on the hardest difficulty level (for more interesting gameplay) unless the only difference between difficulty levels is enemy/boss hit points, in which case the easiest difficulty levels are preferred in the interest of speed. If the difference in difficulty is inapplicable for your run, for example, you trigger the end game sequence right from the start, then selecting the hardest mode is unnecessary.
Well, there are 7 movies listed that uses the easiest difficulty. I wonder if any of those cases could be applied here in one way or another.
As for a UI way, we could do that for an upcoming release, the reason I didn't want that until now, is because I don't like the idea of people being able to run PAL games in NTSC mode (and more precisely I"m tired of people submitting supposed SMB records via this technique!)
To get a better idea of what kind of impact this would have, I decided to look at a number of NES games and see which access uninitialized RAM. I modified Bizhawk slightly to monitor the RAM usage. If the game read from a RAM address before it has written to it, I recorded that. I also recorded what addresses were written to. I took a list of NES games that the site has movies for, ran them for 600 frames each in that modified Bizhawk, and then outputted the data collected. I then turned the data into images to make it easier to digest the information. Here is the image set (warning: large/long images) Each 8x8 pixel block represents a RAM address, starting at 0x0000 at the top left, and ending at 0x07FF at the bottom right. The colors mean the following:Black - RAM was not read from or written to (still uninitialized) Green - RAM was written to first Red - RAM was read from before it was initialized, and still hasn't been written to (still uninitialized) Orange - RAM was read from before it was initialized, but has since been written to
Keep in mind that this data is from only 600 frames of the game, and with no input. The results may change if input is given or the analysis is run for longer. You can tell from the images that a large number of games access uninitialized memory, but I'm not sure what they are doing with it. As other people have said, some games start up in a different way depending on the initial state of the RAM. Being able to control this initial state might be beneficial to movie authors, but I'll leave that up to other users who know more about each game to determine. This data was simply to get an idea of how many games might be impacted by this new policy. Also, if anyone is interested in seeing my changes to Bizhawk or the raw data I made the pictures from I'll be happy to post it.
