@Krackatoa What is your gamplay setup? Are you using dedicated ps4 controllers/sticks and lagless monitors. Much of what you are saying about the cancel window and run cancel window being small makes much more sense to me if you are experiencing lag. I did a little experiment this weekend at a local tournament, where my opponent was using a ps3 stick and I was using a ps4 stick. We were playing on the Evo monitors. I went into practice mode and selected the same character as my opponent. At point blank range I hit the same attack (standing 1) on both sticks simultaneously. In theory, the attacks should trade, but thats not what happened. The ps4 stick beat out the ps3 stick every time. This is because the Lab zero driver is processing the ps3 signal to be read by the ps4 and is introducing a small amount of input lag in the process. Input lag will make cancel windows seem smaller than they actually are, and can make you think that you can buffer dash cancels in places where you cant. If you are not playing on a laggy setup, then maybe we just have different execution / reaction times.
I play on Hitbox, and on PC normally. Input lag has little to do with anything, because we're talking about 1 to 2 frames. Human reaction time for identification (Is this a low or an overhead coming?) is 17 to 22 frames when paying absolute attention. You also have twitch reaction which clocks in at 12 to 15. This is shit that I've measured via dozens of players, and from my own experience playing many other games.
You can probably get your reactions to Wasp Grenade down closer to your peak twitch reaction time, but that's still not enough time to confirm off Wasp Grenade coming out. You cannot use the same timing to cleanly combo off b1 AND run cancel it on block, and you cannot react to which is happening. You have to guess that your b1 is going to connect.
With f22 and f11, the window is far larger, and you CAN do the same timing and still connect a 212 without paying attention to which run cancel window you're hitting. The thing is, this window is VERY small. You're aiming to hit the very end of the comboable RC window for on-hit.
D'vorah can confirm off f22 and f11 alone, and you should aim to hit both RC windows as clean as possible, so as to remove execution errors when they do connect (You also get to confirm into f44 in the corner! You can't do that with the aformentioned "Works for Both!" RC timing). You have time to do so. The only exception to this is if we're going to find some crazy OS with a run cancel involved.
I'm actually pretty sure you're all doing this already, you just don't think that you're doing it.
