Timur Nazarov

Looks like you still have some file with malformed JSON in it in you resourcepacks directory. Could you remove everything from it and try again?

We think that this is likely fixed. We can not reproduce it on the latest snapshot. Can you still reproduce it?

Hello! Thanks for the report! Could you upgrade to the latest Nvidia driver and see if the issue still happens?

Hello! Thanks for the report! Have you tried upgrading your Mesa GPU driver to at least 25.1.7?

Thanks! We’ve removed the big texture from the pack and it still reproduces. The reason for the issue is not that the atlas is big but that water texture is 1x1, so mipmaps can not be used. That case is not properly handled in our code.
So I changed the bug title to reflect that. Feel free to comment if I am wrong.

Hey! Thanks for the report! Do you have an AMD GPU? A screenshot of your debug (F3) screen with hardware info on it would be nice. Thanks!

Could you provide a crash report?

It looks like the server you are connecting to is started in the demo mode.
You can disable the server demo mode by removing --demo from the server startup arguments.

Could you please provide a screenshot of the issue with the game version visible in the debug screen?
This looks like you might have started a wrong version.

Yes. Initially glass was cutout and not translucent. When it was not mipmapped not supporting translucency granted the best performance and supporting it did not have any benefits for Vanilla. So it was a Resource Pack feature request. After it became mipmapped, making it translucent instead of cutout actually makes the transitions between mimpap levels much smoother even for vanilla case. So it was implicitly retriaged and fixed.

This issue is not swept under the rug. We are very aware of it.
But no, we will not revert to the old rendering methods, because it would mean cancelling Vibrant Visuals for Java.
We plan to move forward from here, not backwards. This was partially addressed, but not fully solved, in 25w31a, and it will be fully solved at some point, when the rendering tech is in a better shape to do so. We are doing big refactoring now in preparation for Vibrant Visuals and we will get to fixing this.
We are also delivering other optimizations from time to time, slowly compensating for this. I the end, we expect the game to be faster than originally. It already is on the majority of devices that is not affected by this specific issue.

The issue is caused by looking at an oblique angle, not by the spyglass. It looks the same when you look from the same angle without spyglass and being close by.

Thanks! But could you try removing all resource packs again and sending us the log of that scenario?
This log shows an attempt of loading a bunch of broken packs and it would be nice to distinguish a bug in loading broken packs from a bug loading a purely vanilla game.

Hey! Thanks for the report! Could you attach client logs?
They are usually in `.minecraft/logs/latest.log`.

As far as I can see the resource pack you provided only has 1 layer for iron helmet. Am I wrong? If not, could you provide a resource pack that has 2 layers?

Hey! Sorry, but your laptop is below our minimum system requirements: https://www.minecraft.net/en-us/store/minecraft-deluxe-collection-pc?tabs=%7B%22details%22%3A1%7D#accordionv1-b6c8df09da-item-7739893325:~:text=Java%20System%20Requirements

It is on our priority list. Just needs a big refactor that did not fit into the previous release.

Hey! Thanks for the report! But could you present your logic in a bit more detail? We did not fully understand what exactly and why you want to change.

@Duckam We’ve closed this issue as Invalid since we do not accept modded game bug reports, but it is plausible that you would encounter the same issue without mods. If you can confirm that this happens on your device without mods, please tell us in a comment in the related MC-298908 issue.

Hey! Thanks for the report! Could you provide a screenshot of the F3 screen? We need your hardware details.