Input key queue bug (delay with Thrust Attack)

@GODAIME does your keyboard have n-key rollover? if it doesn't then you're probably maxing out the amount of simultaneous key presses

http://gadzikowski.com/nkeyrollover.html

watched the video seemed like you weren't moving at all when your inputs got eaten, in any case we'll look into it

I do have the same problem, most often with stabs (mousewheel up) but sometimes it also seems to happen with other attacks. Might just be me for the other attacks, but for the stabs I'm 100% sure that I am scrolling the wheel, even more than once at times, and the attack won't start until the 3rd-4th time I scroll. I died many times to this :( I'd say it happens randomly, about every 2-3 rounds I think so about once in 30 minutes?

Edit: fully mechanical keyboard with no N-key-rollover and gaming mouse both bought new around Christmas 2018, and both have zero issues in any other game, if that matters

I get the delayed/no stab input as well, fucks me over allot when chambering as well as the stabs occurring on their own with 0 input on my side, I di used to get this on Chiv occasionally but it's not my hardware as I've tried different mice.

Edit: fully mechanical keyboard with no N-key-rollover and gaming mouse both bought new around Christmas 2018, and both have zero issues in any other game, if that matters

If it's fully mechanical then you probably meant that it DOES (YES) have n-key rollover. Minor error but it helps to be accurate for the devs to fix this.

I'm having the issue as well with an n-key rollover keyboard (Razer Blackwidow Tournament 2014).

However I've also played this game with a non-mechanical non-n-key rollover keyboard and it maxes out on key presses very quickly to the point where it is very difficult to move and swing at the same time. This felt exactly like what happens when my mechanical keyboard fails to register the inputs.

If I had to make a guess, it seems like flinch lag (the server is not telling your game client that you're done flinching yet) or it's some kind of bug with the way they buffer inputs to detect combos and such. Not totally sure though.

My PC is top notch like the OP, so it can't be a hardware issue.

@sloe said:

Edit: fully mechanical keyboard with no N-key-rollover and gaming mouse both bought new around Christmas 2018, and both have zero issues in any other game, if that matters

If it's fully mechanical then you probably meant that it DOES (YES) have n-key rollover. Minor error but it helps to be accurate for the devs to fix this.

whoops, sorry, that's true and I had it reversed in my head for some reason :)

Some of my friends have complained about this

@blobl said:
I am in the same boat, your video perfectly shows what happens but for me it is all my attack that will stop responding for several seconds. My character just turn around like a weirdo and I die in two hits.

Great game but this bug enrages me so much if it is not fixed in next patch I am not sure I will endure it anymore.

Edit: And strangely my movements are never bugged, I always have full control of my character but yea something is full of shit with the attack detection like you said

Same happens to me, but I also have it effect swings. It is so infuruating to die to this that I'm considering just stopping altogether.

It occurs mostly in hug distance, I've noticed.

I believe I've only experienced this input bug online (thought I haven't played much with bots since release) and I noticed I have a bunch of these lines on my log.

[2019.06.17-20.39.27:095][604]LogNetPlayerMovement: Warning: CreateSavedMove: Hit limit of 96 saved moves (timing out or very bad ping?)

Could it be my client fills the buffer too quickly and before it's emptied in time, it just ignores the input? (I have no coding in games experience btw so I could probably be talking out of my ass).

I also found this post in the UE4 support section:

https://answers.unrealengine.com/questions/158542/server-not-processing-moves.html?sort=oldest

Yup that bug is not fixed and it seems to be worst with stabs since last patch.

@Alphonse said:
I believe I've only experienced this input bug online (thought I haven't played much with bots since release) and I noticed I have a bunch of these lines on my log.

[2019.06.17-20.39.27:095][604]LogNetPlayerMovement: Warning: CreateSavedMove: Hit limit of 96 saved moves (timing out or very bad ping?)

Could it be my client fills the buffer too quickly and before it's emptied in time, it just ignores the input? (I have no coding in games experience btw so I could probably be talking out of my ass).

I also found this post in the UE4 support section:

