Having FOV over 100 and sleeping in bed will cause you to look inside your head
When setting the FOV slider above 100 (I use quake pro), and sleeping in a bed, you will see the inside of your head.
How to reproduce: Turn FOV to 100 or higher then sleep in a bed.
Linked Issues
is duplicated by7
Created Issue:
Having FOV over 100 and sleeping in bed will cause you to look inside your head
When setting the FOV slider to 100 or above (I use quake pro), and sleeping in a bed, you will see the inside of your head.
When setting the FOV slider to 100 or above (I use quake pro), and sleeping in a bed, you will see the inside of your head.
Reproduce: Turn FOV to 100 or higher then sleep in a bed.
When setting the FOV slider to 100 or above (I use quake pro), and sleeping in a bed, you will see the inside of your head.
Reproduce: Turn FOV to 100 or higher then sleep in a bed.When setting the FOV slider to 100 or above (I use quake pro), and sleeping in a bed, you will see the inside of your head.
How to reproduce: Turn FOV to 100 or higher then sleep in a bed.
When setting the FOV slider
to 100 orabove (I use quake pro), and sleeping in a bed, you will see the inside of your head.How to reproduce: Turn FOV to 100 or higher then sleep in a bed.
When setting the FOV slider above 100 (I use quake pro), and sleeping in a bed, you will see the inside of your head.
How to reproduce: Turn FOV to 100 or higher then sleep in a bed.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Duplicate of MC-19, please use the search function to see if your bug has already been submitted. Currently over 53% of tickets are being closed as duplicate.
What is your FOV set to? This sounds like a duplicate of MC-19.
Fixed in 14w08a (1.8 Snapshot). MC-19


Has to be >100 not >= 100 as the subject says
I'm able to reproduce the bug with any FOV setting at or above 100. (Does not appear at or below 99.)
Is this still a concern on Minecraft 1.4.4 Pre-Release? If so, please update the version affected.
TnT: If it wasn't, wouldn't this bug be marked as solved?
Christoffer - Not necessarily. Many bugs can be related to a different bug fix which had the pleasant side affect of fixing this bug as well and this ticket not closed off. Please keep track of the tickets you submit and update them accordingly for the new MC versions released. It helps immensely when Mojang is looking for relevant bugs to fix. As well, there are many Jira filters used that help track down which bugs go against which versions, so keeping the bug reports up to date is a huge help.
TNT: Ah, I understand, Thanks for explaining it to me! I updated the version, because it sure existed in 1.4.4 aswell
Can you replicate this issue in latest version of the minecraft? If so, can you please update the ticket?
Can we get a confirmation of whether this happens in 13w10a and an update to the affected versions?
I got the same thing right now running the 1.5.1 pre-release.
I have my FOV on 85, but got a beacon with speed II, so my FOV changes by that.
Now when i sleep i will look in my own head.
Bug still exists in 1.5.1 If you have the FOV at anything over Normal, it will rapidly switch between inside your head and outside your head for a couple of seconds. At a FOV of 100 it stays inside permenately.
Is this still a concern in the latest Minecraft version 14w02c? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
I've just tested and this is still happening in version 14w02c.
Still happening in 1.7.4, im disapointed in how long its taking to fix this. Someone here is not doing there job.
*their. fixed
Fixed in 08a
Fix confirmed.
not fixed! look at image
my Fov is at normal and it is at the update of 19w11b
Confirmed, this exists again, but not at "normal" FOV, only at "quake pro" and only when clicking on the bed from some angles. Since this is such an old report, it's usually handled by creating a new report and marking it as "cloning" the old report (I also don't know why). Can you create the new report, please?