NRS.. PLEASE fix the input drop bug!!!

[funkdoc]

Here's a thought: Get 2 good players in training mode and just have them fight with input display on. When you get the input bug, STOP ALL MOVEMENT so that the display remains on-screen. I think having the display will make this a lot more convincing to NRS.

 

[Death]

I agree with everything the OP said. Every other match when i use Mileena i meant to do D+4 but standing 4 comes out and ate huge combos because of this. Annoying as hell but i guess everyone has to deal with it so whatever.

 

[Slips]

I replicate it all the time in practice mode. Try holding down for like a half second then push 1. You by all intensive purposes should get a d+1, but you actually SEE your character begin to crouch and get a standing one. Its really terrible.

 

[funkdoc]

Ya Slips, same with me. I just never think to capture AVIs when messing around in training mode, but I should def start on that.

 

[Sabin]

MK9 controls are on some OG SNK game status (shitty, buggy)

 

[Dark Kobra]

Ive posted this a few times before, but try going into practice mode. Press up as fast as you can. If done correctly, the input will appear on screen and you will not jump. try doing d1 while pressing down as fast as possible. the down will show on the input, but if done fast enough, you will get a standing 1.

Again, if done correctly, you can replicate this 100% of the time. I don't know if this has anything to do with the input bug, but something to consider as it may well be.

Yep mate, that happens all the time to me. I don't know how much you can replicate this on a controller, but on a Hitbox™, you can get this glitch out 100% and it's a pain when using characters that use instant air techniques, i.e Liu Kang, Kabal, Mileena, Kitana etc.

It has happened to me lots and I'd say 90% of my losses have been due to the inability of the iaf to come out, even though I can get the command out 100%.

 

[Tremloc]

Ive posted this a few times before, but try going into practice mode. Press up as fast as you can. If done correctly, the input will appear on screen and you will not jump. try doing d1 while pressing down as fast as possible. the down will show on the input, but if done fast enough, you will get a standing 1.

Again, if done correctly, you can replicate this 100% of the time. I don't know if this has anything to do with the input bug, but something to consider as it may well be.

post a video so you can shut everyone up and tym can pressure nrs about it.

 

[FatalTragedy]

Is this what's caused my Kabal pressure game to take a hit since the patch? I took a few weeks off to learn Sektor, and after the patch I started using Kabal again to keep up on execution and I'm missing nomad dash cancels like crazy and eating full combos for it. It's bizarre. I know I took some time away to learn a new character but my execution can't be THAT off. My pressure game was pretty solid up until this point.

 

[Robotic]

Is this what's caused my Kabal pressure game to take a hit since the patch? I took a few weeks off to learn Sektor, and after the patch I started using Kabal again to keep up on execution and I'm missing nomad dash cancels like crazy and eating full combos for it. It's bizarre. I know I took some time away to learn a new character but my execution can't be THAT off. My pressure game was pretty solid up until this point.

No, it's been an issue since day 1. But again, I'm not entirely sure what I found (or at least posted) has anything to do with the input glitch.

 

[Shadowfire]

I've tested it myself on a Hitbox. I still haven't seen any evidence that it's not a result of crouching taking a non-zero number of frames. Why is no one addressing that?

Is this what's caused my Kabal pressure game to take a hit since the patch? I took a few weeks off to learn Sektor, and after the patch I started using Kabal again to keep up on execution and I'm missing nomad dash cancels like crazy and eating full combos for it. It's bizarre. I know I took some time away to learn a new character but my execution can't be THAT off. My pressure game was pretty solid up until this point.

And I'm pretty sure this is exactly how legends like this start.

 

[Tremloc]

I've tested it myself on a Hitbox. I still haven't seen any evidence that it's not a result of crouching taking a non-zero number of frames. Why is no one addressing that?

It's possible the issue is related to crouch frames, or movement frames in general. However, that still doesn't account for multiple people confirming that inputting the jump command sometimes makes your character not jump, even though the input shows up on the screen. We should investigate that avenue as well.

Any guesses we make are purely speculation, but we really need to come up with a test case that reproduces the issue with a higher grade of consistency. Then we can bring it to NRSs attention.

If we're able to reproduce it, we should be able to record it in training mode.

 

