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

[AU_IM_DIGIMON]

The input bug is very real. Confirmed for me at Seasons beatings with Soonk, THTB, and ChaosShpere.

And this is coming from someone who undoubtedly thought it was complete bullshit (me).

All you need to do is test the "liu kang b+3,1,2 punish" test. And you''ll get standing 1s and 3s for NO REASON! And it DOES happen randomly. This was tested in training mode with two human players.

But I WILL say that, the input bug hasn't effected me mid match...yet.

Regardless this NEEDS to be fixed. And hopefully this will be fixed soon.

Since this bug happens randomly it's extremely hard to tell the difference between the bug actually happening and human error. When you press and release block and when u actually hit the buttons and when your character is at neutral or not - all play a part of human error (possibly) kicking in, when u fuck up. So just keep that all in mind.

This whole issue is annoying. But it really shouldn't prevent people from playing the game. I know the bug truly exist now. But it still hasn't happened to me mid match, and I really can't tell you why. =/

 

[Matix218]

The input bug is very real. Confirmed for me at Seasons beatings with Soonk, THTB, and ChaosShpere.

And this is coming from someone who undoubtedly thought it was complete bullshit (me).

All you need to do is test the "liu kang b+3,1,2 punish" test. And you''ll get standing 1s and 3s for NO REASON! And it DOES happen randomly. This was tested in training mode with two human players.

But I WILL say that, the input bug hasn't effected me mid match...yet.

Regardless this NEEDS to be fixed. And hopefully this will be fixed soon.

Since this bug happens randomly it's extremely hard to tell the difference between the bug actually happening and human error. When you press and release block and when u actually hit the buttons and when your character is at neutral or not - all play a part of human error (possibly) kicking in, when u fuck up. So just keep that all in mind.

This whole issue is annoying. But it really shouldn't prevent people from playing the game. I know the bug truly exist now. But it still hasn't happened to me mid match, and I really can't tell you why. =/

Its DEF not going to keep me from playing/loving the game, going to tournaments, etc. Like Funkdoc has been saying there are bugs just as bad if not worse in all of the major Capcom fighters as well and we all know how popular those are.

I do hope NRS can fix this though (IE i hope it is something that they can actually pinpoint and figure out what causes it in the code so they can come up with a solution).

The input bug will not keep me from playing the game by any means, it really does not happen that often.

Of course now on streams when someone gets any kind of standing attack the first thing the commentators say is usually "input bug" lol (even though 80ish% of those standings are probably due to user error and not the actual bug)

 

[Scoot Magee]

Yeah any move involving a directional input can be affected by this glitch. I've had it happen a ton of times with uppercuts,scorps back 2 and forward 4, down 4 and ect.

Also about the crouching under projectiles thing mentioned in the first post. I' have this problem vs sub zero also. I realized that if crouch while back dashing my hitbox will stay high until my character is completely stationary. This makes it so freeze and probably other projectiles will hit you. You have to come to a complete stop and then crouch which is retarded imo. Also while on the subject of back dashing, why can't striker block after a canceled gun? You have to wait for the animation of the dash to finish before you can block.

 

[GGA soonk]

Yeah any move involving a directional input can be affected by this glitch. I've had it happen a ton of times with uppercuts,scorps back 2 and forward 4, down 4 and ect.

Also about the crouching under projectiles thing mentioned in the first post. I' have this problem vs sub zero also. I realized that if crouch while back dashing my hitbox will stay high until my character is completely stationary. This makes it so freeze and probably other projectiles will hit you. You have to come to a complete stop and then crouch which is retarded imo. Also while on the subject of back dashing, why can't striker block after a canceled gun? You have to wait for the animation of the dash to finish before you can block.

Yeah, it's like there's a ducking while moving animation. You could avoid this by dash-> d4 but then if you get the input bug you're fucked anyways. The problem with the input bug is it tends to come out during critical moments, ie poking out of pressure or trying to d1 anti air. It happened in over half of my matches at SB, not just to me but to my opponent.

 

[webreg]

Ok, I have tested only one move that used a directional input other than "down" and it wasn't reproducible. So I'll go, like right now, and test this "liu kang b+3,1,2" although I don't understand what the "punish" means in that context because I don't understand how or why it should be in any way, shape or form important to the state of the opponent.

uppercuts,scorps back 2 and forward 4, down 4 and ect.

I'll test that too.

 

[THTB]

That exists for any special that can be dash-cancelled. It's not just limited to Stryker's gun cancel. It's likely intended, if there hasn't been anything done for it yet.

 

[GGA soonk]

Ok, I have tested only one move that used a directional input other than "down" and it wasn't reproducible. So I'll go, like right now, and test this "liu kang b+3,1,2" although I don't understand what the "punish" means in that context because I don't understand how or why it should be in any way, shape or form important to the state of the opponent.


I'll test that too.

What he meant was it is easiest to test the input bug trying to d1 out of the B312 pressure. Nothing wrong with the b312 itself.

Any luck on testing vanilla MK?

 

[Tremloc]

