Very nice. :) Plenty of really tight play. Maybe some brief playaround moments were missed (e.g. with the lumpy Meat Boy clones in the Rapture), but since there's so little waiting time I hardly think it matters. Go on and submit it!
It cannot be submitted for two technical reasons to do with the current version of Hourglass:
1) It has 1 frame random variance on every loading screen that causes desyncs when playing back TASes. Thus, this TAS was segmented and video edited to look single segment.
2) It cannot playback any audio from the game without problems (Hourglass doesn't correctly support XAudio2 so keylie routed it to play nothing)
e.g. if you want to see this on tasvideos, help keylie figure out what on earth to do about these :)
Is Banjo-Tooie supported?
Will there be an easy way to convert to an input file style that only has input on input frames, because IIRC n64 TASBots need to supply input only when the console polls on input frames?
Everything I am seeing is yessssss. I am hyped for awesome N64 TASes now
Spikestuff, do you know how this TAS was made? If it is on PSP, Hero30 is mostly (entirely?) deterministic so I suspect it could be done with just frame advance and good planning, no other TAS tools needed.
It says right below the code image:
"Enter the first five (5) characters of the code. Even though it has six characters, we only want the first five. This code is needed to prevent automated (robot) registrations."
It seems your friend is trying to put in all six characters, instead of only five.
Liked it, but then you're statistics at the end gave away a problem. It says you used Game Level: Easy. Unless there's no difference, you should be using the most difficult game level possible. I'll be voting no for this one (and any subsequent one that uses easy) unless you can tell me that it makes no difference.
IIRC the only thing it changes is money, and you have infinite money anyway.
Another thought: If 'TAS timing ends as you can put the controller down' implicitly removes all blank frames after the last frame of actual input for the purposes of timing, why not remove all blank frames before the first frame too?
That's an interesting thought, but that would require most runs to start from a savestate at the first frame of input, which would make them harder to verify and harder for those who want to watch the run to set it up on their emulator.
Oops, when I said 'remove' I mean 'discount for the purposes of automatically timing'.
(Alternatively, a field 'wait this many frames then begin playing back input' would be fine too.)
With how you perform it it doesn't sound like a debug feature, it sounds more like 'To get this demo to run we need to give it some initial state, let's just turn on all the powerups' or whatever. Kind of like Back in Time in 3D zeldas.
An amusing thought: What if the principle of 'TAS timing ends as soon as you can put the controller down'?
100 meter sprint: Timing ends as soon as you stop exerting with any of your muscles.
Speed chess: Timing for your turn ends as soon as your fingers are no longer in contact with the piece (flinging the piece to its intended final destination is recommended as a pro tactic for saving milliseconds off the timer)
Another thought: If 'TAS timing ends as you can put the controller down' implicitly removes all blank frames after the last frame of actual input for the purposes of timing, why not remove all blank frames before the first frame too?
Would 'beat Ganon, all glitches allowed' be an interesting category for TAS or RTA? You'd have all the power of OoB glitches, but you can't defeat Ganon without some items first.
I thought I would be prepared because I had already watched Kryssstal grind attempts with the new sub 2 minute glitched route. I was wrong. I was not ready at all.
Is this route TAS only? Yes vote
Oh thanks for bringing that up, DTK ?
So nobody can have a stable and "complete" version of RE running to read the inputs for now ?
A/V desync means that when you're playing the game it's fine, but if you make an encode of it (to upload to youtube for example) the audio and visuals will be out of sync. So you can start the TAS now and when you are done talk to someone about fixing Dolphin to be able to encode it.
Well that's pretty good. It would be good to use a different version for the other run. Would this run have been slower with leaf green?
Fire Red and Leaf Green are equally fast for any%. Not in the 'Well, they're basically the same game' sense, in the any% path there are literally no differences you care about, and IIRC cries don't take different amounts of time like they did in RBY.
So I found this:
www.youtubeslow.com
Just add "slow" after "youtube" in a youtube video's address and it takes you to a site that slows the video down (by playing it back in chunks). Needless to say, this is useful for watching WIPs.
You can also opt into the html5 player ( http://www.youtube.com/html5/ ) which has an option to change playback speed to 0.5x, 0.25x and so on.
There isn't a single best ending criteria. It comes down to TASer's choice (What is the most technically interesting ending criteria? What is the most visually interesting/aesthetically nice ending criteria?) and varies from game to game. Of course, it should not be allowed to obsolete a TAS purely by changing the ending criteria.
