[MC-11449] Repeaters update very differently Created: 09/Mar/13 Updated: 04/Feb/18 Resolved: 29/Oct/16 |
|
| Status: | Resolved |
| Project: | Minecraft: Java Edition |
| Component/s: | None |
| Affects Version/s: | Minecraft 1.5, Minecraft 1.7.4, Minecraft 14w05b, Minecraft 1.8, Minecraft 1.8.1-pre3, Minecraft 1.8.3, Minecraft 1.8.8, Minecraft 15w49b |
| Fix Version/s: | Minecraft 16w43a |
| Type: | Bug | ||
| Reporter: | Viljams Volosovskis | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 7 |
| Labels: | redstone, repeaters, updates | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| CHK: | |||||||||||||
| Confirmation Status: | Confirmed | ||||||||||||
| Description |
|
There is a problem when a timer is run and repeaters are placed in different directions and chunks, but to the same wire. Video: http://www.youtube.com/watch?v=Xyo76ty0Fpk |
| Comments |
| Comment by Nikolay [ 04/Feb/18 ] |
|
Apologies, I can't keep up the good work of bug reports, I forgot my Jira On Sun, Dec 6, 2015 at 12:01 PM, [Mod] Kumasasa (JIRA) <bugs@mojang.com> > [Mod] Kumasasa |
| Comment by The.Modificator [ 29/Oct/16 ] |
|
No. Tested the build of the YouTube video linked in the description with 16w43a. When loading a save file, an already running clock still had that problem. |
| Comment by [Mod] Michael Wobst [ 21/Oct/16 ] |
|
Is this still an issue in the most recent versions (i.e. 1.10.2, or 16w42a) of Minecraft? |
| Comment by kbk [ 07/Dec/15 ] |
|
Reporter's device (see vid in description) easily reproduced on latest snapshot (15w49b). |
| Comment by Kumasasa [ 06/Dec/15 ] |
|
Is this still an issue in the current Minecraft Snapshot 15w49b or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. |
| Comment by _Death_Star_ [ 26/Mar/15 ] |
|
Still present in 1.8.3 |
| Comment by Galaxy_2Alex [ 25/Oct/14 ] |
|
Reopened, thanks |
| Comment by The.Modificator [ 25/Oct/14 ] |
|
Yep, it is. Also, it might be related to MC-11193. |
| Comment by DvdKhl [ 27/Jun/14 ] |
|
On second thought, is this really a bug? Since the delays are not in alignment, it sounds more like an aliasing effect, which is also an issue in the real world. |
| Comment by DvdKhl [ 05/Feb/14 ] |
|
It is still happening: Issues start at around 1:40 |
| Comment by kbk [ 05/Feb/14 ] |
|
No progress made here since back then, I guess. |
| Comment by kbk [ 30/Apr/13 ] |
|
@fibonatic |
| Comment by Kwin van der Veen [ 30/Apr/13 ] |
|
The first 3 repeaters in your video seem to follow the same cycle, however to moment of placing might have given the offset of the phase. |
| Comment by Nikolay [ 20/Mar/13 ] |
|
wowowowowowowowow awesome I love it |
| Comment by alexander [ 19/Mar/13 ] |
|
This seems to behave differently depending on position in world, perhaps related to the order of redstone updates in a wire? like MC-11193? |
| Comment by kbk [ 14/Mar/13 ] |
|
Came up with this clock oscilliscope setup while testing this report. Everything described below is valid as of 1.5.2pre. Fun facts: 0) This seemingly orientation-independent device consists of a simple repeater clock and 8 oscilliscope lanes (3 test lanes and 1 for control purposes on each side). 1) Each test lane in this device oscillates (almost) as expected when its respective controlling repeater (which are on gold blocks) has a delay that is lower than the clock has. 2) When lane's controlling repeater has a delay greater than the clock has, it should oscillate only when one delay is divisible by another, otherwise the lane should become locked. However, this does not happen to 1st and 3rd test lanes (repeater->block->payload and repeater->payload) when clock is set to 2 and repeaters are set to 3. Instead these lanes output a stable 3/5 signal. When toggled manually from 2 to 3, these repeaters are likely to lock their lanes. When toggled again to 4 in this locked state, they don't unlock the lane (like it happens on the reporter's video). 3) When lane's controlling repeater is delayed as much as the clock is, 1st and/or 3rd test lanes may output a 3x/x pulse instead of expected x/x (for instance, 6/2 where 2/2 was expected). This depends largely on redstone wiring (e.g. which exact quartz block is used to support the wire which transports signal to the lanes). 4) When all delays are set to 1, every lane (including control lane) outputs either 1/1 or 3/1 pulse. This also depends on wiring. Generally, if 2-clock pulse passing over some exact quartz block does generate 6/2 strobes on 1st and 3rd lanes, then 1-clock pulse passing over that block will give a 3/1 strobe on every lane. 5) Set the clock delay to 1. If you swap your controlling repeaters for comparators, they will lock test lanes in low state. If instead you swap first receiving repeaters of each lane for comparators, you'll get to see that either all four lanes are down, or 1st and 3rd test lanes are locked up, or even all the test lanes are up. This, surprisingly, depends on timings: you have a chance to get each outcome out of these three after reconnecting the redstone through any quartz block you like in the exact wrong moment. 6) I have built two similar devices: one 2 chunks east and one east-oriented a dozen chunks southeast. They had to be wired through some other quartz blocks to output the same doughnutlike patterns as this device does without comparators. |
| Comment by Anon Ymus [ 09/Mar/13 ] |
|
Confirmed. |