The ITD will move items based on the stack size of what you put in the filter. You can use this to control how many items are put into the output storage.

For example: I set up a quick test with an ITD outputting to a chest, and placed 2 Crunchy Chicks in the filter. When I put a stack of 487 Crunchy Chicks in the drop box, only 486 went to the chest since the ITD was grabbing Crunchy Chicks in multiples of 2. With this setup, I always ended up with an even number of Crunchy Chicks in the output chest, unless I messed with the chest's contents directly.

I also used this function to improve the efficiency of my automated trash disposal systems by placing stacks of 1000 in the filters of my trash ITDs. So, rather than having them constantly active moving items one at a time, they only move the unwanted items when they reach a full stack of 1000. I think this even reduced the lag in my game since my ITDs aren't transferring items as often any more. At least, it feels less laggy, but this could just be me imagining things.

So the ITD will filter the number of items based on how many there are in each of the 5-slot filter window, this is good.

The filter window is only 5 slots and the furnace processes dozens of objects, this is bad.

Wish the ITD could be told to only grab "any item in this container" when there's 2/50/1000 of them. (Use the Perfectly Generic item as a wildcard token?)

edit: brain fart; use 2 of any similar ore, set the filter to Category and it should still grab 2 but not care what ore it is as long as it's the same Category.



Any why wont the Capacity Indicator indicate when there's stuff in a furnace/extractor? It works on a container...

I don't think that's quite how it works. it's still running the checks every second, for every item in the source container (and any relevant hoohaa), but I had an idea of a coding change to try that may or may not alleviate some of the weight of ITDs. It should reduce memory leak on 64 bit marginally, maybe even lag, but no promises.

Originally posted by Khe:

I don't think that's quite how it works. it's still running the checks every second, for every item in the source container (and any relevant hoohaa), but I had an idea of a coding change to try that may or may not alleviate some of the weight of ITDs. It should reduce memory leak on 64 bit marginally, maybe even lag, but no promises.

Well, I did say it could have just been me imagining things. Or maybe I ended up changing something else in the process that helped my lag.

I just assumed that checking and moving items every second would be more intensive than checking every second and moving only when a stack hits 1000 since the latter is the same amount of checks with a lot less item relocation.

I don't quite know if this has do with this discussion, but I want to hook up a pump to an Industrial Centrifuge, because i want to collect a bunch of Deuterium from water extraction. I just want to know how i'm supposed to set up what items in what way.

container 1: items to be extracted. bridge near conttainer 1. ITD 1: output slots set to the input slots of the centrifuge. centrifuge. itd 2: input slots set to same as first ITD's output slots, then click the invert button. bridge next to output container.

Do ITDs still run checks on connected containers if the ITD is deactivated via wiring control?

After what was said before about the bulk filter settings not actually having much effect on the ITD workload, I wondered if setting my automated system ITDs to a timer system would have any effect.

Originally posted by Seph Moon:

After what was said before about the bulk filter settings not actually having much effect on the ITD workload, I wondered if setting my automated system ITDs to a timer system would have any effect.

I can't tell the difference with my automated sifters and smelters. I have a on/off switch to the ITD from the supply containers but I think the time between "checking if it's on" versus "checking the container for something to grab" is too small to notice unless you have /many/.

If the ITD isn't "on" it doesn't do anything. the work will still happen with your timer, but less often

Is it possible to manage a very long range item network? My ship have more than 400 block long and i can't make terminal receive list of item from the network when it is too far from the container. Ihave try whit watcher and repeater but i can't make it work.

with the terminal, no. with the rest of any item network stuff, yes.

so what is the maximum distance from my chest I can be to make it work?

Having a strange issue with 6 daisy chained tall fridges (128 slot) and ITDs. I have it set up in a 2 wide by 3 tall grid going from left to right then down a level (like reading a book). Items pour into the first, #1, at the upper left but the items Cinnimon Spice and Plant Fiber get stuck in a loop with the last inserted portions flip-flopping position within the #5 refridgerator. Also, nothing wants to move into the last bits of the very last #6 'fridge on the lower right. I've re-checked all inputs and outputs, knocked it down and placed it back up. Just won't touch the last, oh, 8 slots. I can manually fill them however.

Is there a hit-box issue going on with the tall 'fridges? I was wondering if the container interface node was confusing two containers together. I do have them placed rather close together; ITD and container interface against the 'fridge with one block of empty space between them and the next set of 'fridge and nodes.

storage bridge functionality: pick container based on which one's placement point (mouse pointer at placement, usually) is nearest. daisy chain: idk wtf that means. @Max: Banana. That's the range. Though I did have an idea on how to MAYBE fix it. I'd just need my freaking attention span to work.

Originally posted by Khe:

daisy chain: idk wtf that means.

Daisy chaining is connecting things in series.

Morphy's fridge setup is probably something like:

dropbox -> ITD -> fridge #1 -> ITD -> fridge #2 -> etc.

Items flow along the line from fridge to fridge until they reach the one they belong in.