No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
While running moves can be done at range 0 consistently and without that much effort. You don't need to mash forward so fast your life depends on it. The only thing that matters for iWR2 at range 0 is that you press 2 exactly 1 frame after the third f press. If you press them at the same frame, you will get f2. If you have greater than 1 frame delay, you will get f2. | While running moves can be done at range 0 consistently and without that much effort. You don't need to mash forward so fast your life depends on it. The only thing that matters for iWR2 at range 0 is that you press 2 exactly 1 frame after the third f press. If you press them at the same frame, you will get f2. If you have greater than 1 frame delay, you will get f2. | ||
This is shown here: | This is shown here: https://gfycat.com/oldfashionedhotammonite | ||
Most of the time, when you are trying to do iWR2, you are doing it after another move, such as a wr2 on block. This can make things easier. The trick here is to buffer the first forward, and then on the first frame when you can act, you press f, n, [exactly one frame of f], f+2. This makes it quite a bit easier, given that you have a very large window to buffer the first f. All you need to focus on is timing of your second f with your first actionable frame, and pressing 2 exactly 1 frame after your third f. A common way this is messed up is when the second f is pressed before the first actionable frame. When this happens you get ff2. This is shown here: | Most of the time, when you are trying to do iWR2, you are doing it after another move, such as a wr2 on block. This can make things easier. The trick here is to buffer the first forward, and then on the first frame when you can act, you press f, n, [exactly one frame of f], f+2. This makes it quite a bit easier, given that you have a very large window to buffer the first f. All you need to focus on is timing of your second f with your first actionable frame, and pressing 2 exactly 1 frame after your third f. A common way this is messed up is when the second f is pressed before the first actionable frame. When this happens you get ff2. This is shown here: | ||
Revision as of 13:25, 22 January 2021
f, n, f, n, [exactly 1 frame of f], f+2. Here is what it looks like when done perfectly:
The duration of the first and second forward, as well as the duration of the neutral frames can vary in order to still perform the iWR2, however, pressing 2 exactly one frame after the third forward is mandatory.
For the purposes of this guide, I will just say iWR2, but, of course, this can be used for any moves that need to be executed from a while running state, with a few exceptions.
While running moves can be done at range 0 consistently and without that much effort. You don't need to mash forward so fast your life depends on it. The only thing that matters for iWR2 at range 0 is that you press 2 exactly 1 frame after the third f press. If you press them at the same frame, you will get f2. If you have greater than 1 frame delay, you will get f2. This is shown here: https://gfycat.com/oldfashionedhotammonite
Most of the time, when you are trying to do iWR2, you are doing it after another move, such as a wr2 on block. This can make things easier. The trick here is to buffer the first forward, and then on the first frame when you can act, you press f, n, [exactly one frame of f], f+2. This makes it quite a bit easier, given that you have a very large window to buffer the first f. All you need to focus on is timing of your second f with your first actionable frame, and pressing 2 exactly 1 frame after your third f. A common way this is messed up is when the second f is pressed before the first actionable frame. When this happens you get ff2. This is shown here:
https://gfycat.com/SarcasticHandmadeCoelacanth
In this frame-by-frame overlay, the frame colored purple, denotes the first frame I can input an action. Take note of how the first f is buffered very early.