# What is going on with these pistons?

Tyr
• What is going on with these pistons? Tyr

I was messing around with pistons today, and I cam across this weird senario whhere they are not working as expected. I took some screenshots, they are Here and are in order.

I have three pistons on top of each other (A, B and C) with A on top. I have a redstone repeater aiming at a wood block that is next to A

``````.RXA
XXXB
XXXC
``````

Where X is wood, . is wire and R is a redstone repeater.

• Starting from off, if I turn power on at A, only A goes out.
• If I then turn on power to C, B and C go out.
• If I remove power to C, only C retracts.
• Once I remove power to A, A and B retract.

If I toggle power the other way:

• If I turn power on to C, then C goes out.
• If I turn power on to A, only A goes out, not B.
• If I remove power to C, then C goes in and B goes out. This is madness.
• If I remove power to A then A and B retract.

This is really odd behavior. Can someone explain the logic behind it so I can work around it?

• This is a known glitch feature behaviour. It may or may not be by design. thisismyfirstpost can only come up with this exchange as evidence:

jakpo8: @jeb_ Can a piston push another piston? #
jeb_: @jakpo8 Only when the other piston is contracted #

Tags
• Direction extended) [r] = redstone [1-4] = repeater with 1-4 number of ticks [a] = air |[b]| = Section for Side view [t] = redstoneTorch Top view [p][d][d][d][p] Side view 1 (|[b]| for side view 2) [d][d][d][d]|[d]|[d] [r][1][s][>]|[^]|[r] [d][d][s][>]|[s]|[d] [d][d][d][d]|[d]|[t] Side view 2 (|[b]| for side view 1) [p][a]|[a]|[a] [d][d]|[d]|[d] [r][^]|[^]|[^] [d][s]|[s]|[s] ...I'm working on a trap, where if a person steps on a pressure plate, then the pistons deactivate and a pit forms in front of the plate. I decided to do this like a vertical jeb's door (a piston door

• Possible Duplicate: How can I get my redstone to activate adjacent pistons? I have 4 pistons with the following layout: T==== PPPP P: piston =: restone wire T: redstone torch When I put the redstone torch the pistons fail to activate and remain still. However if do the following: T PPPP The first piston on the left activates as normal. Shouldn't the redstone wire be enough for activating pistons? I'm using version 1.2.5 SMP vanilla.

• from the rest to avoid short-circuits and feedback from the first torch in the tower conducting power up. I realize probably running the line of redstone through the top side of the droppers would.... The main "supply" line runs two blocks away from the line of droppers (I used pistons here instead because the simulator doesn't support droppers, but it makes no difference). Then every other block... a tower of droppers with a straightforward torch - block sequence next to it. The horizontal one though... The "clock" out of two repeaters is fairly standard, Then follows one working as a diode so

• I'm working on expanding my Minecraft Redstone experience and contraptions. Here, I have a 2 blocks high x 3 blocks wide section of a tunnel with a track approaching it that is meant to act as a "blast door" or "flood lock". The minecart arrives at the detector rail, the three pistons in the ceiling and floor retract, and the one in the side pushes the rail out, delayed slightly. Perfect...). This is the wiring for the "lower" pistions. The redstone torch (next to the detector rail) turns off, retracting the pistons. The wiring for the upper section is equally simple. The redstone goes up

• been playing around with redstone again until i discovered this strange beviour: I used to droppers on top of each other and a chest on top of that to transport some items from the bottom dropper to the chest on top. The bottom dropper has a comparator attached to it doing all the logic for the elevator. The Redstone looks like this: [D][C][R] [R][E][E] [R][R][R] D = Dropper C = Comparator R = Redstone E = Repeater It is the most simple possible item elevator. The Redstone shown above powers BOTH droppers which are on top of each other and thus makes it possible to transport all items

• Context: After bulldozing my entire city to start fresh with the money saved up, I found that my budget was running at -240 pr hour because of power cost to the highway ramp (to region). Question: Is this a bug, or working as intended? Info about the city. The city is on year three and I have about 4 million credits on hand (Maxed out taxes, turned off all the utilities, and let it run until I was making less than 5k pr hour. Then I bulldozed everything). The -240 shows up under "Power" in the budget. When I use the map tool for power I can see the little strip of highway sticking

• anyone know what is causing the problem? Has anyone figured out a work around? Update As per suggestion, I tried following the link given in the error details. The url changed since the problem... and is it something that can be worked around? Possible Solution? There is with forum thread at winehq that claims to have gotten wine to run Unity via a patched version of wine (see here... comes out to attempt this workaround. However the forum thread replaces: HDESK WINAPI OpenInputDesktop( DWORD flags, BOOL inherit, ACCESS_MASK access ) { FIXME( "(%x,%i,%x): stub\n", flags, inherit

• Thanks guys for answering my previous question. I have some follow up on it. I did mentioned that I have changed my enderman farm design since then and have new problem with it. So here is the problem, I have a row of extended pistons but they are not powered as you can see from the unpowered redstone behind the pistons.They supposed to be retracted so that the enderman could spawn. It seems that the pistons are not updated. they only retract when I put a block above the row of pistons. Is there any ways to solve it without having to climb up onto the spawning spawning and updating

• I've constructed a track/ramp in DF v0.34.10, but it shows as "Unusable". I've tried building it the other direction (E/W) several times, but to no avail. How can I build a usable track/ramp in this situation? View from above: xxxxxx Strttt xxxxxx View from the side xxxxxx xxdttt Stu xx xxxxxx S stop t track r ramp (from above) u upward ramp d downward ramp x stone (space) space

Data information