Android Nvidia Shield Tablet K1
MCPE 0.15.0
Attachments
Comments
migrated
migrated
PlantSeed
This screenshot explain everything.
migrated
Pretty interesting behaviour..
migrated
Pretty interesting behaviour..
migrated
Pretty interesting behaviour..
migrated
Likely works as intended, pistons cannot be 0 ticked in pe.
migrated
Likely works as intended, pistons cannot be 0 ticked in pe.
migrated
Likely works as intended, pistons cannot be 0 ticked in pe.
PlantSeed
If it was intended, it doesn't make sense.
migrated
I think in the second pic between the andesite, its an invisible block. Can you check Drew?
migrated
I think in the second pic between the andesite, its an invisible block. Can you check Drew?
migrated
I think in the second pic between the andesite, its an invisible block. Can you check Drew?
PlantSeed
The screenshot was attached by me, and there is no invisible block.
migrated
Confirmed in 0.15.0
The screenshot shown below is a falling-edge detector which should emit 2 ticks pulse on a falling-edge and shouldn't emit a pulse on a rising edge.
The repeater is set to 2 ticks delay. On a rising edge the piston should take 1.5 redstone ticks to extend so there should be no pulse emitted from the output. On a falling edge the piston should retract instantly (0 redstone ticks) so there should be 2 ticks pulse from the output.
However in 0.15.0, pistons take 2.5 or 3 redstone ticks to extend and 1 or 1.5 redstone ticks to retract, so the said circuit instead works as a 1 tick dual-edge detector.
migrated
Confirmed in 0.15.0
The screenshot shown below is a falling-edge detector which should emit 2 ticks pulse on a falling-edge and shouldn't emit a pulse on a rising edge.
The repeater is set to 2 ticks delay. On a rising edge the piston should take 1.5 redstone ticks to extend so there should be no pulse emitted from the output. On a falling edge the piston should retract instantly (0 redstone ticks) so there should be 2 ticks pulse from the output.
However in 0.15.0, pistons take 2.5 or 3 redstone ticks to extend and 1 or 1.5 redstone ticks to retract, so the said circuit instead works as a 1 tick dual-edge detector.
migrated
Confirmed in 0.15.0
The screenshot shown below is a falling-edge detector which should emit 2 ticks pulse on a falling-edge and shouldn't emit a pulse on a rising edge.
The repeater is set to 2 ticks delay. On a rising edge the piston should take 1.5 redstone ticks to extend so there should be no pulse emitted from the output. On a falling edge the piston should retract instantly (0 redstone ticks) so there should be 2 ticks pulse from the output.
However in 0.15.0, pistons take 2.5 or 3 redstone ticks to extend and 1 or 1.5 redstone ticks to retract, so the said circuit instead works as a 1 tick dual-edge detector.
migrated
I asked developers about this issue, and it turned out that there were 3 different bugs in it, namely @unknown's first screenshot (slime block doesn't move the piston), @unknown's second and third screenshot (pistons that should extend can fail to do so), and my fourth screenshot (piston's movement is significantly slower compared to the PC edition).
So I'm going to split it into 3 separate tickets. Since @unknown's original report is so vague that I have no idea what they really meant, I will close it as Incomplete.
migrated
I asked developers about this issue, and it turned out that there were 3 different bugs in it, namely @unknown's first screenshot (slime block doesn't move the piston), @unknown's second and third screenshot (pistons that should extend can fail to do so), and my fourth screenshot (piston's movement is significantly slower compared to the PC edition).
So I'm going to split it into 3 separate tickets. Since @unknown's original report is so vague that I have no idea what they really meant, I will close it as Incomplete.
migrated
I asked developers about this issue, and it turned out that there were 3 different bugs in it, namely @unknown's first screenshot (slime block doesn't move the piston), @unknown's second and third screenshot (pistons that should extend can fail to do so), and my fourth screenshot (piston's movement is significantly slower compared to the PC edition).
So I'm going to split it into 3 separate tickets. Since @unknown's original report is so vague that I have no idea what they really meant, I will close it as Incomplete.
migrated
Done:
I set the reporter of the first two issues to @unknown because it's them that reported those issues.
migrated
Done:
I set the reporter of the first two issues to @unknown because it's them that reported those issues.
migrated
Done:
I set the reporter of the first two issues to @unknown because it's them that reported those issues.
PlantSeed
Thanks @unknown, I'll update the affected version to both of these issues, when it still occur in future versions.
migrated
Alright, Alright... The problem is when you try to build a fast clock, the piston can't keep up with the ticks
migrated
Alright, Alright... The problem is when you try to build a fast clock, the piston can't keep up with the ticks
migrated
Alright, Alright... The problem is when you try to build a fast clock, the piston can't keep up with the ticks