Currently, in game and even in the base (the place where you buy guns, do training, etc.), if I hold the forward and left/right keys at the same time (I’m on keyboard-mouse, so W+A or W+D) or switch between them, I’ll lose control of my character for a solid second or two, during which time the character aggressively stutters in whatever direction they were going in when I lost control. This happens in matches too, which leads to sometimes shooting off a whole clip or just drifting into a wall until I regain control. In short, whatever input was issued when I lose control acts as though it’s held down and sped up, if that makes sense. It doesn’t seem to happen when I’m just moving forward or in one direction, but seems to only happen when more than one input is issued.
It seems like this bug has appeared in the past for players, but I can’t find anything recent (within the past two years). My system:
ASUS ROG STRIXC B550-F with BIOS version American Megatrends 2423, from 8/10/2021
AMD Ryzen 5 5600X
Nvidia GeForce GTX 1060 6GB
16 GB RAM
Wired keyboard and mouse
Steps to Reproduce (Required):
Create a character (reproduced using Veteran and Zealot)
Hold W key (forward movement) and switch between A and D keys (sideways movement)
Result: I lose control every twenty seconds or so, and the character stutters in whatever direction it was moving when I lost connection. Also seems to happen with other combinations of input, but the above reproduces consistently. (I can try to get a video of it if necessary, but it would take a bit of time and setup.)
I’ve never used a controller. I use a Razer Deathadder V2 mouse, but otherwise no. My keyboard is a Wombat Pine mechanical keyboard. I’ve only ever had it connected via USB.
Edit: Wanted to add that I’ve been trying the game out for maybe about an hour, changing a few settings, seeing if it goes away, etc. My account shows over 3.5 hours because after I closed the game the first time, some process kept running in the background, which Steam understood as the game still running, and I didn’t notice for quite some time (no tray app). I don’t think that was related to the issue either.
Im also having this is issue also dont have mods and i have a i9-14900k 4070 ti super and the game is just unplayable which is sad bc i was having so much fun playing on steam
def still a issue i can see from the past plp where having input lag either from headset or keyboard i cant tell which it is but def a issue making the game unplayable
As another update: The issue carries across Nvidia driver updates (I’m on the latest version for my GPU). I also tried setting the graphics to low, but that doesn’t get rid of it either. I thought it took longer to appear at first, but once it happened, it repeated at a similar interval to the video I posted above (about every 20–30 seconds).
If there are any specific settings I should test around, I’d be happy to.
Although it may seem unrelated, please navigate to the ‘Controller’ tab under ‘Settings’ and change your deadzone to 0.05, slowly increasing until you notice an improvement.
I tested the deadzone in Sefonia’s room, since it’s circular and lets me easily tell how often the issue repeats (as a measure of loops around Sefonia’s machine).
From 0.00 to 0.20 I incremented by 0.01:
0.00–0.11: No clear pattern of improvement. At some values it seemed to perform better (0.03), but right at the next value it would be bad again (meaning about half a loop or less around Sefonia before losing control). Loss-of-control also didn’t follow any clean pattern: I could run 1.5 loops around Sefonia before it triggers, then only half a loop. As far as I could tell, no clean pattern.
0.12–0.20: It seemed consistently better, meaning I could run 1–1.5 loops consistently before losing control, but it didn’t seem to improve the higher the number.
QE work is tedious, so from 0.20 up I incremented by 0.05. The issue seemed to improve between 0.75 and 0.85 (consistently managing 1 to 2 loops around Sefonia before losing control), but 0.90 to 1.00 was markedly worse—practically the same as where I started.
I’m going to leave the deadzone at 0.75 or 0.80 for the next time I have the patience to test. Given the lack of consistent correlation throughout, I wonder if the deadzone is not the cause of the issue. It might be, since I did see some improvement with certain number ranges, but for all I know the issue’s cause might be something else that just happened to occur less during those times. I figure I’ll find out next time I feel like booting up and testing more.
I hope this helps with your troubleshooting the bug.