mojira.dev
MCPE-31800

Water & lava do not extinguish fire and cause graphical glitches

(Affects 1.2.14.2, don’t know why version isn’t listed) While I was testing out the new features in the new build, I stumbled upon a weird chunk glitch. I don’t know if it’s a one time occurrence.

Linked issues

MCPE-31818 Visual Texture Bug Resolved MCPE-31822 Super chunk rendering bugs Resolved MCPE-31839 Severe graphical glitches Resolved MCPE-31853 Giant Lava Bug .. not an insect.. its a bug in the game Resolved MCPE-31904 The block of lava has a bug Resolved

Attachments

Comments 14

Joseph De Jesus

I saw the same and it was one of the fishes.

device: Lenovo vibe K5 note
android 6.0
GPU: Mali T860

Added video with reproduction of the issue in a flat world

[media]

.
A possible cause is fire not being extinguished when in lava or water.

Attached image:

[media]


To help differentiate issues caused by other graphical glitches.

For graphical glitches with fish please go to MCPE-31907.

This is also affected on the Xbox One version.

4 more comments

I couldnt get the glitch to start again but if i go in a world where these bugs happened the glitched rendering still happens.

David L Dibble

is there any idea as to when this might be fixed?  It's actually making it almost impossible to play in the nether.  You walk into the glitch, and you can't see around you, to see if your going to fall into lava, ghast, or if your going to break through a block with lava above.  

[media]
[Mojang] Mega_Spud (Jay)

Cleaning up old tickets: This ticket has not been updated recently (~1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

MythicBurritoz

Im aware this ticket is closed, but I am still experiencing this glitch in 1.16.0.61 beta. Have had this bug since roughly 1.2.

@unknown: This ticket was closed because we can no longer reproduce the problem in new worlds, and because the only reports of it still happening are in worlds from two years or more ago. It is likely that the bug damaged your world back then and it cannot be repaired at this point, especially if you've been regularly opening it in Beta versions for a while.

(Whenever possible, Mojang includes repair logic for damaged worlds when they issue a bug fix, but it's only practical to do this for regular releases, not Betas, Unfortunately, it's simply the nature of Beta versions that they can damage a world, even beyond repair in some cases. That's why you're warned to make backups of worlds you open in a Beta release, and to use Beta versions only for testing.)

FireLiz

(Unassigned)

109944

Confirmed

Windows

1.2.13.12, 1.2.14.2, 1.2.14.3, 1.6.0.6

Retrieved