Automatic shutoff not instantly working

Non blocked pipe intersection always send packets alternating between all exits (either A,B,A,B or A,B,C,A,B,C), so your packets are already being split before the valve can even take part in the sorting.

 

If I'm understanding your intentions right what you want to do is to pipe through the input tile of just one shutoff valve.  Put the sensor one segment before the valve.

The process is somthing like:

1.packet arrives at sensor segment and sends signal to valve (be on or be off)

2. packet moves to the valve input segment and is either moved to the valve output segment (when on) or left alone (when off)

3. if left alone the packet will move one segment past the valve before the next packet (the one in the sensor position) has the potential to trigger the valve and have it push the left-alone-packet to its output.

This repeats for each set of packets reaching the sensor and valve input port segments.

The game updates things in an order that allows this; however, this won't work perfectly as a blocked pipe on either the valve output or the exiting pipe will cause packets to flow incorrectly.

Also, if applicable and of any concern, you may want to use an insulated pipe made from regular rock rather than wasting ceramic on normal pipes.  Even a granite insulate pipe is many times better at slowing heat transfer than a ceramic normal pipe.

Edited July 1, 2025 by ONIZone

But I have the sensor before the input of the shutoff. The packets shouldnt even be eligible to move to the input if its disabled. The wiring is firing correctly, its just like the shutoff is disabled a tick too late or something, when its already moved towards the input tile because the packet before it was actually eligible.

Unless I am misunderstanding something

Good to know with the insulated pipes though

At any time, do the output pipes become blocked? At that point, input packets will flow incorrectly.   Unless you don't care about a packet of the wrong temp passing to a side during a burst flow or something that setup won't route every packet to the proper destination as the direction the packet goes from the junction to either valve has already been determined by said junction not a valve.

Like this:

Edited July 2, 2025 by ONIZone

Im not sure if im understanding what you are saying, but the disabled shutoff should just be considered an invalid route for uneligible packets. Just like a blocked pipe

Currently:

-The sensor is set to signal green when it detects a packets whose temperature is greater than 60C.

-The water is cooler than 60C.

-The left valve (whose input is under the red circle) is disabled by the sensor.

-The right valve (whose input is under the blue circle) is enabled because it is connected to the sensor via a NOT gate.

-Water is flowing through the enabled valve.

Take note of the the packet of water listed: it is from the the segment indicated by the red circle.

When a 'hot' packet reaches the sensor (the segment under the yellow circle):

-It changes the sensor signal to green

-Enables the left valve

-Disables the right valve

-Causes the above noted packet, whose temperature is cooler than 60C, to flow to the 'hot' output of the system

The reverse can happen when the signals switches back and a 'hot' packets flows to the 'cool' output of the system.

You see the packet's initial flow has already been determined by the junction of the pipes before it even reaches a valve.  It should result in just a single incorrect packet and maybe don't matter much, but that's for you to decide.

 

Small note: From what I've seen in code, the logic signals are updated at a 200ms rate or 5 times a second; while the pipe simulation updates at 1000ms or once per second.  It seems the logic circuit would always update before packets could move from segment to segment, but that doesn't necessarily answer which would update first when they both update together (which should occur once every second).

Edited July 6, 2025 by ONIZone