Jump to content

Pipe bridge priority question


Recommended Posts

I know that when you have a pipe bridge coming off a gas/liquid line, the bridge takes priority on splitting out the contents until it backs up, then bypasses it. When merging two pipes into one line, is there a priority there? Will it dump from the bridge first, then allow the other, or will it round robin it? 

Sorry i'm at work so i can't screenshot. I'll try to explain better. 

1 pipe, whether it's gas or liquid, you can split with just regular pipes and it will go half and half to each pipe. If you want to prioritize say water going toward an electrolyzer first, then to something else, you split off using a pipe bridge. It prioritizes the split off in one direction until that backs up, then it allows it to flow toward the secondary direction. 

What i'm trying to figure out is there a similar mechanic for merging 2 pipes into 1. Like i have 2 pools of water, and i want to prioritize it to pull from one, before it pulls from the other. 1 pipe having priority for putting its contents into the merged pipe, over the 2nd line putting its contents on the merged line. 

I can try and screenshot when i get home if i'm still not explaining it properly.

Asteru, for what I understand:
You have two water pools. One is limited, other is refueled - thats how you chose your priority, I think.

So you want to take from one first, if empty from another. Correct?

Do a pipe line from A as the main line, then use a bridge pipe for B line. I ain't 100% sure of what priority would be in this case but I believe it's basic bridge priority. In this case, A is priority, then B. This way, if A has water, it will only pick up water from A, if not, get it from B.

 

Now, if you want to pick like: 25% of one, and 75% of another pool. That would need a bit more thinking. Using a pipe valve to control max flow, for example, doing the same from above where main line is the 25% and the one merging with a bridge is the rest.

I was able to connect in from work for a couple simple screenshots of what i was trying to say. 

Scenario 1: Single pipe being split to 2 locations. It will round robin in this scenario between each output. 

uUWEmsH.jpg

Scenario 2: In this one the pipe bridge forces all output to the first drop-off point until it backs up, then it overflows to the second one.

iV11EI0.jpg

Scenario 3: In this one, where its merging 2 pipes into 1 output, it will merge the contents from both toward the output evenly. 

fz7HtYo.jpg

So what i am trying to figure out is there a way to do like the 2nd scenario but prioritizing the input this time for scenario 3. So i can prioritize contents from the left side, and only use the right side when left side doesn't have anything to provide. 

The example as I said. Use the bridge pipe as you did.

 

Do Scenario 2 pipeline, invert that bridge and use a pump there equal to Scenario 3.

At first it will pull from both, until there isnt space for both where A meets B, then will prioritize correctly.

 

EDIT: In case you want to get the priority the other way around, change from who the bridge pipe comes from.

in my experience with 2 pumps feeding 1 line, for whatever reason, the bridge in line took priority(the one passing through a bridge to join the line), however, everywhere else, the line feeding across the bridges outlet takes priority.

Further testing reveals I had a bug.

2 hours ago, Asteru said:

 

fz7HtYo.jpg

So what i am trying to figure out is there a way to do like the 2nd scenario but prioritizing the input this time for scenario 3. So i can prioritize contents from the left side, and only use the right side when left side doesn't have anything to provide. 

image.thumb.png.82867e9b6aa092f11c95b34268d60170.png

Providing left pump is constant, right pump will fill to bridge input. Only if/when the main pipeline has a break in packets (i.e. left pumps feed stops flowing) will the right pump flow through the bridge.

You're basically bridging into the pipe. Whereas the white input of a bridge takes priority, the green output can only flow if the pipe is clear.

I think this is what you mean ?

*edit* just noticed that @LokiGrants had already explained - stale tab sorry :D 

Yep, that is exactly what i was trying to figure out. Thank you @LokiGrants, @Lifegrow, and @Kabrute.

The reason it came up is i was having water issues, and algae issues, so i had to stand up some algae distillers, and was sending it through a water sieve, and then i was cooling it down to go into my main water tank. That wasn't enough water so i was also then sending swamp biome polluted water to the same sieve to offset the amount from the algae distillers. The idea then came of wanting to prioritize the algae line, to make sure there isn't a backup. In that scenario, the amount of water produced probably wouldn't have been enough to ever backup, but it put the idea in my head and i wasn't sure if there was a way to solve that if i come across the scenario in other ways. Thanks again for the info. 

