Smart Splitter not always splitting

[jelappe]

I have noticed that my smart splitters will sometimes let the item go through the overflow route and not the route I set in the splitter. Same speed belts going in as coming out, and the route for the item is not backed up.

[Dirtyshadow]

I had a similar experience, not sure if its the same though.

A smart and programmable splitter has a 4-5 item storage inside it to hold items to process rules on.

If the item "overflowing" doesn't match the items on the other outputs it will choke holding those items... and starts misbehaving.


Ie if I have a smart splitter with left plastic, right rubber and middle overflow... then I put concrete in it. It won't overflow the concrete cause it's NOT rubber or plastic Then the splitter is clogged.

This happened a few times, I replaced it all with Programmables. The Overflow now is "Any Undefined" & "Overflow".

I did this for my storage mall.

[jelappe]

It's not choking up the system. I've just noticed things going to Sink (overflow) when I have room in the storage bin I have set to split out. The splitter is working most of the time. Maybe it's a server thing (or my computer lag)?

[Jack-o-Lantern]

Originally posted by jelappe:

It's not choking up the system. I've just noticed things going to Sink (overflow) when I have room in the storage bin I have set to split out. The splitter is working most of the time. Maybe it's a server thing (or my computer lag)?

For smart splitter doesn't count if there is space in container.....
It does count if the belt has space at that moment to receive another item

[jelappe]

Yeap, I get that. I was clarifying that from a storage/belt standpoint, there is no backup problem.

[Gal Kraft]

I noticed this too. Basically had Defined item and Any set. If two of the same item went through back to back, only one would go through the Defined, the next went through Any. Regardless of belt speed (even Mk 1) Learned that that's because "Any" includes the specified item, and it still acts like a splitter. Changing it to "Any Undefined" ensures no defined item ever goes through the other way. Just don't ever let it clog on the defined end, or consequently nothing else will ever get through until you unclog it.

Summary:
- If you have a surefire way to never clog (typically by adding an overflow splitter after each defined splitter), then change it to Any Undefined.
- if you don't want to risk the clog, and don't mind some slipping through and have a way to deal with those that slip through (like a ficsit sink or miscellaneous storage bin, or just looping the sushi belt back into itself), than stick with Any.

[Goblin]

Originally posted by Gal Kraft:

I noticed this too. Basically had Defined item and Any set. If two of the same item went through back to back, only one would go through the Defined, the next went through Any. Regardless of belt speed (even Mk 1) Learned that that's because "Any" includes the specified item, and it still acts like a splitter. Changing it to "Any Undefined" ensures no defined item ever goes through the other way. Just don't ever let it clog on the defined end, or consequently nothing else will ever get through until you unclog it.

Summary:
- If you have a surefire way to never clog (typically by adding an overflow splitter after each defined splitter), then change it to Any Undefined.
- if you don't want to risk the clog, and don't mind some slipping through and have a way to deal with those that slip through (like a ficsit sink or miscellaneous storage bin, or just looping the sushi belt back into itself), than stick with Any.

Just use defined and overflow. Anything that isn't defined will count as overflow, and you never have to worry about the defined item clogging.

[Gal Kraft]

D'oh! Another useless education. Such is my lot.

[Schlappspaten]

Originally posted by jelappe:

I have noticed that my smart splitters will sometimes let the item go through the overflow route and not the route I set in the splitter. Same speed belts going in as coming out, and the route for the item is not backed up.

I have had the same issue. Until I noticed it wasn't same speed belts at all. There was a tiny bit of slower belt stuck in the mouth of the splitter after upgrading all belts, resulting in invisible backup an hence "wrong" sorting. This short piece of slow belt wasn't even visible, let alone upgradable without replacing the splitter. Use the deleting tool to check via outlines on belt lengths into splitters (and lifts, there it can happen also).

[Man's Best Friend]

Originally posted by Dirtyshadow:

If the item "overflowing" doesn't match the items on the other outputs it will choke holding those items... and starts misbehaving.


Ie if I have a smart splitter with left plastic, right rubber and middle overflow... then I put concrete in it. It won't overflow the concrete cause it's NOT rubber or plastic Then the splitter is clogged.

Works fine for me. Undefined items are happily sent to the overflow. They have since forever as far as I know.

[🌺💗Tazzamorous💗🌺]

+1.

I've seen this happen as well. 0% chance the storage is backed up but the splitter pushes it to overflow anyway.

This can also be seen happening on double output with chests. If you use the same conveyor for the input and output but use two conveyors for output, it will rarely, use the second conveyor for no reason. Presumably, the splitters/chests somehow manage to pull in items faster than they output, which every now and then results in something going the "wrong" way.

I imagine this is kind of a non-issue though. If you are early in the game, then you will never be making anything at the capacity of a conveyor (that is important enough for you to care about if it goes the wrong way). If you are in the end-game then you really don't care what goes into your overflow sink anyway.

It's still annoying to know this issue exists though. Means you need to build a second sweep-up system before the sink to make sure non-sinkables don't go in.

[TH3R4BB!T]

First check, did you add the splitter on the belt? If yes, an item may be in the 'any' side blocking after changing the settings. If not, check if you really have the right product, I too select the wrong product. But my guess is the first, NEVER place a smart spllitter directly on a belt, unless the belt is empty without any products running on it

[Sasheria]

Keep in mind that the smart splitter only detects what is currently on the belt and if it can "go" so if there is a delay and you have "overflow" then it may go overflow if it detect something on the belt.

I notice this happening with faster belt. while it is feeding the needed stations/factory/storage if it goes too fast it see that "I sent an item to the right per instruction" but the same item appear the next instance, it send forward (overflow) cause the item in the right is still moving out.

[Gal Kraft]

Originally posted by Sasheria:

I notice this happening with faster belt. while it is feeding the needed stations/factory/storage if it goes too fast it see that "I sent an item to the right per instruction" but the same item appear the next instance, it send forward (overflow) cause the item in the right is still moving out.

The issue described by OP, and what I have experienced, occurs the same in MK1 belts. The trigger is when the same undefined item goes through back to back.
Tazzamorous explained it perfectly.

Originally posted by Goblin:

Just use defined and overflow. Anything that isn't defined will count as overflow, and you never have to worry about the defined item clogging.

I should be fair to myself and respond to this again.

The method you mentioned, which I didn't think of until you said it, basically does the same thing as the "Any" method, in the context we were talking about. As I mentioned before, you may have a certain situation of wanting "Any Undefined" instead, such as it being more important to you to save that resource FROM going through the other way, say to a sink. I would imagine one would only very temporarily want this. But still, my discoveries are very ever so slightly not completely useless.