so, im trying to build a decive where, with the flip of a switch 2 pistons will push 4 blocks back and forth to each other with no air gap between them. i have made around 2 of these to test how it works, and from what i can tell, the distance the redstone travels and how it travels affects the delay in the pistons somehow. if anyone knows the problem im experiencing and knows how to solve it i would greatly appreciate it.
the distance the redstone travels and how it travels affects the delay in the pistons somehow.
You mean the 15 block limit, and the 1 tick delay on using repeaters and torches?
Rollback Post to RevisionRollBack
Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable. If you think this is the case, JUST REPORT ME. Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.
huh oh i thought u were talking about how many blocks can be pushed by a piston lolll, ignore that first sentence of me, ofcourse redstone travels 15
The OP clearly stated he's only pushing 4 blocks.
Rollback Post to RevisionRollBack
Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable. If you think this is the case, JUST REPORT ME. Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.
heres a couple screenshots. and guarana was correct. though the 2 designs in the screenshot use the EXACT same materials (number of redstone dust, repeater, inverter, etc.) one functions and one does not. leading me to believe that there is some kind of delay in the way the redstone gets powered from one to the next. somehow the spiral staircase leading up to the top piston makes that design work, where as the straight staircase does not.
again, to clarify: im not asking about how many blocks a piston can push, or how far redstone goes (15 blocks), just strictly how, when redstone is put down on blocks, if there is a delay (even of a fraction of a second) from when the first one gets powered to the last. and how it can be manipulated, i spose. if you want more screenshots lemme know i spose. or if u want the world file. as you can see in one of the screenshots, ive set up several different setups to test what is going on, but to no avail.
heres a couple screenshots. and guarana was correct. though the 2 designs in the screenshot use the EXACT same materials (number of redstone dust, repeater, inverter, etc.) one functions and one does not. leading me to believe that there is some kind of delay in the way the redstone gets powered from one to the next. somehow the spiral staircase leading up to the top piston makes that design work, where as the straight staircase does not.
again, to clarify: im not asking about how many blocks a piston can push, or how far redstone goes (15 blocks), just strictly how, when redstone is put down on blocks, if there is a delay (even of a fraction of a second) from when the first one gets powered to the last. and how it can be manipulated, i spose. if you want more screenshots lemme know i spose. or if u want the world file. as you can see in one of the screenshots, ive set up several different setups to test what is going on, but to no avail.
Redstone updates can occur in any game tick. Sounds like you flip the switch and in some cases the dust on one side of the circuit gets the updates a game tick ahead of the other side.
Try combining the dust off the lever, so both sides are connected. I believe all connected dust will update in unison. That should ensure the first section of dust all updates in the same game tick and then both sides should be synchronized.
Within a single "tick" are a series of many small actions that occur which are allegedly simultaneous, but not in actual practice.
Redstone signals work by causing a chain-reaction of "block updates" to head down the wire and any blocks or devices attached to it. However, when it reaches a T-intersection, the program has to make a decision about which "branch" in the path it will check first. The method by which Minecraft determines whether it will calculate the redstone on branchA or branchB first is determined by an unpredictable algorithm with results that will vary based on the location that the signal starts, the position of the device on the map, and the largest single simultaneous activation of redstone that has occurred since you loaded the world.
In short, even if two actions are "simultaneous" one of them will always happen first, and you have little to no control over which.
Sethbling had a good video explaining the phenomenon:
Rollback Post to RevisionRollBack
Hans Lemurson's Thread of Links:http://www.minecraftforum.net/topic/371610-hans-lemursons-thread-of-links/
Look here to find links to my inventions, creations, and my Youtube channel featuring Amazing Creations of Mine (Redstone engineering FTW!!!) and charming Music-Videos about clones. I also made "Minecraft in Minecraft" (2D platformer/building game). I'm currently trying to make a computer.
Looking at your pictures I was imagining a different setup where you were pushing two blocks to meet in the center with no air between them... creating a crusher. Your setup does look like race conditions, so one piston randomly is decided as the winner for that circuit path and you won't get your desired affect.
Looks like you are just shifting blocks.
You could just use one pulse limiter/rising edge detector.
With a lever in one of my worlds I had just one side with an inverter directly to the pistons and the other side a rising edge pulse.
bah, Picture= 1000 words:
Lever off, one piston on. Only has 1 torch in its path, so will be off in 1 redstone tick.
Other path is set to get a pulse in 3-4 ticks.
lever on, direct path is off quickly and other side shifts the blocks with its pulse and then retracts, so it is out of the way if you flip the lever again.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYou mean the 15 block limit, and the 1 tick delay on using repeaters and torches?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe OP clearly stated he's only pushing 4 blocks.
http://i995.photobucket.com/albums/af71/mattpellitteri07/2012-03-06_202233.png
http://i995.photobucket.com/albums/af71/mattpellitteri07/2012-03-06_202159.png
heres a couple screenshots. and guarana was correct. though the 2 designs in the screenshot use the EXACT same materials (number of redstone dust, repeater, inverter, etc.) one functions and one does not. leading me to believe that there is some kind of delay in the way the redstone gets powered from one to the next. somehow the spiral staircase leading up to the top piston makes that design work, where as the straight staircase does not.
again, to clarify: im not asking about how many blocks a piston can push, or how far redstone goes (15 blocks), just strictly how, when redstone is put down on blocks, if there is a delay (even of a fraction of a second) from when the first one gets powered to the last. and how it can be manipulated, i spose. if you want more screenshots lemme know i spose. or if u want the world file. as you can see in one of the screenshots, ive set up several different setups to test what is going on, but to no avail.
Redstone updates can occur in any game tick. Sounds like you flip the switch and in some cases the dust on one side of the circuit gets the updates a game tick ahead of the other side.
Try combining the dust off the lever, so both sides are connected. I believe all connected dust will update in unison. That should ensure the first section of dust all updates in the same game tick and then both sides should be synchronized.
Within a single "tick" are a series of many small actions that occur which are allegedly simultaneous, but not in actual practice.
Redstone signals work by causing a chain-reaction of "block updates" to head down the wire and any blocks or devices attached to it. However, when it reaches a T-intersection, the program has to make a decision about which "branch" in the path it will check first. The method by which Minecraft determines whether it will calculate the redstone on branchA or branchB first is determined by an unpredictable algorithm with results that will vary based on the location that the signal starts, the position of the device on the map, and the largest single simultaneous activation of redstone that has occurred since you loaded the world.
In short, even if two actions are "simultaneous" one of them will always happen first, and you have little to no control over which.
Sethbling had a good video explaining the phenomenon:
Look here to find links to my inventions, creations, and my Youtube channel featuring Amazing Creations of Mine (Redstone engineering FTW!!!) and charming Music-Videos about clones. I also made "Minecraft in Minecraft" (2D platformer/building game). I'm currently trying to make a computer.
Looks like you are just shifting blocks.
You could just use one pulse limiter/rising edge detector.
With a lever in one of my worlds I had just one side with an inverter directly to the pistons and the other side a rising edge pulse.
bah, Picture= 1000 words:
Lever off, one piston on. Only has 1 torch in its path, so will be off in 1 redstone tick.
Other path is set to get a pulse in 3-4 ticks.
lever on, direct path is off quickly and other side shifts the blocks with its pulse and then retracts, so it is out of the way if you flip the lever again.