In PC, redstone torches change state when the block they are attached to has a change in signal longer than 1 tick (except for when that change in state is caused by the redstone torch itself, i.e. a short-circuit). In PE however, torches can change state when the block they're attached to has a signal change of 1 tick. The video demonstrates two examples of this in both PE (MCW10) and PC.
https://www.youtube.com/watch?v=8vNeAsOgeyk
To fix: torches should ignore any change in signal to their attachment block that is exactly 1 game tick or shorter (50ms or shorter), and only change state when the change in signal is longer than 1 tick. That way, a pulse that is 1.5 ticks or 2 ticks will affect a the torch, but a pulse that is exactly 1 tick or shorter won't, which is how redstone torches in the PC edition work.
Edit: updated info, since redstone torches in the PC edition ignore any pulse that is 1 game tick or shorter and respond to any pulse longer than 1 tick, not just 1.5 ticks.
Linked issues
is duplicated by 1
Attachments
Comments 20
Great. This may explain issues about weird behavior of torches, e.g. MCPE-11906.
Great. This may explain issues about weird behavior of torches, e.g. MCPE-11906.
This is exactly what's going on. Those really compact and impossible clocks where two torches are on the same block only work because the 1-tick pulse created by one torch is short enough to change the state of the other torch.
This is exactly what's going on. Those really compact and impossible clocks where two torches are on the same block only work because the 1-tick pulse created by one torch is short enough to change the state of the other torch.
@unknown closed this issue as "Works As Intended" with no explanation why it's intended. I strongly disagree with that because it's certainly behaving differently from the PC version, and since redstone mechanics is a really complicated system, having two different mechanics would not make things better.
@unknown closed this issue as "Works As Intended" with no explanation why it's intended. I strongly disagree with that because it's certainly behaving differently from the PC version, and since redstone mechanics is a really complicated system, having two different mechanics would not make things better.
Someone please reopen the issue, or tell us why it's an intended difference. I just can't stand getting it simply ignored and then permanently forgotten. MCPE-11279 is another example which has been dismissed by @unknown for no apparent reason. There would be no point reporting bugs then.
Someone please reopen the issue, or tell us why it's an intended difference. I just can't stand getting it simply ignored and then permanently forgotten. MCPE-11279 is another example which has been dismissed by @unknown for no apparent reason. There would be no point reporting bugs then.
I agree with PHO. I clearly demonstrated in the YouTube video that there is a difference in how redstone torches work in PC and Pocket Edition, yet this issue is marked as "Works As Intended." If the intention is to get redstone working the same in PE as it does in PC, then this is certainly not working as intended, and is still a bug.
I agree with PHO. I clearly demonstrated in the YouTube video that there is a difference in how redstone torches work in PC and Pocket Edition, yet this issue is marked as "Works As Intended." If the intention is to get redstone working the same in PE as it does in PC, then this is certainly not working as intended, and is still a bug.
This bug still exists in 0.14.0, and it still does not work as intended.
This bug still exists in 0.14.0, and it still does not work as intended.
Attached an image
[media]showing a circuit to reproduce the issue without being affected by graphic update lag. The bottom half of it is an RS-NOR latch whose state can be toggled by button "R" and "S". The upper half is a 1-tick pulse generator with button "P".
Steps to reproduce:
Press the button "R".
Then press the button "P".
What I expected:
The state of RS-NOR latch does not change after pressing the button "P".
What actually happened:
The RS-NOR latch turned into a 1-tick clock, eternally changing its state.
Attached an image
[media]showing a circuit to reproduce the issue without being affected by graphic update lag. The bottom half of it is an RS-NOR latch whose state can be toggled by button "R" and "S". The upper half is a 1-tick pulse generator with button "P".
Steps to reproduce:
Press the button "R".
Then press the button "P".
What I expected:
The state of RS-NOR latch does not change after pressing the button "P".
What actually happened:
The RS-NOR latch turned into a 1-tick clock, eternally changing its state.
Reopened.
This issue was marked by developers as "As designed"
Both teams (Stockholm and Redmond) are talking about this issue, so they are aware of the problem and they will try to fix it without breaking anything else. For now it is working as intended so it does not break other Redstone functions.
This issue was marked by developers as "As designed"
Both teams (Stockholm and Redmond) are talking about this issue, so they are aware of the problem and they will try to fix it without breaking anything else. For now it is working as intended so it does not break other Redstone functions.
Well... okay then. Thanks for your information.
Well... okay then. Thanks for your information.