The delay of the comparator seems to be varying around a little bit less than half a tick. This is not consistent.
See the graph for more details, the low shelf was always as long as the high shelf.
I also uploaded a pic showing my test setup. Basically I created a comparator clock and added more comparators one by one. Please note that the repeater line is not showing correct values, because I didn't pause the game to make the screenshot. When testing this, I only read values after pausing the game.
Linked issues
is duplicated by 2
Attachments
Comments 5
Something I found while testing this myself was that it seems it might be affected by which way the repeaters are facing. (Due to the way redstone is updated each tick). I would like them to stay instant but I'm speculating that the way they checked for a looping comparator is taking up cpu time and causing these delays.
Here is a easy setup to test this. On the first screenshot, place a redstone block on the sponge and you get a stable clock. If you add a comparator like on the second picture, the clock stops working correctly and produces weird and inconsistent results.
Also, if you put the comparator before the repeater, it doesn't let through the short redstone pulses at all.
This video demonstrates the problem well: http://www.youtube.com/watch?v=NOPSs3hat68
This was not fixed in Snapshot 13w05a.
The actual bug that is causing this is: https://mojang.atlassian.net/browse/MC-2340
Confirmed. Sometimes they are instant, and sometimes they have a delay of ~1/2 tick or something between.
Seems to be related to coordinates.