https://answers.unrealengine.com/questions/158542/server-not-processing-moves.html?sort=oldest

Yeah they should look into this. I have some UE4/Unity/coding experience and that was one of my assumptions too. Good thinking!

It was hitting me hard today, there has got to be something up with it.

I experience this a fair bit. Glad to see it's a more common issue and not necessarily on my end or my imagination.

Hope there's some info and a fix in the near future.

same problem here for me as stated in the many threads

@GODAIME said:
Hi,

Sometimes in game my thrust attack, which is binded to E key, doesn't work (Yea, I said delay, but actually it doesnt work for more than 2-3 seconds and more. I'm using the "work around" and don't know how bad it can be).

Why is this a bug and not lag/pc problem:

1. When this bug happens.. i hit ESC key to get into the menu.. and spam ESC again to get out of it and it won't work. It works only if I spam hit left mouse key in the menu, and then it closes and the bug is gone.
2. My PC is i7 8700K, NVidia 1060 6GB, 16GB RAM, SSD and I play on medium/high to get 100+ fps for my monitor to show. Can't be processor problem.
3. I never join servers with more than 60 ping in the browser. I don't use main screen server options.
4. There are also other threads about this same issue around the WEB.
5. https://www.youtube.com/watch?time_continue=1&v=DdiNmYxdWSY

Hints:

• happens mostly on duel servers, rarely in frontline. Maybe this is because I morph often, which means I hold/click E (thrust attack) more often and it mess up the key queue or something, but it feels like the key queue is full of shit.
• swings works fine (morphs are impossible).
• this might be related to the stamina checks and not the input queue
• maybe this bug is rare, because me and this guy from the video have it binded to custom key?

Are you using angle after attack press? That would explain a few weird cases, e.g. where nothing is happening when you're not moving the view @ 22. Other than that, it seems largely you're hitting the input in recovery, which will just be ignored right now since attack is not allowed there. The game may have been conditioning you wrong in some cases because the game does queue in hit recovery a little bit, but not in miss recovery, which admittedly, is a bit weird and should probably be adjusted in the future.

EDIT: actually, not sure if the angle after attack press could explain that, but let me know if you do have that enabled anyway.

@Marox I have instances where I've parried but chosen not to riposte but attack a moment later (usually a stab as it's quick) and nothing will happen with several presses. All I do in walk around in front of my opponent holding a still weapon and hand him initiative or, failing that, start an attack I have to FTP out of.

I'll try and get an input view thing so I can see my keypresses realtime and study gameplay footage to see if it is my fault or something else.

@marox said:

@GODAIME said:
Hi,

Sometimes in game my thrust attack, which is binded to E key, doesn't work (Yea, I said delay, but actually it doesnt work for more than 2-3 seconds and more. I'm using the "work around" and don't know how bad it can be).

Why is this a bug and not lag/pc problem:

1. When this bug happens.. i hit ESC key to get into the menu.. and spam ESC again to get out of it and it won't work. It works only if I spam hit left mouse key in the menu, and then it closes and the bug is gone.
2. My PC is i7 8700K, NVidia 1060 6GB, 16GB RAM, SSD and I play on medium/high to get 100+ fps for my monitor to show. Can't be processor problem.
3. I never join servers with more than 60 ping in the browser. I don't use main screen server options.
4. There are also other threads about this same issue around the WEB.
5. https://www.youtube.com/watch?time_continue=1&v=DdiNmYxdWSY

Hints:

• happens mostly on duel servers, rarely in frontline. Maybe this is because I morph often, which means I hold/click E (thrust attack) more often and it mess up the key queue or something, but it feels like the key queue is full of shit.
• swings works fine (morphs are impossible).
• this might be related to the stamina checks and not the input queue
• maybe this bug is rare, because me and this guy from the video have it binded to custom key?

Are you using angle after attack press? That would explain a few weird cases, e.g. where nothing is happening when you're not moving the view @ 22. Other than that, it seems largely you're hitting the input in recovery, which will just be ignored right now since attack is not allowed there. The game may have been conditioning you wrong in some cases because the game does queue in hit recovery a little bit, but not in miss recovery, which admittedly, is a bit weird and should probably be adjusted in the future.

