Bug Description

the water seems to not render in normally, it disappears and reapears like crazy! whenever i look at water my game freezes and when i look away or when i fly away from the water it unfreezes

Reproduction Steps

this happens whenever i join a random world and i look at the water, everything is normal on a superflat world, but even there if i put a water source block my game freezes

Log File

if the log file will be needed i will post it in the comments

Crash Report

the game didn't crash

Share the latest.log and crash report. Even if the game didn't crash, you can force it to crash by holding F3+C. The crash report has information that is not in the latest.log

I tired the latest nighty "Add caching for region draw batches" build to see how much performance improvements and saw these broken things
Only happening on this build not with others builds like combine draw commands

Same behaviour on latest nighty build btw I'm a pojav user

Pojav Launcher is not supported. Sodium puts a giant warning message on your screen explaining this, why do you insist on reporting bugs to us that we can do nothing about?

Pojav Launcher is not supported. Sodium puts a giant warning message on your screen explaining this, why do you insist on reporting bugs to us that we can do nothing about?

I mean this bug happening In pc as well

Well there is no information available to us on how to fix it, and the original poster neglected to use the issue template correctly.

I mean this bug happening In pc as well

Please, provide a screenshot of the F3 screen and your graphics driver version if you can reproduce the bug on PC.

Pojav Launcher is not supported. Sodium puts a giant warning message on your screen explaining this, why do you insist on reporting bugs to us that we can do nothing about?

I mean this bug happening In pc as well

I close it
PojavLauncherTeam/PojavLauncher#6620
If also happen in PC

After some sleuthing, it seems the original poster was using PojavLauncher, and had a device which was affected by the issue which this commit fixed a while ago.

The most recent comments were unrelated to this, and were an issue caused by a bug that existed briefly on trunk yesterday which got fixed this morning with #3018.