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

[Slips]

way too many people are blaming the input bug in place of their own failed inputs now, Shits annoying (more so than the actual bug itself, which is incredibly rare)

Your insane man. The input bug happnes ALL THE TIME.

We have video proof of it happening after blocked strings.

We have video proof of it happening standing at neautral.

The input bug also happens randomly at anytime while your OPPONENT is doing a special move. I don't know how many times I've tried to do a d1 when Kung Lao does a teleport and i get a standing 1 and lose 40% of my health. Jax when he does a dash punch you should be able to float him with a d1 since he's airborne. Its nearly impossible because of the input bug. Same with Kitana's flying ass when she does it low to the ground, its bullshit. No video proof of that but just try it for yourself and you'll see how obvious it is. Take Sindell, put it on wake-up attacks and knock her down till you get her EX flight and start doing d1. Its totally random if you get a d1 or a standing 1.

Brady is right about specials too. I've tried to do hellfire but get b+2 instead. Its like the game didn't even read the d part of db+2. I don't know if its because your opponent did a special at the same time to explain it, or if its just random.

But it happens more than enough to take notice.

I hope NRS feels our pain.

 

[Matix218]

[MENTION=41]Tom Brady[/MENTION],

I understand that you are saying that you have spoken to someone at NRS about it (I assume that is what you mean by the horses mouth) and they know what the problem is but they cant do anything about it.

The thing is, how can they not do anything about it if they know what is causing the problem? I have a very limited understanding of software and programming but I would think that if you have a problem causing a bug (such as this input bug) and you know what the problem is that you would be able to fix it via editing the existing code. Am I wrong?

BTW Tom, I am in no way trying to be a jerk or anything like that, I am just confused as to how, if they know what the problem is, they would not be able to fix it?

 

[GGA soonk]

Your insane man. The input bug happnes ALL THE TIME.

We have video proof of it happening after blocked strings.

We have video proof of it happening standing at neautral.

The input bug also happens randomly at anytime while your OPPONENT is doing a special move. I don't know how many times I've tried to do a d1 when Kung Lao does a teleport and i get a standing 1 and lose 40% of my health. Jax when he does a dash punch you should be able to float him with a d1 since he's airborne. Its nearly impossible because of the input bug. Same with Kitana's flying ass when she does it low to the ground, its bullshit. No video proof of that but just try it for yourself and you'll see how obvious it is. Take Sindell, put it on wake-up attacks and knock her down till you get her EX flight and start doing d1. Its totally random if you get a d1 or a standing 1.

Brady is right about specials too. I've tried to do hellfire but get b+2 instead. Its like the game didn't even read the d part of db+2. I don't know if its because your opponent did a special at the same time to explain it, or if its just random.

But it happens more than enough to take notice.

I hope NRS feels our pain.

Yeah, I'm pretty sure I had the input bug at least once against every opponent at Season's Beatings. It gets old...

 

[Big Pampering]

Yeah, I'm pretty sure I had the input bug at least once against every opponent at Season's Beatings. It gets old...

The amount of times the input bug will happen to you also depends on the character you are using, a character that doesnt have a good d4 wont be using it, a character with a d1 that cant really be used for anti air wont use it. If you pick subz you will have a lot of problems if you use d4, just like scorpions d4 and d1.

 

[Sasuga]

NO, we know it happens, we know it cant be fixed, we know what it effects, and we know that it happens more or less based on what controls are used. YOU however are testing and testing for no reason at this point. i know what it effects already and i know why the bug is there. your testing in hopes it will be fixed is pointless, your testing in trying to find a way to avoid it is pointless because there is no way to avoid it.

Who is 'we' in this context? Because a lot of people are still trying to figure out what the hell is up with this bug and why it happens.

Also, If NRS knows what's causing it, they owe us a fix. It's a game breaker. And if it's to complex to be fixed I'd like some kind of explanation. How hard can that be.

 

[simtmb]

Who is 'we' in this context? Because a lot of people are still trying to figure out what the hell is up with this bug and why it happens.

Also, If NRS knows what's causing it, they owe us a fix. It's a game breaker. And if it's to complex to be fixed I'd like some kind of explanation. How hard can that be.

What kind of an explanation do you want? Tom explained enough about what he knows concerning the input bug, and as far as i and many others are concerned, discussion is over and it's simply something everyone has to put up with. Since NRS has known about it for a long time now, I'm sure no fix yet is as close as it gets to NEVER EVER being fixed.

There's nothing that can be done about it, so we should just leave it at that. What else can we do? There's no way to even remotely avoid it from occurring.

 

[Sasuga]

What kind of an explanation do you want. Tom explained enough about what he knows concerning the input bug, and as far as i and many others are concerned, discussion is over and it's simply something everyone has to put up with. Since NRS has known about it for a long time now, I'm sure no fix yet is as close as it gets to NEVER EVER being fixed.

There's nothing that can be done about it.

I was thinking in the lines of :

- "The input bug can't be fixed, because.... <insert explanation>".
- "The input bug occurs, because... <insert explanation>".

Obviously I missed Tom explaining all he knows and just got the "it can't be fixed" and that "we" know all about it.

 

[GGA soonk]

The amount of times the input bug will happen to you also depends on the character you are using, a character that doesnt have a good d4 wont be using it, a character with a d1 that cant really be used for anti air wont use it. If you pick subz you will have a lot of problems if you use d4, just like scorpions d4 and d1.

The two characters I just so happen to play...

God forbid NRS gives us an official statement, or maybe even a -gasp- apology.

 

[Big Pampering]

The two characters I just so happen to play...

God forbid NRS gives us an official statement, or maybe even a -gasp- apology.

that wouldnt be too good for their sales would it?

 

[webreg]

Ok, I completely agree with Brady on one thing. I think it's pointless to ask for a fix. I'm fairly certain they knew about this even before they released it. Yes I'm saying they knew of this bug and released the game with it none the less because they weren't able to fix it without messing up the whole engine and investing a lot of time and money to Q&A again. Maybe even move the release date and that would have cost them a fortune at a time where the games success wasn't yet certain. People don't like to hear that but that's just how this business works. Any business for that matter.

I think it's unfortunate but it's what it is. I don't agree with their silence on the matter though. It's nice that Brady thinks he knows everything there is to know about the bug and maybe he does but I don't and problems like that are never random. The law of cause and effect applies here like everywhere else. Toms tactic to deal with it is apparent: Playing and ignoring. Maybe it happens, maybe it doesn't. That's a perfectly legit way to deal with it but not one I'm happy with. I want to know. Why? Let me give you an example.

Sometimes I'm messing up Smokes 3,D1,2 and get 3,1 instead. Now, should I work on that to improve my execution or is it the bug? Currently I don't know. Knowledge about it would certainly change the way I play because I can simply choose to do 3,2 instead and this only does 1% or 2% less damage in a combo yet the bug can't happen here. I'd rather choose to do 2% less in a combo than gamble and loose 30% in the end. It's that simple.

 

[Sasuga]

This game is now a bad joke. The punchline is that there IS knowledge that is not power.

Hahahahahahahahahahahahahahahahahahahahahahhahahahahahahahhahahahahahhahahahahahahahhahahahahahaha.