Dj
- DjSapsan
- djsapsan
- Europe/Kiev
- Yes
- No
MC-73713
Sorry for my English.
Issue appears totally unpredictable way - on different version and different environment (single- and multiplayer).
I make video with issue:https://www.youtube.com/watch?v=1TY_qIkdHCM (1.8.8 like 1.7.10)
https://www.youtube.com/watch?v=-1arts4kXDw (1.8.8 like 1.7.10)
https://youtu.be/IPGxZGcOX2s (1.5.2)I try describe issue (sorry for my English):
In singleplayer and some servers issue with 2 consecutive repeaters with delay 2 - serial impulse don't pass correctly. But in other server This problem does not exist.
But appears new issue: wrong work receiver (may my mistake, but it is unlikely, really don't my mistake). AND! Wrong work torches. In one situation torch turn off, in other situation torch not react. And similar behavior on version 1.5.2.
Sorry for my English, and i have a big request:
Treat this issue seriously, because this bug is impossible to make Redstone devices, pleaseSorry for my English.
Issue appears totally unpredictable way - on different version and different environment (single- and multiplayer).
I make video with issue:https://www.youtube.com/watch?v=1TY_qIkdHCM (1.8.8 like 1.7.10)
https://www.youtube.com/watch?v=-1arts4kXDw (1.8.8 like 1.7.10)
https://youtu.be/IPGxZGcOX2s (1.5.2)I try describe issue (sorry for my English):
In singleplayer and some servers issue with 2 consecutive repeaters with delay 2 - serial impulse don't pass correctly. But in other server This problem does not exist.
But appears new issue: wrong work receiver (may my mistake, but it is unlikely, really don't my mistake). And! Wrong work torches. In one situation torch turn off, in other situation torch not react. And similar behavior on version 1.5.2.
Sorry for my English, and i have a big request:
Treat this issue seriously, because this bug is impossible to make Redstone devices, please
Sorry for my English.
Issue appears totally unpredictable way - on different version and different environment (single- and multiplayer).
I make video with issue:https://www.youtube.com/watch?v=1TY_qIkdHCM
(1.8.8 like 1.7.10)https://www.youtube.com/watch?v=-1arts4kXDw(1.8.8 like 1.7.10)https://youtu.be/IPGxZGcOX2s(1.5.2)I try describe issue (sorry for my English):
In singleplayer and some servers issue with 2 consecutive repeaters with delay 2 - serial impulse don't pass correctly. But in other server This problem does not exist.
But appears new issue: wrong work receiver (may my mistake, but it is unlikely, really don't my mistake). And! Wrong work torches. In one situation torch turn off, in other situation torch not react. And similar behavior on version 1.5.2.Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugisimpossible to make Redstone devices, pleaseSorry for my English.
Issues appears totally unpredictable way - on different version and different environment (single- and multiplayer).
I'm made video with issue:https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, server spigot)
1:40: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse/
3:20: most stupid bug. One torch is blocking other WITHOUT physical contact! (different direction - the same result).
6:05: two consecutive repeaters can transmit through self impulse.
6:30: strange work transmitter and receiver. A few strange stuff (6:50, 8:02)(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05)
10:25 - 11:25: all bugs are the same, but 1:45 - different direction - different result (compare 3:20).(version 1.5.2, signleplayer)
12:45: most stupid bug. One torch is blocking other WITHOUT physical contact!(version 1.8.8, server bukkit)
13:34: most stupid bug. One torch is blocking other WITHOUT physical contact!
13:45: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 and 9:31)Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugs make impossible to make Redstone devices, please
different and indeterminately
Sorry for my English.
Issues appears totally unpredictable way - on different version and different environment (single- and multiplayer).
I'm made video with issue:https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, server spigot)
1:40: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse/
3:20: most stupid bug. One torch is blocking other WITHOUT physical contact! (different direction - the same result).
6:05: two consecutive repeaters can transmit through self impulse.
6:30: strange work transmitter and receiver. A few strange stuff (6:50, 8:02)(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05)
10:25 - 11:25: all bugs are the same, but 1:45 - different direction - different result (compare 3:20).(version 1.5.2, signleplayer)
12:45: most stupid bug. One torch is blocking other WITHOUT physical contact!(version 1.8.8, server bukkit)
13:34: most stupid bug. One torch is blocking other WITHOUT physical contact!
13:45: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 and 9:31)Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugs make impossible to make Redstone devices, pleaseSorry for my English.
Issues appears totally unpredictable way - on different version and different environment (single- and multiplayer).
I'm made video with issue:https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode (all impulses have 4 ticks):
(version 1.8.8, server spigot)
1:40: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
3:20: most stupid bug. One torch is blocking other WITHOUT physical contact! (different direction - the same result).
6:05: two consecutive repeaters can transmit through self impulse.
6:30: strange work transmitter and receiver. A few strange stuff (6:50, 8:02)(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05)
10:25 - 11:25: all bugs are the same, but 1:45 - different direction - different result (compare 3:20).(version 1.5.2, signleplayer)
12:45: most stupid bug. One torch is blocking other WITHOUT physical contact!(version 1.8.8, server bukkit)
13:34: most stupid bug. One torch is blocking other WITHOUT physical contact!
13:45: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 and 9:31)Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugs make impossible to make Redstone devices, please
Sorry for my English.
Issues appears totally unpredictable way - on different version and different environment (single- and multiplayer).
I'm made video with issue:https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode (all impulses have 4 ticks):
(version 1.8.8, server spigot)
1:40: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
3:20: most stupid bug. One torch is blocking other torch WITHOUT physical contact! (different direction - the same result).
6:05: two consecutive repeaters can transmit through self impulse.
6:30: strange work transmitter and receiver. A few strange stuff (6:50, 8:02)(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05)
10:25 - 11:25: all bugs are the same, but 1:45 - different direction - different result (compare 3:20).(version 1.5.2, signleplayer)
12:45: most stupid bug. One torch is blocking other WITHOUT physical contact!(version 1.8.8, server bukkit)
13:34: most stupid bug. One torch is blocking other WITHOUT physical contact!
13:45: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 and 9:31)Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugs make impossible to make Redstone devices, please
Sorry for my English.
Issues appears totally unpredictable way - on different version and different environment (single- and multiplayer).
I'm made video with issue:https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode (all impulses have 4 ticks):
(version 1.8.8, server spigot)
1:40: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
3:20: most stupid bug. One torch is blocking other torch WITHOUT physical contact! (different direction - the same result).
6:05: two consecutive repeaters can transmit through self impulse.
6:30: strange work transmitter and receiver. A few strange stuff (6:50, 8:02)(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05)
10:25 - 11:25: all bugs are the same, but 1:45 - different direction - different result (compare 3:20).(version 1.5.2, signleplayer)
12:45: most stupid bug. One torch is blocking other WITHOUT physical contact!(version 1.8.8, server bukkit)
13:34: most stupid bug. One torch is blocking other WITHOUT physical contact!
13:45: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 and 9:31)Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugs make impossible to make Redstone devices, pleaseSorry for my English.
Issues appears totally unpredictable way - on different version and different environment (single- and multiplayer).
I'm made video with issue:https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode (all impulses have 4 ticks):
(version 1.8.8, server spigot)
1:40: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
3:20: most stupid bug. One torch is blocking other torch WITHOUT physical contact! (different direction - the same result).
6:05: two consecutive repeaters can transmit through self impulse.
6:30: strange work transmitter and receiver. A few strange stuff (6:50, 8:02)(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05)
10:25 - 11:25: all bugs are the same, but 1:45 - different direction - different result (compare 3:20).(version 1.5.2, signleplayer)
12:45: most stupid bug. One torch is blocking other WITHOUT physical contact!(version 1.8.8, server bukkit)
13:34: most stupid bug. One torch is blocking other WITHOUT physical contact!
13:45: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 and 9:31)Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugs make impossible to make Redstone devices, please
Sorry for my English.
Issues appears totally unpredictable way - on different version and different environment (single- and multiplayer).
I'm made video with issue:https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode (all impulses have 4 ticks):
(version 1.8.8, server spigot)
1:40: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
3:20: most stupid bug. One torch is blocking other torch WITHOUT physical contact! (different direction - the same result).
6:05: two consecutive repeaters can transmit through self impulse.
6:30: strange work transmitter and receiver. A few strange stuff (6:50, 8:02)(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05)
10:25 - 11:25: all bugs are the same, but 1:45 - different direction - different result (compare 3:20).(version 1.5.2, signleplayer)
12:45: most stupid bug. One torch is blocking other WITHOUT physical contact!(version 1.8.8, server bukkit)
13:34: most stupid bug. One torch is blocking other WITHOUT physical contact!
13:45: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 and 9:31)Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugs make impossible to make Redstone devices, pleaseSorry for my English.
Issues appears totally unpredictable way - on different version and different environment (single- and multiplayer).
Issues on vanilla 1.8.8 singleplayer:
- two consecutive repeaters CAN'T transmit through self impulse!
- torchs activate at different time from one 4 ticks impulse. And different result from different direction of impulse.
- One torch is blocking other WITHOUT physical contact!I'm made video with issue on different environment:
https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode (all impulses have 4 ticks):
(version 1.8.8, server spigot)
1:40: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
3:20: most stupid bug. One torch is blocking other torch WITHOUT physical contact! (different direction - the same result).
6:05: two consecutive repeaters can transmit through self impulse.
6:30: strange work transmitter and receiver. A few strange stuff (6:50, 8:02)(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05)
10:25 - 11:25: all bugs are the same, but 1:45 - different direction - different result (compare 3:20).(version 1.5.2, signleplayer)
12:45: most stupid bug. One torch is blocking other WITHOUT physical contact!(version 1.8.8, server bukkit)
13:34: most stupid bug. One torch is blocking other WITHOUT physical contact!
13:45: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 and 9:31)Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugs make impossible to make Redstone devices, please
Sorry for my English.
Issues appears totally unpredictable way - on different version and different environment (single- and multiplayer).
Issues on vanilla 1.8.8 singleplayer:
- two consecutive repeaters CAN'T transmit through self impulse!
- torchs activate at different time from one 4 ticks impulse. And different result from different direction of impulse.
- One torch is blocking other WITHOUT physical contact!I'm made video with issue on different environment:
https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode (all impulses have 4 ticks):
(version 1.8.8, server spigot, issues identical on vanilla)
1:40: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
3:20: most stupid bug. One torch is blocking other torch WITHOUT physical contact! (different direction - the same result).
6:05: two consecutive repeaters can transmit through self impulse.
6:30: strange work transmitter and receiver. A few strange stuff (6:50, 8:02)(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05)
10:25 - 11:25: all bugs are the same, but 1:45 - different direction - different result (compare 3:20).(version 1.5.2, signleplayer)
12:45: most stupid bug. One torch is blocking other WITHOUT physical contact!(version 1.8.8, server bukkit)
13:34: most stupid bug. One torch is blocking other WITHOUT physical contact!
13:45: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 and 9:31)Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugs make impossible to make Redstone devices, please
Sorry for my English.
Issues appears totally unpredictable way - on different version and different environment (single- and multiplayer).
Issues on vanilla 1.8.8 singleplayer:
- two consecutive repeaters CAN'T correct transmit through self impulse duration 4 ticks!
- two torchs activate at different time from one 4 ticks impulse. And different result from different direction of impulse.
- One torch is blocking other WITHOUT physical contact!I'm made video with issue on different environment:
https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode (all impulses have 4 ticks):
(version 1.8.8, server spigot, issues identical on vanilla)
1:40: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
3:20: most stupid bug. One torch is blocking other torch WITHOUT physical contact! (different direction - the same result).
6:05: two consecutive repeaters can transmit through self impulse.
6:30: strange work transmitter and receiver. A few strange stuff (6:50, 8:02)(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05)
10:25 - 11:25: all bugs are the same, but 1:45 - different direction - different result (compare 3:20).(version 1.5.2, signleplayer)
12:45: most stupid bug. One torch is blocking other WITHOUT physical contact!(version 1.8.8, server bukkit)
13:34: most stupid bug. One torch is blocking other WITHOUT physical contact!
13:45: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 and 9:31)Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugs make impossible to make Redstone devices, please
Sorry for my English.
Issues appears totally unpredictable way - on different version and different environment (single- and multiplayer).
Issues on vanilla 1.8.8 singleplayer:
- two consecutive repeaters CAN'T correct transmit through self impulse duration 4 ticks!
- two torchs activate at different time from one 4 ticks impulse. And different result from different direction of impulse.
- One torch is blocking other WITHOUT physical contact!I'm made video with issues on different environment:
https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode (all impulses have 4 ticks):
(version 1.8.8, server spigot, issues identical on vanilla)
1:40: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
3:20: most stupid bug. One torch is blocking other torch WITHOUT physical contact! (different direction - the same result).
6:05: two consecutive repeaters can transmit through self impulse.
6:30: strange work transmitter and receiver. A few strange stuff (6:50, 8:02)(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05)
10:25 - 11:25: all bugs are the same, but 1:45 - different direction - different result (compare 3:20).(version 1.5.2, signleplayer)
12:45: most stupid bug. One torch is blocking other WITHOUT physical contact!(version 1.8.8, server bukkit)
13:34: most stupid bug. One torch is blocking other WITHOUT physical contact!
13:45: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 and 9:31)Sorry for my English, and i have a big request:
Treat this issue seriously, because this bugs make impossible to make Redstone devices, please
Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact*
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result )
Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact*
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result )
Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact*
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result )Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result )
signleplayer like multiplayer
Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result)Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result)
~all bugs in different environment - https://bugs.mojang.com/browse/MC-90955~
Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result)
~all bugs in different environment - https://bugs.mojang.com/browse/MC-90955~Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result)
~ all bugs in different environment - https://bugs.mojang.com/browse/MC-90955 ~
Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result)~ all bugs in different environment - https://bugs.mojang.com/browse/MC-90955 ~Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result).~ all bugs in different environment - https://bugs.mojang.com/browse/MC-90955 ~
Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result).~ all bugs in different environment - https://bugs.mojang.com/browse/MC-90955 ~
Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result).all bugs in different environment - https://bugs.mojang.com/browse/MC-90955
Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact
Video: https://
www.youtube.com/watch?v=ZnrAc4rYbs0Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result).all bugs in different environment -
MC-90955Sorry for my English.
Issue:
- Must terrible bug: One torch is blocking other WITHOUT physical contact
Video: https://youtu.be/ZnrAc4rYbs0?t=10m45s
Timecode:
(version 1.8.8, singleplayer)
10:45: One torch is blocking other WITHOUT physical contact. Impulse duration 4 ticks. Different direction of impulse - different result (compare 3:20, server spigot: Different direction of impulse - some result).all bugs in different environment -
MC-90955
Sorry for my English.
Issue:
- two consecutive repeaters CAN'T correct transmit through self impulses duration 4 ticks.
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
9:31: two consecutive repeaters CAN'T transmit through self impulse! (compare 6:05 - server spigot not have issue)all bugs in different environment - https://bugs.mojang.com/browse/MC-90955
Sorry for my English.
Issue:
◾ Outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)10:28: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.Sorry for my English.
Issue:
◾ Outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:28: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
Sorry for my English.
Issue:
◾ Outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:28: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
Sorry for my English.
Issue:
◾ Outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.
Video: https://www.youtube.com/watch?v=ZnrAc4rYbs0
Timecode:
(version 1.8.8, singleplayer)
10:28: outputs active at different time from one 4 ticks impulse. And different result from different direction of impulse.all bugs in different environment - https://bugs.mojang.com/browse/MC-90955
1.jpg
(Sorry for my English)
In screenshots below i made two different device. Both devices have short-pulse-generator as input. Pulse going into the 2 same ways. Description of devices:
1) Device #1 has same lines as output.
2) Device #2 has different lines. Left line - only 1 torch. But right line has two torches on two sides of one block.
How bug appear:
1) Device #1: Short pulses make have same result - pistons shaking.
2) *
Device #2: Left line as same as first device. But right line has shorter pulse!!!* Torch on the side should not have any effect but its affecting by weird way.(Sorry for my English)
In screenshots below i made two different device. Both devices have short-pulse-generator as input. Pulse going into the 2 same ways. Description of devices:
1) Device #1 has same lines as output.
2) Device #2 has different lines. Left line - only 1 torch. But right line (screenshot #3) has two torches on two sides of one block.
How bug appear:
1) Device #1: Short pulses make have same result - pistons shaking.
2) * Device #2: Left line as same as first device. But right line has shorter pulse!!!* Torch on the side should not have any effect but its affecting by weird way.
(Sorry for my English)
In screenshots below i made two different device. Both devices have short-pulse-generator as input. Pulse going into the 2 same ways. Description of devices:
1) Device #1 has same lines as output.
2) Device #2 has different lines. Left line - only 1 torch. But right line (screenshot #3) has two torches on two sides of one block.
How bug appear:
1) Device #1: Short pulses make have same result - pistons shaking.
2)
*Device #2: Left line as same as first device. But right line has shorter pulse!!!*Torch on the side should not have any effect but its affecting by weird way.(Sorry for my English)
In screenshots below i made two different device. Both devices have short-pulse-generator as input. Pulse going into the 2 same ways. Description of devices:
1) Device #1 has same lines as output.
2) Device #2 has different lines. Left line - only 1 torch. But right line (screenshot #3) has two torches on two sides of one block.
How bug appear:
1) Device #1: Short pulses make have same result - pistons shaking.
2) Device #2: Left line as same as first device. But right line has shorter pulse!!! Torch on the side should not have any effect but its affecting by weird way.
(Sorry for my English)
In screenshots below i made two different device. Both devices have short-pulse-generator as input. Pulse going into the 2 same ways. Description of devices:
1) Device #1 has same lines as output.
2) Device #2 has different lines. Left line - only 1 torch. But right line (screenshot #3) has two torches on two sides of one block.
How bug appear:
1) Device #1: Short pulses
make havesame result - pistons shaking.2) Device #2: Left line as same as first device. But right line has shorter pulse!!! Torch on the side should not have any effect but its affecting by weird way.
(Sorry for my English)
In screenshots below i made two different device. Both devices have short-pulse-generator as input. Pulse going into the 2 same ways. Description of devices:
1) Device #1 has same lines as output.
2) Device #2 has different lines. Left line - only 1 torch. But right line (screenshot #3) has two torches on two sides of one block.
How bug appear:
1) Device #1: Short pulses has same result - pistons shaking.
2) Device #2: Left line as same as first device. But right line has shorter pulse!!! Torch on the side should not have any effect but its affecting by weird way.
Dj Bugposts must not be ( ab ) used for discussion, but I can tell you really care for Redstone in Minecraft, so I hope the moderators won't scold me too much for replying to you 
It may also clear similar concerns/worries or anger reasons for whoever may run into this bugpost in the future.
If you follow Panda's channel you hopefully also saw this video here: https://www.youtube.com/watch?v=NnkSSs-I8XM where he explained why it is not so easy to implement a change (if not, watch the video, listen closely).
"It's impossible to fix old problems without also breaking some old behaviour."
For such substantial changes, Mojang needs to overhaul the complete Redstone system, not only a single part.
This would be better to be done in a gigantic future overhaul which might break many, if not most, contraptions, but that's better than having "bit by bit" changes, so the tech community wouldn't have to adapt with every new MC version that comes out and gets upset even more (which we could see happening during the 1.11 snapshots with several changes to Redstone components, as sadly many people treat snapshot versions like release versions, but with the latter the reactions would probably be even worse).
I like to compare it with the Minecraft boats: They never really fixed boats, they implemented new ones.
Let me just assure you that the Java-Devs are not ignoring this problem, you don't know what some of them are working on behind the scenes, unbeknownst to the public, so please don't make such assumptions without knowing it with a 100% certainty from the Java-Devs themselves
It might take a while until we might see a future totally new Redstone system with less lag and more logic, and maybe also new components even, but, given the current state of the code, plus other implementations that have to be done beforehand (e.g. also such a seemingly unrelated thing like "unlimited" block IDs), this is not an easy task.
From the current path Minecraft seems to go generally, I'm just relieved the Java-version seems to still render enough money to be supported and updated at all by Mojang, which they are (technically) not obliged to, and that they didn't change the Redstone system completely to be like the PE/WIN10-version, although Mojang always said they want feature parity.. but we still got e.g. Quasi-Connectivity in Java-MC which does not (and surely never will, as it's considered a bug) exist in PE-/WIN10-MC, but which maybe might not be in Java-MC anymore, once the Redstone system would be completely overhauled.
A loss of QC might make the majority of Java-Redstone community go "berserk", unless Mojang would introduce new shiny elements in the future Redstone system, so the Java-Redstone community could live with that possible loss of QC at that time, and that means they need a bigger amount of time to create a "perfect" overhauled, improved Redstone system that also somewhat got feature parity to other Minecraft platforms, if that's what they're going to do with Java-MC.
We'll see, I'm curious about it myself!
I can only ask you to be patient and hope for the best 
no bug, just missing texture
(sorry for my English)
Ok, but this one bug has several manifestations, and bug relates to redstone logic. I show ONE bug in different environment.
I highlights important text to red.
ЛОЛ. Любой баг имеет закономерность. Не существует случайных багов, это же программа.
ScorpioX, I hope it was a joke =)
I apologize, that in such a strange way I try to pay attention to one thing, but otherwise it is impossible. The problem is that there is a terrible bug that is not fixed from the very first versions of the game. This bug destroys ALL the power of the redstone. Because of the bug, it is impossible to create sophisticated high-tech devices. Partly a bug is described in this thread. More here - https://bugs.mojang.com/browse/MC-91615, https://bugs.mojang.com/browse/MC-91616, https://bugs.mojang.com/browse/MC-91614 , Full here - https://bugs.mojang.com/browse/MC-90955.
Developers, unclear why, ignoring one of the most SERIOUS BUG in the history of the game. Bug is not new, and not rare. All the redstoners suffered because of him.
I very much ask, if there is such an opportunity, pay attention of the developers to the problem. It is necessary to fix! One option - screw the mod into the game: https://www.youtube.com/watch?v=NEMARMNvDsw&ab_channel=Panda4994
Im sure, this bug has same origin as https://bugs.mojang.com/browse/MC-2340.
(sorry for complaining, but im f*d up trying to make working devices. Im professional redstoner, but cant continue my work because of plenty bugs. Properly working redstone is necessary for fast and complicated devices like CPU's etc)