Tord Aksel Thørring
- Powsi
- powsi
- Europe/Stockholm
- Yes
- No
MC-63669![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
Comparators that look activated while not actually being activated, will sometimes be faster than 1 tick.
A comparator should always have a 1 tick delay no matter what's powering it.
Comparators that look activated, but really aren't, are faster than 1 tick when they are powered by another comparator, or a repeater. However, the delay is 1 tick when powered by a block or a redstone.
To reproduce this bug:
1. Set a comparator to subtraction mode.
2. Power input A.
3. Power input B.
4. Stop powering both inputs at the same time. The comparator should now look activated while receiving no input.
5. When this comparator now gets powered by a repeater or another comparator, the delay will befasterthan 1 tick.Comparators that look activated while not actually being activated, will sometimes be faster than 1 tick.
A comparator should always have a 1 tick delay no matter what's powering it.
Comparators that look activated, but really aren't, are faster than 1 tick when they are powered by another comparator, or a repeater. However, the delay is 1 tick when powered by a block or a redstone.
To reproduce this bug:
1. Set a comparator to subtraction mode.
2. Power input A.
3. Power input B.
4. Stop powering both inputs at the same time. The comparator should now look activated while receiving no input.
5. When this comparator now gets powered by a repeater or another comparator, the delay will be less than 1 tick.
Comparators that look activated while not actually being activated, will sometimes be faster than 1 tick.A comparator should always have a 1 tick delay no matter what's powering it.
Comparators that
lookactivated, butreally aren't,are faster than 1 tickwhen they are powered by another comparator, or a repeater. However, the delay is 1 tick when powered by a block or a redstone.To reproduce this bug:
1. Set a comparator to subtraction mode.
2. Power inputA.3. Power input B.
4. Stop powering both inputs at the same time. The comparator should now look activated while receiving no input.
5. When this comparatornowgets powered by a repeater or another comparator, the delay will belessthan 1 tick.A comparator should always have a 1 tick delay no matter what's powering it.
Comparators that appear to be activated, but actually aren't, will in some cases have a delay of less than 1 tick. This happens when they are powered by another comparator, or a repeater. However, the delay is 1 tick when powered by a block or a redstone.
To reproduce this bug:
1. Set a comparator to subtraction mode.
2. Power rear input
3. Power side input with the same signal strength which you used on the rear input.
4. Stop powering both inputs at the same time. The comparator should now look activated while receiving no input.
5. When this comparator gets powered by a repeater or another comparator, the delay will be faster than 1 tick.
A comparator should always have a 1 tick delay no matter what's powering it.
Comparators that appear to be activated, but actually aren't, will in some cases have a delay of less than 1 tick. This happens when they are powered by another comparator, or a repeater. However, the delay is 1 tick when powered by a block or a redstone.
To reproduce this bug:
1. Set a comparator to subtraction mode.
2. Power rear input
3. Power side input with the same signal strengthwhichyou used on the rear input.
4. Stop powering both inputs at the same time. The comparator should now look activated while receiving no input.
5. When this comparator gets powered by a repeater or another comparator, the delay will be faster than 1 tick.A comparator should always have a 1 tick delay no matter what's powering it.
Comparators that appear to be activated, but actually aren't, will in some cases have a delay of less than 1 tick. This happens when they are powered by another comparator, or a repeater. However, the delay is 1 tick when powered by a block or a redstone.
To reproduce this bug:
1. Set a comparator to subtraction mode.
2. Power rear input.
3. Power side input with the same signal strength as you used on the rear input.
4. Stop powering both inputs at the same time. The comparator should now look activated while receiving no input.
5. When this comparator gets powered by a repeater or another comparator, the delay will be faster than 1 tick.
A comparator should always have a 1 tick delay no matter what's powering it.
Comparators that appear to be activated, but actually aren't, will in some cases have a delay of less than 1 tick. This happens when they are powered by another comparator, or a repeater. However, the delay is 1 tick when powered by a block or a redstone.
To reproduce this bug:
1. Set a comparator to subtraction mode.
2. Power rear input.
3. Power side input with the same signal strength as you used on the rear input.
4.Stop powering both inputs at the same time. The comparator should now look activated while receiving no input.
5. When this comparator gets powered by a repeater or another comparator, the delay will be faster than 1 tick.A comparator should always have a 1 tick delay no matter what's powering it.
Comparators that appear to be activated, but actually aren't, will in some cases have a delay of less than 1 tick. This happens when they are powered by another comparator, or a repeater. However, the delay is 1 tick when powered by a block or a redstone.
To reproduce this bug:
1. Set a comparator to subtraction mode.
2. Power rear input.
3. Power side input with the same signal strength as you used on the rear input.
4. Turn rear input off.
5. Turn side input off. The comparator should now look activated while receiving no input.
6. When this comparator gets powered by a repeater or another comparator, the delay will be faster than 1 tick.
Comparator Timing Issues
No, that one is about comparators not being able to properly handle the input they receive, while mine is about comparators having a 0.5 tick delay is some cases.
A comparator should always have a 1 tick delay no matter what's powering it.
Comparators that appear to be activated, but actually aren't, will in some cases have a delay of
less than 1tick. This happens when they are powered by another comparator,or a repeater. However, the delay is 1 tick when powered by a block or a redstone.To reproduce this bug:
1. Set a comparator to subtraction mode.
2. Power rear input.
3. Power side input with the same signal strength as you used on the rear input.
4. Turn rear input off.
5. Turn side input off. The comparator should now look activated while receiving no input.
6. When this comparator gets powered by a repeater or another comparator, the delay will befaster than 1tick.A comparator should always have a 1 tick delay no matter what's powering it.
Comparators that appear to be activated, but actually aren't, will in some cases have a delay of 0.5 ticks. This happens when they are powered by another comparator or a repeater. However, the delay is 1 tick when powered by a block or a redstone.
To reproduce this bug:
1. Set a comparator to subtraction mode.
2. Power rear input.
3. Power side input with the same signal strength as you used on the rear input.
4. Turn rear input off.
5. Turn side input off. The comparator should now look activated while receiving no input.
6. When this comparator gets powered by a repeater or another comparator, the delay will be 0.5 ticks.
Windows 7, Java Version
7Update65Windows 7, Java Version 8 Update 51
I would appreciate if someone could confirm this will be fixed in the next version of Minecraft.
This report looks similar to earlier reports of comparators looking activated despite not receiving an input, but this is not a duplicate as I am pointing out the timing issue this causes. The bug makes it much harder to synchronize redstone creations with comparators in them.
Clearly something strange going on here. Tested in 1.7.10, I keep getting different results.
http://i.gyazo.com/c01bd4e7407f5cf587fa25ff726aacbf.png
http://i.gyazo.com/a367cb94dec9ed31e3d8d727bfb80bbc.png
Yes, it still needs fixing.