Because you can't, thats not buffering, buffering is putting inputs in queue when you're performing an action that can't be interrupted, this can't be done when talking about movement. Holding f while the df2 animation occurs is not buffering since if u let go before the move ends the forward movement won't happen, you're just waiting for it to happen and confirming on sight (since moving forward is a continous action and not an "event" holding it is like inputing once per frame, again, you can't buffer movement). It's cool if it helps you but this is not buffering.
@@Justlookingaround19 totally agree! it's a "time filler" as you are actually afforded some amount of time, that you can input any direction you want (e.g. forward, back, etc.) before recovering from a ch df2 to do a PEWGF. saw someone on reddit already done it way way back in 7.
ooh i remember this. its been talked about before and a tool was used to count the frames where you hold forward slightly and then hit DF+2. its a bit of an old tech that no one seems to remember. specially if your like me that likes to a lot of combos this is actually helpful. FYI i still can't do it consistently but this method somehow works
this was already a thing in previous games its not a new concept, its honestly more inconsistent than just timing the forward press though so no one talks about or uses it
I knew I wasn’t trippin, I play dvj and he has ch ws3 into perfect 14 frame electric. And I notice I would get it sometimes but I didn’t do the input I’ve known to give a 14 frame electric (➡️⬇️↘️2) Instead my command history would says ↘️2 ⬇️ (1 frame) *( 1 frame of neutral) ➡️( 6 frames) which implies that I was burrefring the forward
good tip, I personally knew about this technique but don't like it, basically you remove the neutral input doing it this way and do it more like the devil jin Ultimately ive found most important aspect is speed on the first frame of recovery and using the df,3 non float timing to train muscle memory, thank F for the last patch cause its worth doing again.
The confusion has more to do with semantics than a difference in understanding of the mechanics. To me buffering is if you press forward, let go, then after recovery the move ends a forward command comes out. This doesn't happen here, you still need to be holding forward on the frame after your recovery ends. So it's more that you don't need to time the initial press of the forward, but you still need to time the release of the forward. Which is an important detail that should help with executing the move, but imo "buffering the forward" doesn't describe this thing well enough.
That was a very Reddit comment. He did exactly what a buffer is (inputting a move that the game holds until the 1st possible executable frame) only he held it. This helps with the timing bc instead of having to wait till the exact frame your recovery ends, you can instead just let go of forward into immediate df+2
@@Rayketsu The game isn't holding anything though, if you let go of forward ON the frame your recovery finishes, there's no forward input coming out. So there's no buffer, your forward input wasn't stored anywhere. The actual buffer window for attacks is 9 frames (for sidesteps it's 16f!) so you can press and release an attack button several frames before your recovery finishes, and that input will be stored (buffered) and will be replayed the moment you come out of recovery. That's not what's happening with holding forward and releasing it on the frame you've recovered.
@@Rayketsu why are you being dense? do people really not understand what a buffer is? if you input a DP while blocking in street fighter 6, you'll get a frame one DP because it stores a SEQUENCE OF BUTTONS
I use controller and tap forward and then and then with my left hand C grip my L1 button which is mapped to do the heat engage and then hit down-forward together. Although I am less likely to use kazuya god step inputs in a match.
you need a neutral input tho between the forward and downforward. or you need to skip neutral input and do down input into downforward input which still involves letting go of the forward
I think you can hold df instead of f becayse df has a f input in it. I know you can input the first f for the ddewgf after 2 ewgfs by holding onto the df on the second ewgf. F n d df2, f n d [df]* 2 then f n d df2. The df in parenthesis is when you hold the input.
I actually do the same thing with raven and his forward dash instead in df and whatever attack I wanna do, I normally hit fdf and it makes it a lot smoother
I think going for the 3 input all together in the command history yeilds better results. If you are good at ensuring the neutral input is 1 frame, by all means go for that route.
your technically not buffering the forward as you are letting go of the button 1 frame after you are able to act giving you 1 frame of forward, definitely makes it easier but not a buffer
@@KouryuTube #52 in the movelist. You're saying you can do that after downforward 2 by holding forward? Either way, it doesn't seem to work for me atm.
@@tracephage Try holding forward after the downforward 2, but DONT hit the d, df+2. Do this a few times to get used to the frames of animation. What you are looking for is the first frame of Kaz moving forward. Once you've seen that a few time, try to start inputing the d, df+2 (EWGF) on that same frame. I hope that makes sense. You want to hold forward and try to do the EWGF at that same frame that Kaz would of moved forward.
Hold forward, and immediately as the input comes out, press the diagonal down forward at the exact same time as 2. Not one frame earlier, not one frame later.
