Build the attached setup, place a redstone block between the pistons and wait a few seconds. Alternatively kill yourself (/kill), fly away and come back etc. (same steps as to reproduce MC-177)
Actual outcome: Redstone block turns invisible.
Expected outcome: Redstone block stays visible.
Bug also exists for other blocks if you power them
Probably the same underlying issue as MC-177, but this particular issue can not be reproduced anymore because of changed piston behavior.
Related issues
is duplicated by
MC-5769
Weird piston BUD bug with redstone blocks
MC-5775
graphical glitch when using the redstone block with pistons
MC-5913
Redstone Block disappearing when pushed by piston
MC-5924
Blocks appearing to disappear
MC-5966
Redstone Glitch!
MC-6001
If a piston clock is running with a redstone block, the redstone block becomes invisible
MC-6124
invisible block
MC-6262
Redstone block piston-timer render error
MC-6715
redstone block disappearing
MC-7056
Redstone Block disapearing
MC-7210
New piston bug
MC-7769
Redstone Block disappears when put in a certain piston configuration.
MC-7979
piston glitch with redstone block
MC-8557
Redstone block vanishes if between two pistons
MC-8950
Disapearing blocks with pistons
MC-9475
redstoneblock disappears
MC-9705
Opposing pistons pushing into block that powers them make the block disappear
Attachments
Comments
migrated
migrated
you don't have to use /kill or fly away. you just have to wait or try again
migrated
confirmed, seen it in cubehamsters video http://youtu.be/gAAoKMU6dBw
migrated
Also notice that this bug doesn't need a redstone block, on the attached screenshot the diamond block becomes invisible, too, after a few seconds.
migrated
Here's a video of the behavior I made. Also note that the redstone does not appear to pulse.
migrated
Redstone not appearing to pulse is MC-5778
migrated
This seems to be much worse with 13w05b as the block now seems to disappear split seconds after starting the clock.
migrated
Confirmed.
migrated
I can no longer reproduce in 13w07a.
migrated
Still reproducible using the 4-piston clock with non-sticky pistons
migrated
Confirmed to still occur on 13w07a with the four piston setup if no repeater delays are added. Reopened.
EDIT:
Actually, also occurs with 2-piston setup without repeaters after waiting a few seconds.
migrated
Bug seems to be sort of resolved with sticky pistons but still happens on normal ones.
If you build the 4-piston setup with sticky pistons it looks like the block is pushed through all 4 positions in one single tick, which is very weird. But at least it doesn't turn permanently invisible.
Behavior for non-sticky piston seems to be unchanged.
migrated
Got it now. For me, there is both the redstone block and an invisible one that occupy the same space and experience z-fighting with each other. Upon destroying the redstone block, the invisible one continues around.
migrated
I filed MC-10677 for the new weird sticky piston behavior.
migrated
Unable to reproduce with 4 piston setup.
migrated
Confirmed fixed for both the 2 and 4 piston setup in MC 1.5. The pistons are now behaving properly and are moving slower
migrated
Thanks for the update. 😉