VOOT frame data

[Porcupine]

My lists show the number of frames in the animation of every attack, not including the command frame. For example, a 5-frame attack starts animating on frame 1 and the projectile appears on frame 5. I reported the recovery of all safe moves as the subsequent frame on which you can input a dash (the motion won't begin until one or two frames later). A typical standing attack has a recovery of 1, but there are many abnormal moves. Those that recover at negative frames can be canceled with movement before firing, and also enable instant shots with proper timing. Moves with a recovery of 0 enable a family of attack chains requiring perfect timing. If movement is input simultaneously with the projectile, some of these fire while others do not.

The command frame is invisible but a few weapons such as Temjin CW attacks will glow during this frame. In order to make CW easier to press, LW or RW need to be held down for 3 frames to register, but the extra 2 frames can be hidden in any previous action. You can press turbo up to 11 frames before you press CW and get a turbo shot (only 10 frames before you press a direction to get a dash). You can press crouch up to 15 frames before you press CW and get a crouch shot.



















Interval refers to the number of frames between shots, either for multiple-shot attacks or manual chaining techniques. I listed almost all the unique chains I was able to find, including some obscure ones. Chains are enabled through various mechanics, some are glitches and some are intentional. A few chains are enabled by multiple mechanics in which case they may be input in multiple ways. Some chains come out at fixed speed while others reflect the timing of the input. In such cases I either give the shortest interval or the exact output window.

I didn't list the majority of generic chains that can be achieved through plain walk canceling or rotation canceling as the interval can usually be figured out from the provided animation and recovery data. I provided a few examples to help. A few VR have a slower rotation cancel than others, either because their walk decelerates too slowly or because of a glitch in their rotation, but this can be overcome by walking in certain directions, or rotating earlier in some circumstances.

Some dash attacks come out 3 frames slower at the very beginning of a moving dash. The angle of rotation increases accordingly. To remove this, just wait a bit after starting the dash to fire. Every frame you wait removes a frame from the delay. Some VRs cannot do a moving back dash, attempting one yields a stationary back dash with the startup delay worsened by an additional 4 frames. This does not apply to their back diagonal dashes.

I recommend noting the fastest attacks for each VR because they are good for canceling your landing freeze. Using my conventions, a 5-frame landing freeze is equivalent to canceling and replacing it with a 5-frame attack with a recovery of 1. That's assuming perfect timing. When attacks have both interval and recovery data, the recovery is listed relative to the earliest projectile that can be canceled into a dash.

[MentholMoose]

Wow, how are you compiling this info?

[Porcupine]

I compiled this very slowly over the last two months. The basic technique to gather frame data is simple. I press the Start button during Training Mode with perfect timing over and over, stepping through any set of actions and inputs I choose. I first accidentally realized this was humanly possible as I was compiling information for the bomb research thread. With slow motion on, the leniency for pressing Start increases to 2~3 frames depending how you look at it, making it feasible to continue almost indefinitely without screwing up.

I've already moved on to the next major project utilizing this ability. I will finish the recoveries for the unsafe moves later. It may take a long time but this is only the beginning...

[Porcupine]

I spent three weeks to finish the recovery frame data for all unsafe RT and dash attacks. Some LT attacks also have recoveries but I only marked them in red if their recovery behavior is abnormal. Standing LT attacks can cancel into a walk or dash before full recovery (being able to shoot again without moving). Crouching LT attacks can cancel into a sliding crouch or dash, starting on the same frame. They can cancel into a walk at some later frame, and attain full recovery some time after that.

I applied stricter criteria to standing regular attacks, marking any with more than a few frames of recovery in red. Stationary crouching attacks are not marked in red if they can cancel into a sliding crouch. When possible this always occurs some time before they can cancel directly into a walk or dash. Walking or sliding crouch attacks are only marked in red if they force a VR to be stationary.

RT attacks list the frame on which full recovery occurs. Dash attacks count the number of moving frames after the final projectile appears. This convention could be considered less by one frame. A jump or trigger press may be registered on the next frame, which I'll call the first frame of the freeze. Not commonly known, you can move in any direction on this one frame at walking speed. Some dash attacks allow jumping before the freeze begins, except on the final frame of the dash.


















Frame data for diagonal dash attacks is typically identical to the forward or backward version. This is true even when the diagonal attack has a different number of shots, only a different firing interval adjusts the recovery frames. If one version has only one shot while the other has multiple then the recovery frames may also adjust. There are a few side dash attacks with differing left and right dash recoveries.

The number of shots can be reduced by running out of ammo, or firing a crouch attack as a dash is about to expire. When these happen the recovery frames are unchanged so the overall attack finishes quicker. Temjin air forward dash RW, which recovers quickly, is an exception. It recovers slower with only one shot, finishing at the same time overall. Some glitchy dash attacks make an empty gauge sound after firing but that has no effect upon these frame data relationships.

Temjin surfboard and Dordray air rushes have an unlit recovery animation after running out or hitting a wall. They cannot control the subsequent drop nor cancel the landing freeze, but they can jump on the first frame after the aerial recovery animation. Cypher SLC has one frame of unlit recovery then descends with usual air movement. The landing freeze can be canceled and isn't lengthened when ending near the ground.

[Porcupine]

After carefully watching a Japanese replay video, I noticed there is a different timing when doing the jump glitch after Temjin's surfboard hits the edge of the stage.

When the surfboard expires normally there are 8 unmoving frames at the end with the surfboard still lit, followed by 16 unlit recovery frames. After that Temjin descends for 11 frames and has a 6 frame landing freeze. If hitting an obstacle Temjin instead stops for 16 frames with the surfboard still present, followed by 16 unlit recovery frames. In both cases, jumping on frame 17 begins with a 6 frame jump delay mini-freeze, instead of the usual 3.

If hitting the edge of the stage the surfboard ends immediately. There is only 1 unlit recovery frame just when Temjin reaches the wall, and no unmoving frames precede that. Regardless whether the surfboard hits the edge during startup or after missing the enemy, the "Nagoya jump" glitch should be input on the next frame, after contacting the wall. This technique is used by some Temjin players for timeout at the end of a round.

An alternative way to perform this technique is to do a plain air dash all the way until Temjin is rubbing the edge of the stage with his body. Hit CW, then press jump exactly 2 frames after that. Note that in this method there is an extra frame difference in timing due to the CW command frame. In both cases at the edge, the "Nagoya jump" technique begins with the usual 3 frame jump delay.

Dordray can also use this glitch to re-jump or grow giant in midair after his air forward dash LW or CW. In his case it doesn't matter if his air rushes hit an obstacle, the edge, or expire normally. The timing is the same and will also have the usual 3 frame jump delay.

[Porcupine]

I had neglected to post this when I added the red recovery data earlier: the VOOT timer counts down quicker than real life. It calculates using 25/50 fps PAL format instead of 30/60 fps NTSC format which is how the game actually runs. Therefore the default 80 second time limit is actually only 66.67 real seconds, no wonder it feels so short!

Frame data for long lasting things tends to be synced to real seconds: angel mode takes 2 real seconds to activate, Cypher plane mode lasts 10 real seconds, etc. Specineff death mode is instead 13 game timer seconds (actually 13.6 because the game allows him a bit more time until after the final Death message disappears off screen).

VOOM has a 90 second default time limit which likewise counts down quicker. It seems to use the same 25/50 PAL format, although for some reason the fractional seconds don't cycle the same displayed number patterns that VOOT does. Interestingly, the time limit for choosing your VR at the select screen counts down in real seconds.

Force has a 90 second default time limit which counts down quicker than real seconds, but slower than VOOM and VOOT. Instead of counting quicker by a factor of 6/5, the Force timer decreases by an extra second about every 12 real seconds.

Index has a 90 second default time limit which counts according to real seconds. Specineff VW super mode lasts 13 seconds, while for other characters it lasts 17 seconds.

[HerrCarl]

Though I don't play OT much, this frame data set is unbelievably detailed! Thanks for sharing out!

[Porcupine]

A couple years ago, HerrCarl (Vogel) and izuko (Fei-Yen) independently tested and confirmed that the VOOM timer counts down quicker than real life seconds by a 30/24 factor. So 5/4 = 1.25 times faster. This is slightly faster than VOOT. Rounds last 72 real seconds, which is still longer than VOOT.

I hypothesized that the 24 frames per second could have come from the movie film format, but who knows. I'm not sure if this is intentional or accidental due to confusion over standards. If it is accidental, the precise multipliers could be 23.976 and 29.97 fps.

Some years ago, before I went into temporary retirement, I did all the close combat frame data for Fei-Yen but never got around to other VR. It's more involved than might be expected, because close combat frames in VOOT can be extended, within limits, by your distance to the enemy. Especially if they are dashing away. You'd want to know the number of frames in each stage: from startup, to possible sliding extension, to the final stationary windup before hit frames, the active range and most typical hit frames, and finally the recovery frames.

My Xbox 360 got rrod recently after years of non-use (even though it's the Jasper model) so I'm not likely to finish, unfortunately.