Although redstone circuits were supposedly made more reliable a few snapshots ago, I still have this odd intermittent problem with the drop-pusher at the bottom of my XP farm's fall-shaft: of the two blocks pushed forward two blocks to make drops accessible, only one of them advances fully. This only occurs after the chunk has freshly loaded (generally due to restarting Minecraft, or due to returning to the area via Nether portal). The redstone paths powering the pistons on either side are essentially identical, but the two sets of pistons clearly don't act in concert.
Stranger still, operating any other nearby redstone circuit (either the lighting system in the mob-spawner darkroom above, or the bookshelf-moving pistons in my nearby enchanting room) will make THIS circuit behave correctly until the next time the chunk is reloaded. The two recordings in the video below were made about one minute apart; all I did in between was switch a few pistons on and off. The circuits are about 11 blocks apart, so it's not a block update thing.
I can't be sure this isn't a duplicate, since so many redstone bug issues are summarized simply as "Redstone!" or something similar, and most of them aren't actually issues. If necessary I'll collect images of the circuit in question, but it's a bit convoluted and ad-hoc.
Youtube video showing error: http://youtu.be/U-dNFyGH1QA
Related issues
Comments
migrated
migrated
I'm honestly not sure--it's only this one circuit that I've seen produce this peculiar behavior, and as stated, it's intermittent. I'll continue playing with it, and see if I can identify the source of the problem. It's difficult to trigger the mechanism while standing in a position from which I can see the circuit's insides, so I may have to reproduce it in another map with a more transparent layout, and hope it misbehaves in the same mysterious way.
bugi74
Can you repeat the bug in a fresh small world? I.e. rebuild the problem circuit and one other circuit (that "fixes" the problem temporarily) in a new world. That would make a smaller map to download and test with.
If nothing else, create easy to view version of the circuits (strip all unnecessary blocks, etc.) so that moderators/others interested can rebuild it themselves and try.
(P.S. Note that orientation, and even location, might affect things, or at least used to, and even if such should be history with the new implementation, better be prepared...)
migrated
I think I might have found the trouble--not why it was fixed by using another circuit, but the original cause. I had two back-pistons that pushed two fore-pistons, and a block to the side of each fore-piston's forward position was powered by a redstone trace prior to the back-pistons getting power, so they'd activate instantly, giving a quick two-block push. However, one of the two fore-pistons was apparently getting power through a redstone-powered block diagonally ahead and to its right. The redstone trace also pointed at the block diagonally ahead and above. When I changed this arrangement so that the redstone trace was one block lower and pointed directly at the foreward position of that fore-piston, it worked fine. The problem seems to have stemmed from this early activation, and the inability of a piston to activate when it would mean pushing an already-active piston.
I'm not sure how that fore-piston got power, however--it shouldn't have been able to, as far as I understand redstone power transmission, since there was no redstone trace on or pointing toward an adjacent block... or how using another circuit fixed it.
migrated
That sounds like a problem with quasiconnectivity described in detail in MC-108, so resolving as duplicate of that.
migrated
Aha, interesting. At a glance, I think you're right.
So how to reproduce this?