[MC-92250] You can see through blocks using high FOV values and speed

The Bug:

You can see through blocks using high FOV values and speed.

Steps to Reproduce:

Summon a solid wall of blocks nearby and teleport yourself up against it by using the commands provided below.
```
/fill ~6 ~ ~6 ~6 ~4 ~-6 minecraft:stone
```
```
/tp @s ~5 ~ ~ 0 0
```
Navigate to your video settings and change your FOV to "Quake Pro".
Give yourself the speed effect by using the command provided below.
```
/effect give @s minecraft:speed 100 3 true
```
Look closely at the solid wall you're standing against.
Take note as to whether or not you can see through blocks using high FOV values and speed.

Observed Behavior:

You can see through blocks.

Expected Behavior:

You would not be able to see through blocks.

Related issues

is duplicated by

MC-12568 Player can see through blocks with very high FOV

MC-95355 Speed + high FOV creates viex glitches, like X-Ray

MC-105871 FOV Wallhack.

MC-123413 See through walls

MC-167747 Third person with PRO fov causes x-ray vision.

MC-169280 Xray glitch in 3rd person mode with speed

MC-171889 X-ray effect when having 255 speed level

MC-182725 FOV glitch

MC-189553 High FOV + Speed + 3rd Person - See through walls glitch.

MC-197091 High FoV (using enchantments and effects) causes X-ray effect

MC-204833 Blocks becoming transparent in 3d person

MC-217026 3rd Person Quake Pro FOV view bobbing Xray issue.

MC-221003 you can see trough blocks with high FOV

MC-247977 3rd Person Wall-Clipping Glitch

MC-273080 speed effect causes the camera to clip

relates to

MC-273908 You can see through blocks when sprint jumping into a bed next to a wall

MC-8684 You can see through blocks when using widescreen resolutions

MC-88677 High FoV (manually changed in options.txt) causes X-ray effect

Attachments

Comments

migrated 2015-11-06T19:01:59Z

[media][media]

bemoty 2017-08-08T17:41:12Z

Duplicate of MC-10755.

[Mod] Neko 2017-08-08T18:53:52Z

@unknown, speed 4 is supported.

bemoty 2017-08-08T19:42:43Z

@unknown Oops? Why is MC-12568 resolved as a duplicate of MC-10755 then? Speed 3 is supported too then.

[Mod] Neko 2017-08-08T19:52:25Z

Fixed, thanks.

bemoty 2017-08-13T20:16:48Z

Can confirm for MC 1.12.1, this already works with speed 3.

RedCMD 2018-02-06T22:53:57Z

can confirm for 1.12.2, but with Quake-PRO FOV + Speed 2 + sprinting in survial

FaRo1 2018-05-17T18:44:07Z

This also happens in third person view without speed effect. But because it's easier to reproduce with speed, I'm not going to change the report.

migrated 2018-08-27T15:59:05Z

Confirmed for 1.13.1.

migrated 2018-08-27T17:00:14Z

~~Can I be the reporter of this issue, please?~~
Thanks. 🙂

migrated 2020-06-07T12:29:46Z

Confirmed for 1.16 Pre-release 2.

migrated 2020-07-03T13:10:22Z

confirmed for 20w27a

pulpetti 2020-08-05T13:32:55Z

In 1.16.2 Pre-1

migrated 2020-08-19T23:53:45Z

Confirmed for 1.16.2

UserTeemu 2020-10-14T12:04:53Z

Confirmed for 1.16.3

Sebexan 2020-10-23T18:35:11Z

Present in 1.16.4 Pre-Release 2

Sebexan 2020-11-02T19:10:48Z

Present in 1.16.4

Sebexan 2020-11-04T19:32:28Z

Present in 20w45a

Sebexan 2020-11-11T17:15:57Z

Present in 20w46a

UserTeemu 2020-11-20T21:56:57Z

I think this issue is related to near clipping in rendering. At least in third person, it seems like this issue can be prevented if all block faces are rendered more than 0.05 blocks (the near clipping plane value) away from the camera.

I tested my theory about near clipping with a mod that changes the near clipping value to 0.03 from the original value (0.05). And yes, lowering that value decreased the area on screen, where you can see through blocks. That happened with all perspectives.
However lowering the value shouldn't be the fix, since it can break a lot of other things.

Sebexan 2020-11-27T13:51:02Z

Present in 20w48a

migrated 2020-11-29T00:01:20Z

Works for me too! Works better on some walls than others.

Sebexan 2020-12-21T15:11:58Z

in 20w51a

Sebexan 2021-01-25T13:23:30Z

I can confirm for
1.16.5 and 21w03a

Sebexan 2021-02-05T13:47:41Z

I can confirm for 21w05b

Sebexan 2021-02-11T15:40:30Z

in 21w06a

Sebexan 2021-02-17T19:17:34Z

I can confirm for 21w07a

Sebexan 2021-02-24T20:09:45Z

I can confirm for 21w08a

Sebexan 2021-03-11T13:27:51Z

I can confirm for 21w10a

Sebexan 2021-03-18T10:22:31Z

I can confirm for 21w11a

Sebexan 2021-03-31T21:05:44Z

I can confirm for 21w13a

Sebexan 2021-04-07T15:34:10Z

I can confirm for 21w14a

Sebexan 2021-04-14T18:26:24Z

I can confirm for 21w15a

Sebexan 2021-04-21T18:59:20Z

I can confirm for 21w16a

Sebexan 2021-04-28T15:13:14Z

I can confirm for 21w17a

Sebexan 2021-05-05T17:30:58Z

I can confirm for 21w18a

Sebexan 2021-05-12T13:46:14Z

I can confirm for 21w19a

Sebexan 2021-05-19T17:35:14Z

I can confirm for 21w20a

Sebexan 2021-05-27T14:11:26Z

I can confirm for 1.17 Pre-release 1

Sebexan 2021-05-31T17:32:33Z

I can confirm for 1.17 Pre-release 2

Sebexan 2021-06-08T18:32:58Z

I can confirm for 1.17

Avoma 2021-09-07T18:05:52Z

Can confirm in 1.17.1.

Avoma 2022-05-14T12:58:15Z

Can confirm in 1.18.2 and 22w19a.

migrated 2022-05-25T09:56:26Z

This is actually caused by generic.movement_speed being over a certain value, and is not specific to potion effects nor enchantments (MC-197091); they just modify said attribute.
Using /attribute, you can cause this too.

This can be fixed by clamping the FOV within a certain range, while not clamping the movement speed; Or by modifying how the world gets rendered on a wide screen to fix this (also fixing MC-8684).

FaRo1 2022-05-25T10:11:46Z

I think limiting FOV is a good idea regardless, but asymptotically, not with a hard cutoff point. And MC-8684 shows that also properly fixing the actual rendering issue would be good anyway.

Brain81505 2023-04-30T11:53:53Z

Can confirm in 23w17a