[Shadowfire]

It's possible the issue is related to crouch frames, or movement frames in general. However, that still doesn't account for multiple people confirming that inputting the jump command sometimes makes your character not jump, even though the input shows up on the screen. We should investigate that avenue as well.

Any guesses we make are purely speculation, but we really need to come up with a test case that reproduces the issue with a higher grade of consistency. Then we can bring it to NRSs attention.

If we're able to reproduce it, we should be able to record it in training mode.

Jumps also don't happen in one frame, that's by design. It's why down->up moves don't have just frame timing.

 

[GGA soonk]

There are crouching frames but that's not the issue. Uploading videos right now and will post.

 

[Tremloc]

Jumps also don't happen in one frame, that's by design. It's why down->up moves don't have just frame timing.

But if the game shows input up, and my character doesn't jump, then something is wrong. Please explain your post further.

 

[GGA soonk]

But if the game shows input up, and my character doesn't jump, then something is wrong. Please explain your post further.

Right. Jumps don't happen in one frame but they should come out after 1 frame of input, which they do not.

 

[GGA soonk]

Ok here are some vids I made. I'm using a hitbox so I can be sure of no mistakes while recording.

First Vid. Addressing the jump input thing. I am tapping and releasing each direction except for when you actually see me jump. That's to verify my jump button actually works.

Second Vid. Instant D1s are fine. Hit both buttons one right after the other(let go of down or not, doesn't matter) and d1 will come out.

Third Vid. I am holding the down button until the end of each 1. There seems to be a 1 frame window where you will get a standing attack instead of a ducking attack. Sometimes I can get the timing right over and over but this is all I was able to record. You should get the idea.

Fourth Vid. Went back out to record some more. In case there was any doubt about it being caused by the constant D1s. Again, I'm holding down each time I press it until the end of the move.

 

[NRF CharlieMurphy]

... awesome.

 

[GGA soonk]

If I'm right about the 1 frame input drop, that would explain Brady's comments at Devastation about ice blast(DF3) and ice clone(DB1) not working right. Perhaps if the F3 and B1 were hit during the 1 frame window, it would cause the down not to register and give standing attacks instead.

 

[Slips]

There is some weird business doing moves out of strings or block or something too. Like with smoke I'll do his 3,d1,2 and will be mashing d1 after and will get a standing 11. It pisses me off to no end.

 

[Robotic]

I've been talking about this for months, thank you Soonk. How much this has to do with the input glitch is to be determined...

 

[Robotic]

There is some weird business doing moves out of strings or block or something too. Like with smoke I'll do his 3,d1,2 and will be mashing d1 after and will get a standing 11. It pisses me off to no end.

In the instances when you mash, it is likely you have hit one of those mashes on the 1 frame where it does not recognize your direction yet, causing a standing 1.

 

[GGA soonk]

Yeah, I don't have the free time right now to test out the crazyness involved with blockstrings and specials etc. Later today I will do some more. Can't believe nobody has made vids of this yet. Honestly I just got tired of hearing about it with no proof. Thanks Slips for the 'hold down for a half second' idea. I think this 1 frame of dropped input could be the answer to all input bugs, since that's all it really takes. Hopefully more testing will prove or disprove, and hopefully Storms can front page those vids to get some attention rather than people just blowing off the input bug due to lack of evidence.

 

[Drayn0]

This bug seems to become more prevalent the more I play the game. There are combos with skarlet that I can hit only 1/3 of the time due to the input bug. IN practice mode you can even see the controls being put in but the move itself won't come out.

 

[Tremloc]

Ok here are some vids I made.

awesome! thank you so much for this soonk!

 

[Slips]

In the instances when you mash, it is likely you have hit one of those mashes on the 1 frame where it does not recognize your direction yet, causing a standing 1.

Well.. I hope that gets fixed too then, because in every other fighting game in existence if your holding down during hit or block stun or recovery and are mashing a button you get the crouched version. I do 111 with Scorp, and am holding down during the last 1 and mashing 4 but I don't get a d+4 but a standing 4 and I lose the match for it. Its just awful.

Its contradictory for NRS to have had such a huge negative edge window to help with special move inputs but have such precision with directional inputs. Its not intentional of course, I just hope they fix it.