Sprinting sometimes causes FOV to toggle while walking at normal speed

I have never heard of this before, nor can I reproduce it. Do you have any mods installed? Does this still occur if you update your java (your version is very outdated)?

Duplicate of MC-1021.

Yes, I know it is a duplicate. I was giving a better description than "the FOV went boingoboingoboingo", and ways to replicate it.

I do use mods, but I tried replicating it using a plain vanilla client. I tried in various ways, it only seems to occur on internet servers. I could not replicate it at all in single player, or on a locally based server. I connected to a random vanilla server, and as soon as I found land, I was able to easily replicate it. You have to start sprinting within a split second of letting go of shift.

I recorded a video, to show the bug. It took a couple tries at the start, since my FPS was decreased a bit from recording. In the second half of the video, I was showing that you do move at normal walking speed by making a jump that is only possible while sprinting without the bug.

http://www.youtube.com/watch?v=K23sfntkVgU&feature=youtu.be

Swapped the duplication links in favor of the better description here

Also needs reopening 😉

Thanks. Done

> I know several different events trigger it, but I have found one way to faithfully recreate it after 1-3 tries.

I have found that the best way to reproduce it is to be chased by a person from the enemy team playing Scrap Mettle or Harb on the alpha.oc.tc PvP server 😞.

More seriously, it seems to occur more often if you double-click forward especially quickly, like you do when you really want to get away.

I met Dinnerbone online on oc.tc, and he said in chat that he was aware of the bug. I killed Dinnerbone as revenge for the sprint bug, of course! 😛

Also happens when flying right after sprinting

I can't reproduce it in 13w03a should I hold shift longer?

Nor can I, it appears to be indirectly fixed.

Edit: Never mind, I reproduced it in multiplayer fairly quickly. It appears to be slightly harder to replicate though, and stops in 1-3 seconds.

Can also confirm (you should update the affected versions). From my tests I have also seen that the quicker you tap the W key in succession, the more likely it is to occur.

Update affected versions to what version(s)?

As far as I know, the bug has been around since sprinting was implemented in Beta 1.8, I think I remember running into it a couple times then.

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Yes it is, I reproduced it immediately in a 1.5 vanilla server.

I'm not sure about the "immediately after sneaking" part of the description. I experience this bug extremely frequently, and I've never noticed a connection with sneaking. It's certainly happened when I haven't been sneaking.

As others have said, it does seem more likely to happen when you double-tap rapidly. It's an incredibly frustrating and long-standing issue with the game.

(Latency also seems to worsen it, but clearly cannot be the root cause of the bug.)

This has been around for a long while. Play on any Parkour server or other movement based games and it really becomes a problem. I can get it to happen almost every time when I am in creative mode. You start sprinting, stop sprinting, then quickly pick up sprinting again with very little time not sprinting in between. Reproduced in 1.5.2.

especially a problem on hypixel's minecraft server
if you play quakecraft and start sprinting and then the speed effect is applied afterwards it is the same:
you start changing between walking and sprinting, despite you are holding the w key
if you stop pressing any keys and start sprinting again it works

this bug is very annoying for jump parcours, too, if you need to sprint, but it will fail (sometimes)

