Oh wow, I remember playing this game as a kid and also finding the exact same glitch... but I couldn't remember the name of the game!
Anyway, the run is a little boring but there's really no way around that. I still like it. Voting yes.
I disagree with this. Nightmare is more of a gimmicky difficulty that actually gets in the way of certain high speed strategies and would probably wind up being less entertaining to the players and more frustrating to the TASer.
Oh, really? My bad for not reading a little more closely. If those runs were submitted but not published, I don't see any reason this one should be published.
I think this should obsolete the other run that aims for in-game time. First and foremost I already think it's silly to aim for in-game time instead of real time. So having two in-game time categories seems way too arbitrary for me.
Hmm, looking at it again, it seems like there are already clock-stopping glitch runs on the site. For the sake of precedent, this video should be published. If not, the whole category should be removed (have we ever removed videos from the site? I don't think so).
Soda's time is 31.82, not 32.48.
Anyway, I'm not so sure this deserves a separate category due to the large similarity to the currently published video. I enjoyed the new strategies in this run, but I skipped the rest of the video.
I recommend ignoring wimbledonswirl, as he/she/it is just a troll from the SM64 community looking for attention. You could probably tell from the grammar and info he/she/it gave, that he/she/it has no idea what they're/it's talking about.
The singular they isn't a great crime, you know...
I think this run falls into the same vein as the Chrono Trigger or Pokemon runs - exploits a glitch to allow memory corruption in order to advance.
Anyway, voting yes.
Waiting 10000 frames for the debug menu is annoying, though fast-forwarding isn't too bad (there could be a subtitle in a published encode explaining that people should fast forward, maybe...).
I believe the currently published run has a subtitle at the scene where you have to wait under the waterfall for five minutes, so there's no reason this shouldn't.
Well 'i wanna be the guy' is a pc exe game, but i think its pretty bad that big ps1 and n64 games can be tased but a simple 2d game like i wanna be the guy or pinball for windows xp can't.
:(
You have to understand it's not just the graphics or size that is an issue here. Windows is much harder to emulate because the system requirements to do so are a lot higher than any currently-emulated console, and in addition to emulating Windows itself, you would need to emulate a wide variety of hardware and software. With the PSX or N64, they all run on the same hardware, and the instruction sets that need to be emulated are vastly simpler compared to PCs. This makes actually creating and manipulating save states that can be played back in a manner which is precise and reliable extremely difficult. Furthermore, there's really no reason to emulate a PC on a PC, so no one is going to put together all that time and effort in order to make some silly video game videos.
In fact, I think that TAS authors should be given the opportunity to reply to any objections that viewers or even judges have against their submission, before it gets rejected. There might be a reason why the TAS seems to do something badly or break some rule, and the author should be given the opportunity to explain himself (if he didn't think of doing it in the submission text).
You shouldn't think of it in those terms. Yes, the video processing power of the DS is only slightly better, but there's also two screens, one of which is touch-sensitive, and other various things which make it harder to emulate as efficiently as the N64. A Pentium 4 is definitely too slow to use a DS emulator well.
Doom has been TASed often, but there really hasn't been an updated one. It could be interesting to see if the current TAS records could be beaten by this community.
Goodness, this game's sounds are hideous and the screen runs at such an awkwardly low framerate that this is really difficult to watch. Still voting yes because it looks good and I don't presume to judge what others should find entertaining.
I forgot to mention that there was a crazy idea at yi2, but it was unfortunately a bit slower. I don't know details of this glitch, and all I can say is that too many sprites could give such a strange thing. ISM has uploaded a sample of the glitch.
weird, how could that be slower? That seems like it should save time honestly.
It is about a third of a second from the goal. It takes longer to grab the shell than that.