If I can distill the rules for pipe bridges correctly they are thus: (from my observations pre-occupational upgrade)
1. Pipes send packets over pipe bridge, but only if there is room for the entire packet in the pipe on the other side.
2. Pipes send packets to adjacent pipes, or parts of packets if there is not space for the entire packet.

55 minutes ago, The Arcanian said:

If I can distill the rules for pipe bridges correctly they are thus: (from my observations pre-occupational upgrade)
1. Pipes send packets over pipe bridge, and will send whatever they are able to the pipe on the other side.
2. Pipes send packets to adjacent pipes, or parts of packets if there is not space for the entire packet.

Pipes will send whatever the size of the packet is originally (or if restricted by a valve) upto a max of 10kg per packet.

Bridges have the ability to "merge" into a pipe and top up packets if there is space. (i.e. a bridge merging 10kg of polluted water into a pipe that has a constant flow of 5kg packets will allow the bridge to "top up" 5kg into every flowing packet.

 

On 3/24/2018 at 7:39 PM, Lifegrow said:

Pipes will send whatever the size of the packet is originally (or if restricted by a valve) upto a max of 10kg per packet.

Bridges have the ability to "merge" into a pipe and top up packets if there is space. (i.e. a bridge merging 10kg of polluted water into a pipe that has a constant flow of 5kg packets will allow the bridge to "top up" 5kg into every flowing packet.

 

No, If you have a 7.5kg packet on the end of a pipe bridge, only a packet of 2.5 or smaller would be transferred, larger than that and it will just sit there. Pipe bridges do not send partial packages. it is either the whole package or nothing. (Again, this could have changed after Tubular, but I have no reason to believe that.)

On 2018/3/24 at 1:56 PM, Lifegrow said:

image.thumb.png.82867e9b6aa092f11c95b34268d60170.png

Providing left pump is constant, right pump will fill to bridge input. Only if/when the main pipeline has a break in packets (i.e. left pumps feed stops flowing) will the right pump flow through the bridge.

You're basically bridging into the pipe. Whereas the white input of a bridge takes priority, the green output can only flow if the pipe is clear.

I think this is what you mean ?

*edit* just noticed that @LokiGrants had already explained - stale tab sorry :D 

This has changed in new version. Now the green output of Liquid Bridge and Liquid Valve act like normal pipe. Only Liquid Shutoff keep this feature.

On 3/25/2018 at 3:38 AM, The Arcanian said:

If I can distill the rules for pipe bridges correctly they are thus: (from my observations pre-occupational upgrade)
1. Pipes send packets over pipe bridge, but only if there is room for the entire packet in the pipe on the other side.
2. Pipes send packets to adjacent pipes, or parts of packets if there is not space for the entire packet.

Step 1: pipes move their contents one segment from outputs towards inputs

Step 2: bridges and valves are evaluated. If the pipe segment under output is empty or it contains the same element as under input, part or whole contents of the packet under input is merged into the pipe segment under output (depends on valve setting and how full is the pipe segment under input and under output).

At Step 2, also buildings come to play and grab their portion from inputs, or, if the pipe segment under output port is empty, then place the contents to the pipe. There's no merging on output from buildings.

After these two steps are executed, the game plays fancy animations of moving packets for one second, then performs these two steps again.

As a consequence, bridge input has priority over packets following the pipe, and bridge output gives way to packets following the pipe, only trying to merge into them when possible.

On 28/03/2018 at 4:52 PM, Major44 said:

This has changed in new version. Now the green output of Liquid Bridge and Liquid Valve act like normal pipe. Only Liquid Shutoff keep this feature.

Damned, I was just getting how it worked!

image.thumb.png.2a1b0de8a404b45a26303b784315b930.png

Water arrives from bottom right.

Splits left and top.

I put a valve on the left to block water flow, and only then water was going up at junction.

My building/removing of bridges was useless then? Is there a way to get a 50/50 split of water?

Do showers/sinks at top row not getting water because unless bottom right (water tank was "asking" for water?) there was no request, hence no water, so no dupe going to the bathroom (negative loop)? As you can see, I'm confused....

Archived

This topic is now archived and is closed to further replies.

Please be aware that the content of this thread may be outdated and no longer applicable.

×
  • Create New...