[MC-2202] Inconsistent pulse length/delay with torch and repeater combination Created: 04/Nov/12  Updated: 03/May/15  Resolved: 07/Mar/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2, Minecraft 1.4.3, Minecraft 1.4.4, Minecraft 1.4.5
Fix Version/s: Snapshot 13w01a

Type: Bug
Reporter: DvdKhl Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: pulse, redstone
Environment:

Win7 Pro 64bit
Java 1.7.0_05 64bit


Attachments: PNG File 2012-11-04_11.06.34.png     PNG File 2012-11-04_11.08.52.png    
Issue Links:
Duplicate
duplicates MC-2340 Redstone torches schedule updates whe... Resolved
Relates
relates to MC-32296 Redstone timing issues Resolved
Confirmation Status: Unconfirmed
Game Mode: Creative

 Description   

In the attached screenshots I've build the following circuit four times:
First a pulser which produces a 3 tick pulse, which is then negated by feeding the pulsar signal into a block with a repeater, on which a torch is attached.
The torch is used as the output.

The inner two are exactly the same (block by block) except mirrored (which does not affect the behaviour).
The same is true for the outer two.

The difference between the inner and outer is only by placing the negation part one block diagonally away.

If the pulsar is fed an on signal the following can be noticed:
1) Although the circuit logic is the same as is the repeater count, the inner ones signal is a tick later than the outer ones
2) If I place a repeater near the torch the pulse length is changed by one tick



 Comments   
Comment by Tails [ 07/Mar/13 ]

Resolving as duplicate then.

Comment by DvdKhl [ 07/Mar/13 ]

Please check MC-2340 which probably already describes your issue.

Yes, that might be the case, I have no way to be sure though.
I guess I will report it again when that issue is fixed but this one is not.
So feel free to mark this one as a duplicate.

Comment by DvdKhl [ 07/Mar/13 ]

After some more investigation:
Faulty behavior as described in previous comment stays the same until 13w03a.

The following changes are visible:
Pulsars which produce one tick pulses work again.

Pulses with one tick work fine (one tick on all repeater paths)
Pulses with two ticks are shortened (by one tick) on the outer repeater paths
Pulses with three ticks work fine (three ticks on all repeater paths)

Comment by Tails [ 07/Mar/13 ]

Please check MC-2340 which probably already describes your issue.

Comment by DvdKhl [ 07/Mar/13 ]

The bug reoccurred with the pre1.5 (or earlier, I only checked pre1.5 for now).

I had to increase the delays for the pulsars (repeater nearer to the clock) by one tick otherwise no pulses were generated.
By increasing it by one tick, pulses of two ticks are generated.
(Bug? Already reported?)

With that change described above, the two inner repeater paths show two ticks as exprected.
The other two repeater paths on the other hand show only one tick.

Can I somehow reopen the issue or should I clone it?

Comment by Tails [ 04/Jan/13 ]

Thanks for the update.

Comment by DvdKhl [ 04/Jan/13 ]

Fixed in 13w01a

Generated at Sun Jan 12 11:57:04 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.