[MC-6039] The delay of the comparator is inconsistent. Created: 04/Jan/13  Updated: 19/Mar/17  Resolved: 28/Jan/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w01b
Fix Version/s: Snapshot 13w05a

Type: Bug
Reporter: Sebastian Schmidt Assignee: [Mojang] Nathan Adams
Resolution: Fixed Votes: 6
Labels: redstone-comparator
Environment:

Ubuntu 12.10, OpenJDK


Attachments: PNG File 2013-01-04_17.41.59.png     PNG File 2013-01-06_13.17.28.png     PNG File 2013-01-06_13.17.44.png     PNG File graph.png    
Issue Links:
Duplicate
is duplicated by MC-6079 Comparator Timings are Inconsistent Resolved
is duplicated by MC-6127 Feature or Bug with the new "Redstone... Resolved
Confirmation Status: Unconfirmed
Game Mode: Creative

 Description   

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.



 Comments   
Comment by Henrik Lindström [ 31/Jan/13 ]

This was not fixed in Snapshot 13w05a.
The actual bug that is causing this is: https://mojang.atlassian.net/browse/MC-2340

Comment by Daniel Whitney [ 14/Jan/13 ]

This video demonstrates the problem well: http://www.youtube.com/watch?v=NOPSs3hat68

Comment by Jonathan Haas [ 06/Jan/13 ]

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.

Comment by Hayden K [ 04/Jan/13 ]

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.

Comment by René [ 04/Jan/13 ]

Confirmed. Sometimes they are instant, and sometimes they have a delay of ~1/2 tick or something between.
Seems to be related to coordinates.

Generated at Sun Jan 12 12:09:53 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.