EDIT: actually, not sure if the angle after attack press could explain that, but let me know if you do have that enabled anyway.

I disabled it myself. I get the bug with slashes too. Enough people are noticing this that it's worth investigating. It can't be recovery delay when you haven't done anything to trigger a recovery. Literally had people in hug distance wiff a thrust, then try to swing to punish and have to press 4 or 5 times for the swing to register.

@alonesilverwolf said:
I disabled it myself. I get the bug with slashes too. Enough people are noticing this that it's worth investigating. It can't be recovery delay when you haven't done anything to trigger a recovery. Literally had people in hug distance wiff a thrust, then try to swing to punish and have to press 4 or 5 times for the swing to register.

Yes exaclty.

Also please clear the input queue when we respawn because I always do an attack for no reason when spawning, attacking my teammate and losing stamina

For me it's a bit of a mixed bag. Thrust, Slash, Feint, Parry just don't register randomly.

I noticed it seems to happen a lot for me after I parry, which is especially bad when you are in frontlines with 1 vs x enemies & you parry then go in for a swing attack, but nothing happens so you just end up getting hacked up by them while standing there looking like an utter tool with your ding-dong in your hand.

It also happens randomly too where I've pressed my right mouse button to parry (while not attacking) & nothing happens, which is really fun on duel servers.

Me & a friend tested the stab chamber thing (he wanted to cheese the chamber achievement), & all we were doing was back & forth stabs. We did that for about 10+ minutes until he got the achievement. We'd more often than not make it until our stamina was almost drained, but there was quite a bunch of times where after a couple or thrusts back & forth that one of us would get stabbed. I just thought we were messing up the timing before, but now I don't think that was the case as it's not difficult to spam scroll the mouse wheel up, or tap whatever button/key you've bound thrust attacks to (in my case both of my thumb buttons).

In regards to input queue thing, it's a little annoying. You input a specific attack/feint/parry & your character decides to do something else entirely, like if I do a thrust/slash attack & they decide to do the opposite, or parry/feint instead. It makes me rage & shout at my screen more than the input delay issue.

@de.tail said:
For me it's a bit of a mixed bag. Thrust, Slash, Feint, Parry just don't register randomly.

I noticed it seems to happen a lot for me after I parry, which is especially bad when you are in frontlines with 1 vs x enemies & you parry then go in for a swing attack, but nothing happens so you just end up getting hacked up by them while standing there looking like an utter tool with your ding-dong in your hand.

It also happens randomly too where I've pressed my right mouse button to parry (while not attacking) & nothing happens, which is really fun on duel servers.

Me & a friend tested the stab chamber thing (he wanted to cheese the chamber achievement), & all we were doing was back & forth stabs. We did that for about 10+ minutes until he got the achievement. We'd more often than not make it until our stamina was almost drained, but there was quite a bunch of times where after a couple or thrusts back & forth that one of us would get stabbed. I just thought we were messing up the timing before, but now I don't think that was the case as it's not difficult to spam scroll the mouse wheel up, or tap whatever button/key you've bound thrust attacks to (in my case both of my thumb buttons).

In regards to input queue thing, it's a little annoying. You input a specific attack/feint/parry & your character decides to do something else entirely, like if I do a thrust/slash attack & they decide to do the opposite, or parry/feint instead. It makes me rage & shout at my screen more than the input delay issue.

Oh yeah, the input queue thing has gotten very noticeable for me since the last patch. Happened rarely for me before, where I'd want to thrust. and end up swinging instead. Happens a LOT more frequently recently.

idk how a game that was pushed back so much, launches with these issues. Very irritating, to say the least.

I'd like to remind that this bug is not fixed and is REALLY annoying

@blobl said:
I'd like to remind that this bug is not fixed and is REALLY annoying

Nope, not fixed and it is one of the reasons I stopped playing for 2 weeks up until today. Had a few hours of duels, and yet again, I'm done.

Man seriously, fuck these incompetent devs. They really don't seem like they give a flying shit at this point.