This is a TAS of the n64 classic "The Legend of Zelda - Ocarina of Time". It is the first run (that I know of) that is under 2 hours and the first run that uses the "Reverse Bottle Adventure Glitch" which is what made this time possible. Using this glitch you can instantly update something in your inventory or quest item sub-screen.
Aims for fastest time
Uses death as shortcut
Takes damage to save time
Abuses programming errors in the game
No predefined saves
Genre: Action
Genre: Adventure
This is my first submission if I left something out of these comments let me know.
Bisqwit: Congratulations on your first TAS movie. I believe you gained a lot
of experience in the making of it. However, as many audience members have pointed
out, this movie is lacking in a few aspects we keep important. Compared to the
published movie, it does not do as good job following the Guidelines,
such as "never wait for anything unless absolutely necessary", even though
it completes the game faster due to new techniques.
As you already have realized yourself, part of it is because you
did not use frame advance in the making of this movie.
As such, because this movie does not really represent well the quality we uphold
on this site, and because the votes cast on this submission are not significantly
in favor of publishing it, I am rejecting this submission.
I wish you good luck for your next TAS work, but I recommend you
gather experience from some less demanding TAS project first.
The other issue you guys need to consider is that there is a submission to SDA that is going to be around the time of guano's movie. Do you really want a movie closer in time to a run on SDA when a much much faster run is available?
Yes, if the faster run is sloppy.
Borg Collective wrote:
Negotiation is irrelevant. Self-determination is irrelevant. You will be assimilated.
Manocheese's speedrun will actually beat the current TAS's time, even if you were to count the introduction cutscene.
A lot of the time saved comes from save-warping, though.
Manocheese's speedrun will actually beat the current TAS's time, even if you were to count the introduction cutscene.
A lot of the time saved comes from save-warping, though.
How much time saved comes from the item menu not freezing the game for five minutes whenever its used?
How fleeting are all human passions compared with the massive continuity of ducks.
Manocheese's speedrun will actually beat the current TAS's time, even if you were to count the introduction cutscene.
A lot of the time saved comes from save-warping, though.
You're talking about Guanobowl's run, right? I remember the parts of a speedrun that was rejected from SDA popping up on youtube that completed OoT in 2:22 or so.
Manocheese's speedrun will actually beat the current TAS's time, even if you were to count the introduction cutscene.
A lot of the time saved comes from save-warping, though.
You're talking about Guanobowl's run, right? I remember the parts of a speedrun that was rejected from SDA popping up on youtube that completed OoT in 2:22 or so.
THe 2:22 speedrun (not sure if that was the time) was done by fluffy kitten and rejected (out of bounds glitch). Manocheese has apparently made a better one. I haven't seen it yet.
Yeah, I meant Guano's TAS. Sorry for the confusion.
upthorn wrote:
YautjaElder wrote:
Manocheese's speedrun will actually beat the current TAS's time, even if you were to count the introduction cutscene.
A lot of the time saved comes from save-warping, though.
How much time saved comes from the item menu not freezing the game for five minutes whenever its used?
About a minute or 2, perhaps.
Btw, fluffy's run was 2:33, so technically it didn't beat Guano's TAS since the intro cutscene wasn't included.
Lastly, please never use "argumentation" again. The word is argument.
Shouldn't you say something like 'btw, it's not "argumentation", the correct word is "argument"'? The way you worded that sentence makes it sound like you were offended by me using the wrong word.
The other issue you guys need to consider is that there is a submission to SDA that is going to be around the time of guano's movie. Do you really want a movie closer in time to a run on SDA when a much much faster run is available?
Shouldn't you say something like 'btw, it's not "argumentation", the correct word is "argument"'? The way you worded that sentence makes it sound like you were offended by me using the wrong word.
No, messages are made at people's own discretion, there is no style guide here. However, argumentation was the correct word anyway. On the other hand, I can't say that I've heard about "unoptimizations" before :P That sounds like something one would do deliberately.
Shouldn't you say something like 'btw, it's not "argumentation", the correct word is "argument"'? The way you worded that sentence makes it sound like you were offended by me using the wrong word.
No, messages are made at people's own discretion, there is no style guide here. However, argumentation was the correct word anyway. On the other hand, I can't say that I've heard about "unoptimizations" before :P That sounds like something one would do deliberately.
No it wasn't. Though I was wrong in my belief that argumentation was not a word (http://en.wikipedia.org/wiki/Argumentation), the correct word there was argument anyway. Argumentation refers to a system of analyzing arguments, while an argument is a series of statements that attempt to show that a certain premise leads to a certain conclusion. Thus, "the slippery slope" is an argument, not an argumentation.
No, argumentation is the act of making arguments. Argumentation theory is the study of argumentation, and in the article, argumentation is used as a short hand for argumentation theory. Wikipedia isn't meant to be used as a dictionary.
And "the slippery slope" isn't an argument, it's a form that an argument can have. Argumentation which is based upon that kind of argument is naturally called the same. Since both are potentially valid words in the context one must assume that the author intended what was written, thus making it the correct word.
Joined: 5/2/2006
Posts: 1020
Location: Boulder, CO
Look, this isn't an argument.
Yes it is.
No it isn't, it's just contradiction.
No it isn't.
Yes it is.
It is not.
It is. You just contradicted me.
No I didn't.
Ooh, you did!
No, no, no, no, no.
You did, just then.
No, nonsense!
Oh, look this is futile.
No it isn't.
I came here for a good argument.
No you didn't, you came here for an argument.
Well, an argument's not the same as contradiction.
It can be.
No it can't. An argument is a connected series of statements to establish a definite proposition.
No it isn't.
Yes it is. It isn't just contradiction.
Look, if I argue with you, I must take up a contrary position.
But it isn't just saying 'No it isn't'.
Yes it is.
No it isn't, Argument is an intellectual process ... contradiction is just the automatic gainsaying of anything the other person says.
No it isn't.
Yes it is.
Not at all.
Now look!
(pressing the bell on his desk) That's it. Good morning.
But I was just getting interested.
Sorry the five minutes is up.
That was never five minutes just now!
I'm afraid it was.
Eh, whatever, so it's just a semantic technicality. At this point, I agree with Twelvepack. We've gotten fairly off topic...
Anyways, on topic, given the poll results and the sentiments in the thread, how likely is it that this run will get published?
Whether or not the run is published, there's going to be an improvement published within a few months. So should the run be published now, and obsoleted later, or not published at all?
I am also reconsidering what I said about the run before. Perhaps it would be a good idea to publish it.
So basically there are four possible opinion on publishing this run:
1) Definitely not. It contains glaring errors and sloppy playing which amount to considerable time which could be optimized (several minutes probably?). The fact that it's faster than the currently-published run is irrelevant.
2) Definitely yes. It's not only faster than the currently-published run, but it's a lot faster (something like 40 minutes). Even if it contains mistakes it still represents the state-of-art of TASin this game because we don't have anything better and nothing better will be ready in the near future (probably many months).
3) Yes, it might not be optimal, but we could still publish it as a temporary update to this game TAS, especially since no improvement is coming in the near future. Many people are interested in seeing this and it will most probably be very popular.
4) What do you mean? This submission *is* better than the currently-published run and thus should be published. The currently-published run has mistakes too (even if they are because the author didn't know back then about all the tricks).
In short: 1) We aim for perfection, 2) we aim for fastest time, 3) we aim to entertain people, 4) this submission simply *is* better than the old one.
Second part of 2) sounds more like 4) to me.
Also the way you act all shocked that someone thinks this submission is "better" than the old one makes me think you equate "better" with "technical perfection", which I would say is a very incomplete definition.
Thanks to the avi I was able to watch the movie now. I enjoyed watching it, fast-forwarded the cut-scenes though.
A lot of the arguments in this thread are based on accuracy or optimisation. Sure, this movie is less optimized than guano's latest WIPs, but his WIPs are not the ones going to be obsoleted, right?
The published movie has a lot of unoptimized parts too, especially in the beginning (and I'm not even talking about shortcuts unknown back then). I watched it again a few days ago and altogether this submission doesn't look less optimized than the published movie. With roughly the same playing quality, more interesting glitches and way less total time, I'm giving this a clear yes vote. I enjoyed watching it and I think it should obsolete the published run.
Here... I uploaded the vid...
It shows how it goes for me...
http://rapidshare.com/files/51400830/Zelda_TAS.rm
this are btw. my Settings:
I think it could be the Input plugin... but could it be really the problem?
Or is it the internal settings of my Graphic/Sound Plugins?
btw.
The Majoras-Mask run desynchs also in the beginning...
(after that old witch tells the storys to get to the 3rd day...
He left the house... and enters the East part... then he runs back and directly in the corner... and stays there and just make shit^^")
I think it could be the Input plugin... but could it be really the problem?
Or is it the internal settings of my Graphic/Sound Plugins?
btw.
The Majoras-Mask run desynchs also in the beginning...
(after that old witch tells the storys to get to the 3rd day...
He left the house... and enters the East part... then he runs back and directly in the corner... and stays there and just make shit^^")
