mojira.dev

Ceresjanin123

Assigned

No issues.

Reported

View all
MC-307373 Rare intermittent issue causing extreme performance degradation when entities are visible Community Consensus MCL-26548 The Minecraft Launcher doesn't use the correct JVM arguments for modified installations Invalid WEB-8498 Some reports don't show up when filtering for my open requests Fixed MC-306528 When returning to the world list after failing to recreate a world, all worlds now display the default icon until the world list is reopened Confirmed MC-305177 Kelp flickers severely at high render distance Won't Fix MC-304362 RGSS breaks permanently when toggling hardware anisotropic filtering Fixed MC-303702 Small gaps still appear in item models Confirmed MC-303698 Chunk loading now causes severe frametime spikes Confirmed MC-303695 Reloading textures while the game is tick frozen causes animated textures to render incorrectly Fixed MC-303484 Nether portal animation causes beacon beams to render through fog Confirmed

Comments

Can confirm. And personally I prefer Vulkan’s mipmapping

What is your hardware and operating system? (alternatively just send a screenshot with the F3 menu open)

The request is listed now so this report should be closed now.
Regardless it appears that the real issue is sorting because the reports are not correctly sorted by “newest first”. Should I report that instead?

[media: obraz-20260325-102849.png]

Your method does not work. The portal regenerates partially below the void, leaving it broken.

I cannot reproduce on Intel B580

This is not snowy grass but snow layers flickering. It’s caused by geometry (snow layers are only 2 pixels tall), not the texture so anisotropic filtering has no effect.

The only way to fix this is either TAA or MSAA or LOD’s and I doubt Mojang is willing to add any of these.

This is the most puzzling “won’t fix” resolution I have ever seen.

First of all, this issue is way more common and serious than mojang devs might have realized
- Tick freeze is a commonly used command.
- Reloading textures is one of the more common actions a player might do during tick freeze. As tick freeze is an useful tool for comparing performance between graphics settings (which can also trigger texture reload), or small differences between textures.
- The visual impact is severe, any time this issue is triggered the user will most definitely notice it right away.

Second of all the fix to this issue is seemeingly trivial
- Upon reloading textures step the animations (and only the animations) by two ticks (one tick doesn’t work)
- Or, make animated textures unaffected by tick freeze entirely (less ideal)

[media]
[media]
[media]
[media]

On Intel GPU’s loading this resource pack causes this issue to happen, regardless of if anisotropic filtering is enabled or not

[media]

Nope.

Also please take a look at MC-303452 which skipped triage due to the same request.

[media: 2025-10-27_12.51.30.png]

Here you go

[media: 2025-10-24_12.26.21.png]

[media]
[media]
[media]
[media]
Load more comments