This is the most definitive proof. I recommend the discussion migrate to this thread.

And I also recommend that people stop being morons that don't actually read the OP and thus talking about the non-instant jumps like they're related to this.

Well, include yourself in that moron statement because you've been discussing it with the rest of us. I think we concluded that it wasn't related to the input issue. However, input anomalies should be scrutinized so we can have a better understanding of what's going on.

I don't understand the moron comment though, I thought we were having a healthy discussion about it; no reason to be a jerk.

 

[FatalTragedy]

Is Sektor's b3 an issue? I get a lot of naked 3's while recovering from block stun. Again, probably just me but I have to know.

 

[GGA soonk]

Is Sektor's b3 an issue? I get a lot of naked 3's while recovering from block stun. Again, probably just me but I have to know.

You might be hitting the B before you're fully out of block stun and it won't register.

 

[webreg]

What he meant was it is easiest to test the input bug trying to d1 out of the B312 pressure. Nothing wrong with the b312 itself

Damn, could have said that earlier. ance:
Well, practice for me I guess and confirmation of my previous results. No test is ever useless as long as it was properly executed. Sorry Digimon for misquoting you but I'd like to keep the results up if you don't mind.

 

[webreg]

You might be hitting the B before you're fully out of block stun and it won't register.

Doing that now.

 

[GGA soonk]

Damn, could have said that earlier. ance:
Well, practice for me I guess and confirmation of my previous results. No test is ever useless as long as it was properly executed. Sorry Digimon for misquoting you but I'd like to keep the results up if you don't mind.

I did. Problem is, we're on two different threads lol. Anyways your test isn't worthless, as it shows we shouldn't be experiencing drops on standard normals, only downpokes.

 

[webreg]

So, what about a completely unpatched version of MK9? Well, ...


Look at the inputs. As I said 100% repeatable, no randomness and patches don't matter.

 

[GGA soonk]

Thanks. Not what I expected, but good to know it's been the same and we weren't being taken for a ride with negative edge.

 

[webreg]

Anyways your test isn't worthless, as it shows we shouldn't be experiencing drops on standard normals, only downpokes.

Exactly.

Thanks. Not what I expected, but good to know it's been the same and we weren't being taken for a ride with negative edge.

Well I have tested an up to date and an unpatched version. I can't say anything about the patches and versions in between.

 

[GGA soonk]

Exactly.

Well I have tested an up to date and an unpatched version. I can't say anything about the patches and versions in between.

Negative edge was only changed in the last patch, so vanilla MK would have shown a change had there been any. Thanks for the extra effort.

 

[GGA soonk]

MODS, please close this thread. we know the bug exists but it cannot be fixed, it is here until MK10 so there is no reason to keep a thread asking for it to be fixed open.

Right now we're testing it's ramifications and how far it extends. So far special moves have been shown to be unaffected. We'll have to find another reason for your missed specials, Tom.

 

[DanCock]

I have had my inputs dropped during specials alot. Who ever is doing the testing use sindel.


Sent from my iPad 2 using Tapatalk

 

[DanCock]

Also I'm thinking negative edge might be the thing causing all of this.


Sent from my iPad 2 using Tapatalk

 

[GGA soonk]

I thought so, too, dan, but didn't they just change the negative edge window? From webreg's testing, nothing has changed between vanilla MK and what we have now.

Tom, I'm not saying you're retarded for being unable to do specials, but webreg has been unable to reproduce dropped specials due to the input bug. All this means is there is another cause, whether it be the way the game reads commands or some other input drop. It just seemingly has nothing to do with this input bug.

 

[webreg]

Edit: Deleted and reposted below due to corrections.

 

[Chaosphere]

i am telling you that it happens ANYTIME down is involved for a fact. any special that has down in it gets effected. i am unsure about the F and B inputs as i havent tested it enough but i am positive on down.

its so random on specials, sometimes it almost never happens, sometimes it happens all the time.

again, MKDC i used GL.. its the same engine.. i NEVER.. i mean 0.0% of the time got a standing 3 instead of DF3 or 1/B1 instead of DB1. i find it hard to believe that now i magically miss the same inputs that i abused so much in the same fucking engine. if i have my own input execution issues why did i not have this problem on the same commands then?

for a fact, anything with down has a bug and this may extend to other inputs but i have not tested extensively on anything but down.

i can totally see this being true. I don't see specials being any different from a downpoke if it involves the down command. if it happens with d+1, then why cant it happen with d, f+1. of course this is just speculation from my end.

 

[THTB]

Also I'm thinking negative edge might be the thing causing all of this.


Sent from my iPad 2 using Tapatalk

This existed before the negative edge change.

 

[webreg]

if it happens with d+1, then why cant it happen with d, f+1

Because holding the "down" command is the problem in combination with the next command and "forward" doesn't care if you are standing or not, "1" does. For a "down 1" you absolutely have to press "1" WHILE you are holding "down". In "down forward", "forward" only cares that "down" was pressed previously and not that it is still pressed. So no, can't happen because the bug is the game "forgetting" that the character is currently crouching.