Hello!
My issue arises when holding a movement key for more than 1 second. Any combination of WASD (with or without sprinting) will force my character to halt in place for about 0.25 seconds, then the movement signal begins to cycle from pressed to unpressed movement every 0.25 seconds.
To put it another way: if I were to simply hold down the 'W' key, my character would walk forward for 1 second, stop for 0.25 seconds, then sprint for 0.25 seconds, halt for 0.25 seconds, and repeat. During the sprinting period, the fov changes and dirt particles are kicked up, but my overall movement speed is much lower than if I were walking normally.
I have tried a number of solutions from reinstalling the launcher all the way to reformating my hard drive with a fresh install of windows. The issue does not seem to pertain to system performance. None of my other games, or programs suffer from this problem.
My search for solutions yielded only one result: a ticket on this forum with ID MC-118615.
Their ticket is labled RESOLVED, I'd like to know what steps they took to fix it.
Thank you.
Comments 3
Hi. Through trial and error I deduced the problem was coming from my keyboard. I'm still not sure why. I switched to using a different keyboard and the problem instantly went away. I've been fiddling with different settings in control panel using the old keyboard but I can't figure it out. Anyway this doesn't seem to be a Minecraft bug.
If anyone else is experiencing these problems try changing your input (a steam controller also worked fine).
I have a fix for anyone who doesn't want to use a different keyboard or a different means of input. It is true that the source of the problem is not based in Minecraft but in your keyboard, and it probably arose after inputting key presses that altered how your keys function when pressed (the specific key presses and what they specifically do are unknown to me).
Solution is to just unplug and plug back in your keyboard. Do this and your movement will return to normal.
Please provide a small video with the debug screen enabled (hit the
F3key) demonstrating the issue.