temporary fix (doesn't work with 1.6.1 though)

Jesper that is not a fix. It's for 1.3.1

Edit: Oops sorry. But you should have posted the new thread here

oh, you're right, I changed it.

but you need to install a mod and it's not a fix
it just by-passes the problem by putting sprinting on a different key from walking...

hope a mod (tails) will see this again and pushes this issue again
it's really annoying and a lot of users I know are experiencing it (look at the list of duplications)
if everybody who experiences this issue would vote for it...

well I just drifted away

don't want anybody to feel obliged but please hurry a bit to include a fix in MC 1.6 or a small bug fix release after that

yeah, that's what I meant with 'temporary fix' but they definitely fix this bug. It exists for waay to long

Resolved with the addition of the sprint button.

The old way of double-tap sprinting is still there. So just because there is a sprint button, it doesn't mean that there isn't still a bug in the double-tap sprinting. The sprint button doesn't remove that bug.

nope, this is not fixed...
maybe works as intended but definitely not fixed

it is fixed as far as it is possible -> just switch to the sprint button
the double tap cannot get fixed because the issue is there by design
the server has to verify whether sprinting is correct now and checks the players movement (prevent hacking), the issue is caused by the latency between the server and the player
>>the player sends the attempt to sprint, but the server takes too long to answer-> client changes to moving normally/slowly again and sends this to the server
->now while the server sends the message that the client is allowed to sprint it gets the new message that client has started to move normally again
>>the client starts sprinting->the client gets the message: you have to move normally again
->the client moves normally again

maybe there is another solution to this, but the concept is there to prevent hacking as far as I know

possible solution: maybe you could send the client random hashes/codes that represent time stamps in a servers database (->the hashes need to be unique so that a modded client cannot fake them) so that he could verify that he makes the client moving normally although he has double tabbed the up button

There're a lot of similat tickets, can't get which is the main. But I can confirm this bug for 1.9 and 1.10. This should be re-opened.

Can someone please make a video reproducing this while that program is visible?: http://hot-virtual-keyboard.com

I had this happen to me while using the control key; no slabs were involved either. No steps to cleanly reproduce, but it isn't limited to double-tapping w. (No quality recording, but as a note to myself the low-quality log recording is 2016-07-19-1247-47 at 3:13:03)

The bug appears randomly, so reproducing it is time consuming. The bug appears when I use Ctrl too.

EDIT: I FIXED THE ISSUE BY CHANGING MY KEYBOARD FROM MY 3.0 USB PORT TO A 2.0 USB PORT. Maybe there was something wrong with the port I was using. Feels bad, since I only have 4 3.0 usb ports but now I seem to only have 3.

If it is the server why does it also happens in single player worlds? I mean there shouldn't be any latency in offline mode am I right? It's happening to me while playing singleplayer too in 1.12.2. Nothing seems to fix it, I have optifine and some shaders, no mods, I tried re-installing everything, playing vanilla, etc... nothing works.

It's worth to mention that this bug didn't affect my gameplay before updating my nVidia GeForce 1060 drivers to the version 385.69.

Hope this info helps.

My pc is quite good too, so it's not a "performance" thing either.

In case you need the info:
2TB storage.
16Gb RAM at 1600mhz
GTX 1060
i7 4790k at 4.0Ghz
everything is msi

I'll add a video when I can get it to replicate again, but I can confirm that this still happens in 1.13.1 and also affects sprint swimming.

I first encountered this a day or two ago in version 1.13.1. Today I replicated it and captured my footage. I can't replicate it in singleplayer. On my friends private server, I tried replicating this without the glowing effect before my first comment and wasn't able to get it which was confusing. After digging through other duplicates of this, I discovered https://bugs.mojang.com/browse/MC-111031 and realized that I had the glowing effect when I first found this bug. In my video below I show joining a server, applying the glowing effect, and my method of replication which is to quickly tap ctrl, rather than holding it or using w. The rubberbanding will subside after a while and return to walking, but seems to last longer when going faster. Holding ctrl initially or during the rubberbanding will result in normal sprinting. About 1/3 of the way through the video I remembered to turn on the virtual keyboard as requested by Helper Fabian.

Java Edition 1.13.1, Windows 10 64bit, Intel i7-7700 3.6GHz, Nvidia GTX980 

https://youtu.be/AAnhtiIhNFM 

For me the issue is reproducible when I am traveling exactly at (90.0/y) in the F3 display on a multiplayer server in the nether at y=32. the moment I am not traveling at 90.0 the glitch stops, and when I enter 90.0 my fov toggles and I travel at walking pace. the only way I have found to move at sprinting speed while holding the 90.0 heading is to strafe left and right.

Minecraft 1.13.1

Java:1.9.0_51 64bit

CPU: 8x Intel(R) Kenor (R) CP E3-1241 v3 @ 3.5GHz

Display: 1600:900 (NVIDIA Corporation) GeForce GT 740/PCIe/SE2 4.6.0 NVIDIA 388.13

So you mean y=32, in the nether, first "facing" angle 90? I can't reproduce it with that.

Hello,

I found a way to reproduce it easily and it happens everytime. 

To reproduce the sprint bug, on a game server (happens in Hypixel in the Lobby)

Press W W W (holding the last W), pressing the keys very quickly.  For some reason pressing W three times consequetively causes the screen to get stuck zooming in and out.

My config: Minecraft 1.11.2, OptiFine_1.11.2_HD_U_C7, No other mods. Keyboard - Razer chroma.

Please use the preview button to check if your comment looks like you want and only then send it. You just caused 180 mails to be sent.
Also, you're playing with a modified client on a modified server. Please make sure you don't report bugs here, confirm them for a version or similar, unless you can reproduce them in an unmodified game.

I removed optifine, and the same happens in vanillia Minecraft 1.11.2.  Pressing w three times quickly triggers the sprint zoom in/out bug.  Tested in Hypixel and Mc Central.

And what about unmodified servers? Like Singleplayer or one you run yourself (minecraft.net/download/server)?

Confirmed in Vanilla, Singleplayer. Triple W often causes this bug.
(That's also why I've been unable to reproduce it before, I never use double W to sprint. If that's the only way to cause it, double W to sprint could just be ignored, it behaves weirdly in many other ways anyway, is unreliable and can make you accidentally sprint sometimes.)

I can say that it can also happen with control, at least on a server where I have a moderately-high latency connection on. It's not consistently reproducible, though. I'll see if I can find a log video and also check the ping I had.

I'm not sure if it has already been mentioned, but turning off Dynamic FOV in the options, video settings, clears up the issue for me instantly.  But it is a compromise as I'm quite fond of Dynamic FOV.

That's an Optifine option. This bugtracker is only for Vanilla Minecraft. Also, that's not a fix, it just permanently stays in one FOV.

I got the same issue. Playing is nearly impossible. I don't know... I did not noticed last week when playing, but today... the switching of FoV is akward.
-> Multiplayer (Vanilla, no mods used)
-> Version 1.13.2

I can probably smoothen it while changing options a bit, but it's still... there. 😞

 Please see reference here: https://youtu.be/t7eZaWvN5BE

Since there's no support to this bug, i beg someone who had it too to help me telling WHAT DID YOU DO to fix it. I have only 2 worlds on hardcore and both are having this bug, and it's full-time, sprinting is normal but walking is bugged nonstop, i can't play literally.
It's vanilla btw, no mods, not even optifine\forge, nothing.

I tried to tweak vid conf, FOV, GUI, tried to update version, downgrade version (between 1.14.1 and 1.14.2), bug still there. I don't know what to do. Please, i'm begging.

Use Ctrl for sprinting. If that doesn't help, Try Optifine, it has an option to disable FOV widening.
Also, you shouldn't downgrade while using the same .minecraft folder. It probably works fine between 1.14.2 and 1.14.1, but between other versions it can cause crashes or other issues.

I'm having this problem on the latest version of Minecraft, no matter what I do

Here's the reference: https://youtu.be/az5aLV2w4f0

I still have this issue on 1.14.4 it’s most noticeable when you have the effect glowing and trying to run double tapping the W key

We just encountered this problem (Minecraft Java Edition 1.15.2, Windows 10, NVIDEA GTX 1650). It turned out not to be a Minecraft bug, but a simple keyboard configuration accident. Were were using a gaming keyboard (Ducky Shine 3) where you can set the delay and repeat rate of letter keys using the Fn and F1-F8 function keys, and the repeat rate was set unusually high. Minecraft exhibits exactly the symptoms described in this issue if the keyboard used has an unusually high keypress repeat rate set. Use a normal text editor and hold a letter key and judge if the key's delay and repeat rate are normal. If not, make sure they are normal before using the keyboard with Minecraft. You may have to consult the keyboard's manual or check your operating system's keyboard configuration settings.

Thank you @Markus Kuhn, my kids had been playing around with my Asus ROG Strix Flare keyboard and locked it to a higher refresh rate. Fn + Left Alt + F4 (God knows how they managed that combo exactly).

This issue is repeatable if you have a keyboard that can increase the repeat rate (usually Gaming keyboards). And you'll quickly notice that when you hold a key down in Notepad etc, your repeat rate is very fast.

See atached GIF for evidence:

[FoV-Issue|https://i.imgur.com/8fsNrdh.gifv]

@unknown That's not even Java edition. This is the Minecraft java edition bug tracker.

Fabian it's the same issue across platforms.

Case and point:

Java: https://i.imgur.com/l29cNyP.gifv
Windows: https://i.imgur.com/8fsNrdh.gifv

Doesn't matter, it's completely separate code. If the MCBE devs messed up the same way, that's just a coincidence. Fixing this bug in one game doesn't automatically fix it in another. The reports can be marked as related, but that's it.
Also, please check before sending a comment, because every edit sends a mail.

please check if affects 1.16 release candidate 1

Can confirm in 20w48a.

Can confirm in 20w51a.

I was about to upload that

Can confirm in 1.19.

Can confirm in 1.19.2

Can confirm on 1.20.1.

Why is 1.7 listed under fix versions?

Because a fix attempt was made in that version.