Pushblock doesn't work sometimes

[Slyzor]

I'm probably half a year late but still. Sometimes when I use pushblock just nothing happens. This wasn't a case before. Makes doing pbgc kinda hard and unreliable.

 

[IsaVulpes]

"Sometimes" is a very great help in figuring out why and where

How about a recorded replay on slowmotion, where you show your inputs so we can see you pressing PP in blockstun
Or an easily reproducible case..

 

[Slyzor]

AI did 3 s.HP hits, pushblock worked only on the last, though the first two weren't registered as PP. Not sure what's up with that, but I really don't recall this problem being the case like a year ago or so.

Edit: I don't have a problem with PP supers.

 

[Lawnalog]

you just didn't press the the two punches at the same time on the first two tries.

 

[Slyzor]

Weeeell, I did. They just didn't registered as 2 punches. You can see how maybe not quite on the first s.HP, but on second one 2 punches appear simultaniously.

Edit: By the way, about supers. You can see how 2 punches weren't registered as PP but still super did came out.

 

[mcpeanuts]

Weeeell, I did. They just didn't registered as 2 punches. You can see how maybe not quite on the first s.HP, but on second one 2 punches appear simultaniously.

Edit: By the way, about supers. You can see how 2 punches weren't registered as PP but still super did came out.

For supers, the two punch buttons can be pressed up to 3 frames apart and the super will still come out. I don't honestly know if pushblocks have the same kind of leniency.

 

[Sotherius]

Try to set a macro for 2P. and test the pushblock that you're not getting with it.

 

[Adeveis]

I've honestly had this problem too where i mash pushblock but get nothing. I thought i was just bad.

 

[Lawnalog]

I've honestly had this problem too where i mash pushblock but get nothing. I thought i was just bad.

your thought was correct.

 

[mcpeanuts]

your thought was correct.

Ohhhhhhhhhhhhhhh shiiiiiiiiiiiiiiiiit

 

[Mike_Z]

For supers, the two punch buttons can be pressed up to 3 frames apart and the super will still come out. I don't honestly know if pushblocks have the same kind of leniency.

They do, anything requiring PP or KK uses the same code path (pushblock, supers, unfly, dashing, etc). It's 2 frames, though, not 3.

AI did 3 s.HP hits, pushblock worked only on the last, though the first two weren't registered as PP. Not sure what's up with that, but I really don't recall this problem being the case like a year ago or so.

In the first two examples those buttons are pressed WAAAAAAY further apart than 2 frames. 4-6 frames at least.

The unfortunate answer to your question is PEBCAK (user error). In your video it's really obvious.

Edit: I don't have a problem with PP supers.

Supers can be negative-edged, for example:
Press MP ... Press HP + Release MP
or
Press MP ... Press HP, Release HP + Release MP
will count for a super because you are negative-edging one or both of the buttons.

I really don't recall this problem being the case like a year ago or so.

Well then, either you got worse, or your hardware degraded.
According to version control, no code or script even remotely associated with input processing or pushblocking has changed in any way since...let's see...December 24th, 2013.

I've honestly had this problem too where i mash pushblock but get nothing. I thought i was just bad.

See the answers above.

 

[Slyzor]

Okay, thx Mike.