Joined: 10/12/2011
Posts: 6337
Location: The land down under.
DOES ANYONE USE EDIT ANYMORE?
Answer I have no idea
Hey look I used edit
Voting NO reasons
- Late April fools (If it was April 1st I would've voted yes)
- Heck you can make that faster not saying how because I don't want to see another one
- Stopped recording before death doesn't count
- 35 rerecords common if you're going to fake make it higher God!
- ""eggache" movie" nope when your timer stops your run stops. the death doesn't count.
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account.Something better for yourself and also others.
Actually, we have a ruling that it is ok to stop the movie at the point where continuous blank input reaches the goal.
But that doesn't mean anything when you miss the date with several weeks.
I thought this was some kind of desync, but apparently ending input and waiting for the first mob to run into him is the run.
What are the voting guidelines (and why aren't they auto linked to the poll)?
Needs to be in a "fastest end of input that results in death" category.
It is a slow and boring death and seemingly devoid of technical merit if not properly qualified.
I thought this was some kind of desync, but apparently ending input and waiting for the first mob to run into him is the run.
What are the voting guidelines (and why aren't they auto linked to the poll)?
Needs to be in a "fastest end of input that results in death" category.
It is a slow and boring death and seemingly devoid of technical merit if not properly qualified.
This submission should be rejected, but assuming it was of publishable quality, you are incorrect. TAS site rules are that we time the game until final input. Bending this rule at all completely invalidates timing on just about every single video (most games end at least 2 frames after final input, usually more).
Joined: 12/28/2007
Posts: 235
Location: Japan, Sapporo
Here is a "fastest game over" run. :3
EDIT: I forgot to vote. I see through this run no effort, no entertainment, and no surprise. It's just because of the bad goal choice. No vote, sorry.
Retired because of that deletion event.
Projects (WIP RIP): VIP3 all-exits "almost capeless yoshiless", VIP2 all-exits, TSRP2 "normal run"
"fastest death" and "fastest end of input that results in death" have the same meaning for official timing.
But for a viewer unfamiliar with the official definition some clarification would be helpful.
"fastest death" and "fastest end of input that results in death" have the same meaning for official timing.
But for a viewer unfamiliar with the official definition some clarification would be helpful.
I think part of the problem is that fastest death runs typically aren't accepted, so there's little precedent.
If they were accepted, I personally would think that the fastest time as measured from start to when the death actually occurs would be more interesting than end-of-input, because there are so many games where you'll die eventually with no input as long as you start the first level, so "fastest death" runs in many cases then become a simple menu navigation exercise.
Joined: 6/2/2009
Posts: 1182
Location: Teresópolis - Rio de Janeiro - Brazil
nanogyth wrote:
Needs to be in a "fastest end of input that results in death" category.
That at least would make some sense, to kill Mario faster you must keep pressing right untill you have the necessary speed to end the input and have the same result as if you're still pressing right.
It may be a serious submission and LYF may not be a troll, but it doesn't look like too much effort was put into his run, so I'm voting No on this one.
I am old enough to know better, but not enough to do it.
Again, this?
http://tasvideos.org/3084S.html
And you could have saved a frame, by pressing "select" at the introduction, instead of "A">"B">"A">etc.
Nevermind, SNES9x 1.43 is different.
Joined: 12/28/2007
Posts: 235
Location: Japan, Sapporo
Amaraticando wrote:
And you could have saved a frame, by pressing "select" at the introduction, instead of "A">"B">"A">etc.
I tested that, but strange frame rule prevents us from saving a frame. I now feel that most of our know-how to handle something like frame rule or lag management, is more or less useless on 1.51...
Retired because of that deletion event.
Projects (WIP RIP): VIP3 all-exits "almost capeless yoshiless", VIP2 all-exits, TSRP2 "normal run"
Re: timing
Of course timing ends at the last input, regardless of whether the game is beat at that time. However, in this case, the goal is to die as fast as possible, and ending input early to stand around and wait for something to hit him goes against that goal. He could have died faster by running into an enemy. It would still be appropriate to end input as the earliest frame that allows him to die without losing time.
Voting no for that reason.
- 35 rerecords common if you're going to fake make it higher God!
This movie that has high ratings have only 58 rerecords. Unpublished it now? LOL
Antoids wrote:
TAS site rules are that we time the game until final input. Bending this rule at all completely invalidates timing on just about every single video (most games end at least 2 frames after final input, usually more).
Thereareruns which end input way before its supposed to. :P
And you could have saved a frame, by pressing "select" at the introduction, instead of "A">"B">"A">etc.
I tested that, but strange frame rule prevents us from saving a frame. I now feel that most of our know-how to handle something like frame rule or lag management, is more or less useless on 1.51...
I tested it too now and got the same result...
But what about the fadout lag?
My first language is not English, so please excuse myself if I write something wrong. I'll do my best do write as cleary as I can, so cope with me here =)
(ﾉಥ益ಥ）ﾉ
