Pistons/blocks turn white for a split second when pushing/pulling blocks

Affects 1.16.100.59. This is a render dragon only bug

Render Dragon was disabled in 1.16.100.60 so it's not going affect that version.

can confirm for 1.16.200.51 on Windows 10

Affects 1.16.200.55

affects 1.17.20.20

Affects 1.16.210.50

This bug affects Windows 10 release in 1.16.200. I was not able to experience it until now since I do not have XBox or beta. Now that I'm seeing it, I think it should be escalated as an accessibility issue because it could trigger siezures. (Compare MC-11519)

Relates to MCPE-111632 might be similar.

Still present in 1.16.210.56

And yes. This is 100% renderdragon, but I'm not sure if it's a bug! Since, probably, many have noticed that when loading chunks / fast construction in blocks, they become white for a second, partially loading (smoothly). This also works with a piston (like a quick installation of new blocks.

Please fix this. This is legitimately an accessibility issue for people with certain types of epilepsy or similar problems... This and the weird chunk loading visuals both have me scared to play right now.

@Junior Apanishile very likely unrelated. While MCPE-111632 mentions not rendering, this is different / it renders but incorrectly

This issue does not affect chests and trapped chests.

1.16.210 too

I tried to fix this by changing the texture assigned to "movingblock" in blocks.json, but it made no difference. Strangely, the blocks.json assigns the Update Block texture to moving blocks, but that does not seem to be effective because standalone moving blocks also appear solid white. (You can get standalone moving blocks in creative mode by cloning blocks being pushed by pistons, related to MCPE-111632.) That makes me think the actual texture being used is a hard-coded solid white.

For reference, here is a visualization of moving blocks made by cloning a sticky-piston pushing a block on a fast clock circuit on 8 successive ticks:

Affects 1.17.2

I believe this is fixed in the latest beta so this bug should be fixed in the next update of the game.

This has been fixed, however, blocks now flash brighter instead of white when pushed by a piston, affecting 1.17.30. Would that count as this bug or as a new one?

There's a bug where the block movement animation is, in most of the times, laggy or no animation at all.

Anyone can give me a reference to an open bug report about it? I can't seem to find it. they're all either duplicates or invalid.

Moving blocks flashing brighter after this fix is tracked at MCPE-136928.

Henry Markle: are the reports you're talking about resolved as a duplicates of this one, or another? Please give some examples.

I am at the latest available version on Windows 11. I can confirm that piston animation is laggy if there's animation at all.

I have a very decent computer with a dedicated graphics card and this issue is still very clearly present. I am unaware of an issue ticket open for this one.

Some additional information: The piston itself is fine. It's the block that has no animation.

It is unaffected by game settings such as vsync, fps/max fps, render distance.

Here are 2 recordings of a 2x2 piston door: one with iron blocks, the other with chests.

The result we're getting is that you can't see the iron blocks moving at all; they just pop from one place to an other, while the chests are at a slightly better position, but still pretty bad.

The expected result is that you would be able to see the blocks smoothly transitioning from one place to an other.

GoldenHelmet: Does the issue I mentioned above need its own ticket? I prefer a mod to do it, because the issue has been reported many times, as far as I am aware, but most if not all were closed for various reasons, like being a duplicate for an unrelated bug. It has been around forever and it undermines the player's experience when working with redstone, yet it remains unresolved.

Finally as for your question, MCPE-127932 has been marked as a duplicate to this very ticket, despite that one talking about a completely different issue. It has been given injustice leaving a big issue everyone complaining about unresolved.

It is the issue that I was talking about in the previous comments. I hope this helps.

Henry Markle: thanks for following up on this issue. I have started looking into it and saw that you made a new report for the piston animation (MCPE-155987), which I have updated an confirmed. The moving block animation should be tracked as a separate issue from the piston animation, but I'm still determining whether it needs a new report or we should reopen MCPE-118444/MCPE-118447. I'll update this comment when ready.

MCPE-118444 has been reopened (oops). Didn't realize that happens automatically.