Ideas
17 Comments
- MajooSH9 days agoNew Spectator
Same. it seems to be global issue, still waiting for patch
- CooloutAC9 days agoSeasoned Ace
I don't have this issue. what kind of kb do you have? I have one of those 8000hz magnetic keyboards and my A and D keys are bound with SOCD. I did return one KB though, where the A and S key was bound to the FN key to change between F keys and MAC, and it caused conflict when SOCD was enabled so I returned it. This sounds like it is your issue too brother. You have one of those smaller 68% kb without f keys? The keyboard I have now has the multimedia keys like mute, volume +,-, as b,n,m keys. which is much better for gaming. I have an mchose board, returneds a cidoo. I contacted the company about this issue how it is an oversight for a kb marketed as a gamer kb, to have A and S bounds to the fucntion key, because A keys is used by most gamer for strafing. I would change your keyboards.
- Blueh9 days agoSeasoned Novice
That's not his issue, and you're wrong. For the past 5 days there have been continuing reports of this happening.
- Blueh9 days agoSeasoned Novice
In the same boat as you, man. I also don't have Afterburner or RTSS installed, so disabling them is not an option.
My only "fix" has been to go through all my programs and disable anything that remotely resembles an in-game overlay. Even then, it's inconsistent; I will sometimes get the issue and sometimes not.
Try to do the same, then hop into the firing range first, and see if you have the issue. If you do, nuke the game and try again. This has been the only way I have been able to play. - REPTYLE_NL8 days agoSeasoned Traveler
1000% a javelin bug because it tracks keyboard presses
- RegularJohn538 days agoRising Spectator
I’m sorry I didn’t understand half of what you just said. I’m on a gaming laptop I never used anything fancy and as I said I’m only having this issue since the winter update before that everything worked fine.
- RegularJohn538 days agoRising Spectator
That’s what iI’ve been doing too. Checking the firing range first. Yesterday I had two sessions in the first everything was normal but in the second I had issues with pressing S.
- cemersen8 days agoNew Spectator
Yeah I think this is highly likely because I tried everything yesterday from BF1 up to BF6 and could replicate the issue in all games. Every other game (CS2, Cyberpunk etc.) I have tested is running smoothly so I can confirm it is a BF specific issue. Funnily, when you play with a controller, it doesn't happen, at least in BF6, I tested this as well.
- REPTYLE_NL8 days agoSeasoned Traveler
Correct, just finishing testing. BF1, BF5, and 6: pressing A or S makes the game stutter or drop frames. W and D are not impacted by this bug.
This must be the javelin software bc it all started after the update.
- NY3Dbgmx7 days agoNew Spectator
I'm consistently experiencing this. How has this not been fixed yet? It's preventing us from playing and it's a recently introduced bug