T.hawk Tutorial: buffering

t-hawk

#1

This may be something new for some of you, this may be something old. I wanted to put this up regardless for those who would like more information on T.Hawk. If you are not hardcore then you don’t really need to read through this. I am going to try to make this short.

For those who don’t know when you press a button in sf4 you are actually doing 2 button presses. The press down is one, the release is another.

With this in mind T.Hawk has the ability to buffer moves off of condor spire into other moves just by keeping the button pressed down, doing the input, then releasing it.

By using this technique of buffering, which is not an exactly a new thing but not a lot of people know, you can make condor spire actually safer to do because you have time to see how your opponent responds to you doing the move. I made a video showing this

[media=youtube]Nb7YIP–MsA[/media]

You can also use this in Jab spd situations.

You do the block string and when by holding the button down. If your opponent sits there, do the 360 motion and release the button. If they do something besides sit there, you can do something else in response to their action, making your 50.50 situations more of a guarantee rather than a guess.

Other source material for those interested, some of which applies to sf4

[media=youtube]ZBxyBXMZqbA[/media]

Sent from my iPad2 using Tapatalk


#2

I am not sure i am following here. how do those moves make condor spire safer? Buffering obviously helps with anticipating the reaction but it does not make the move safer?

That Damdai vid has me thinking of a few things i tried back in super…will see if anything has changed.


#3

I am trying to imply exactly what you just said. By input buffering you are putting yourself less at risk because it, as you said “helps with anticipating the reaction”. Rather than committing to moves right away.

I have noticed with a lot of online and offline T.Hawks is that they don’t buffer, at all. This explination is to hope that some of you true hardcore heads will look into this stuff and work on it. Input masking/buffering makes it so much easier to react to things.


#4

Its more like a kara buffer i guess?


#5

It just helps you get the move out as soon as possible after recovery; doesn’t make spire any safer. This is the same as looking at the opponent’s reaction, then going for a delayed Typhoon/reaction AA. Just a delayed 50/50.


#6

I constantly use it in my gameplay and it actually makes your reaction faster because you are not doing a motion and a button press. If you do it correct, you are just releasing a button.


#7

I think saying “spire is safer” isn’t quite right. This method doesn’t technically change anything with regards to frame data or anything. It’s just a trick to allow you to minimize the effort required to do a followup, which means there’s less chance you’ll screw up. So it’s “safer” in the sense that it’s easier to do and therefore harder to screw up (and then get punished).


#8

the technical term is called “negative edging”. I see where you’re going with this and it’s nice of you bring it up. I typically don’t do it cause i can’t stand not having my trusty jab button cocked and ready for spamming but it has its uses as you’ve shown. Keep up the good work and keep spreading the Hawk gospel.


#9

I hate negative edge. Sometimes it works, some more times it doesn’t. Then again maybe its my sloppy inputs or my stock parts.