There is a limit to how many frames you can have before the game glitches (see MCPE-152734). If the lag doesn't crash the game, the max amount of frames will glitch it.
Bump. Any update on this bug? It still occurs in the 1.21 (Tricky Trials) update.
Any update on this issue? Can this be fixed? Thanks.
Mods, can you update the affected versions to include versions up to and including the latest 1.20.81.1 release? Please and thank you 🙂.
@Sam You are talking about tryashtar's Image Map (https://github.com/tryashtar/image-map)? I use that to add maps to the game. It helped me understand the NBT format.
@Sam I tried with the Java edition and this does not happen there; but the Java edition has a limited color palette, which translates the custom maps into a downsampled image. I'm hoping this bug gets fixed soon; it's been 2 years.
This also occurs in the latest 1.20.72 release.
Thanks for updating this report last time mods.
@Dan Martin, have you found a workaround?
Can we update this to say that this bug affects the current releases?
Same issue occurred for me in Windows 10.
Also tested in Windows 11 and this occurs.
Using a Bedrock server and this occurs there too.
I'm thinking there is a limit that is hard-coded.
@Dan Martin Have you tried turning on the "Remove Texture Limit" in the video settings before you load your world? This allowed my world to load all my maps without any pink tiles being rendered.
I have to turn on "Remove Texture Limit" every time I launch Minecraft. My world works now, but I think it still crashes when I save and quit.
It is great to see that you are still checking in on this issue. Can you also update the affected versions to include the latest releases?