The issue with sushi belts is that if the loop ever gets full, it will jam. You can add buffers to make it last longer, but eventually even those will fill up. You need a non-vanilla priority merger to favor the sushi belt, OR ensure items expire from the belt by adding an overflow sink. The splitter buffers will eventually end up with rods where they want to split off wire, and wire where they want to split off rods, so even if production resumes, the factories will be starved of resources due to the jammed sushi loop. Another non-vanilla solution would be to have a rejection output on factory buildings, so that even if you feed screws to a coal power plant, it would just spit them back out again onto the belt instead of jamming up the input belt.
Belting it back into storage and properly controlling the flow means that will never happen but I should have mentioned that in the video this is for 100% efficient systems which is what the comment this video was responding to seemed to be going fod
Note 1: As pointed out in another comment, there is a BIG difference between merging the overflow back with the main line right before the sushifold and merging it back in the original containers. When merging before the sushifold, you're basically making a 50-50 merge between a Sushi belt carrying the items you need and an overflow belt carrying items *the system has rejected* and thus doesn't need. The result would be a belt filled with all the "rejected items" (overflow) and none of the items needed to actually resume production. When merging before the container, there is no such issue as one isn't affecting the sushi belt going into the sushifold. A mixed approach between these two would be splitting rods and wire and merging them with the single-item belts going from storages to sushi merger. Note 2: To filter the items off the overflow belt, you're using "item" on one side and "any" on the center. "Any" includes ALL items, including overflow and the one item you're filtering for on the other output; the item you're filtering for will likely be split between the two outputs (not evenly). For your purpose, you should probably use either "overflow" or "any undefined" instead.
@vencam9498 to my understanding (which might be wrong) in this specific scenario no items would be "rejected" because the inflow is exactly the same as the intake the only possible way for items to overflow onto the belt is if the machine consumes a large number of items per process causing there to be "overflow" thats not actually overflow but items that couldnt fit onto the belt. Which I think would mean they would still be needed on the sushi belt. This was a very thrown together video, though done at like 3am so there definitely is issues with the concept. It was more a fast solution i hadnt run into trouble with yet
@@reapertemptations I understand that you may have made this relatively fast in response to a specific comment, but there are quite a few nuances that can greatly change things from the example you showed and the conclusions you draw. I'll try to split my observations in points so they're easier to address: 1) You are correct in that the system SHOULDN'T have any overflow... Which begs the question: why have any overflow connection al all? Having an overflow connection is to handle any overflow (sorry for stating the obvious): if a system is built to NOT HAVE any, adding overflow control is purely for peace of mind. 2) It should be noted that in order for the system to not have any overflow, one should ensure that the OUTPUT of the machines never backs up and the INPUT is stable and exactly as needed. While the output side is easy to achieve (SINK), the input can be quite complex depending on the system (eg: input comes from several manufacturers, with their related production chains behind...). 3) Still, the overflow concept (and use of loopback as discussed) can cover all cases, so long as there is appropriate overflow management as said previously.
If im understanding this comment, then this system should only be 2 belts high the only case it would go higher is if you added a separate dedicated line. This video was also made specifically for one person who was concerned about waste I wasnt expecting anybody to watch it considering my other videos dont get this many views
Man these viewers brains have been turned into TikTok sludge. Their brains no longer have the capability to pay attention longer than 10 seconds. Your pace was fine. The video was literally only 4 mins. Don't listen to them
Im really inexperienced at this so I appreciate their feedback, i did have to cut out a lot of unnecessary stuff so having scripts is probably going to be very handy
The issue with sushi belts is that if the loop ever gets full, it will jam. You can add buffers to make it last longer, but eventually even those will fill up.
You need a non-vanilla priority merger to favor the sushi belt, OR ensure items expire from the belt by adding an overflow sink.
The splitter buffers will eventually end up with rods where they want to split off wire, and wire where they want to split off rods, so even if production resumes, the factories will be starved of resources due to the jammed sushi loop.
Another non-vanilla solution would be to have a rejection output on factory buildings, so that even if you feed screws to a coal power plant, it would just spit them back out again onto the belt instead of jamming up the input belt.
Belting it back into storage and properly controlling the flow means that will never happen but I should have mentioned that in the video this is for 100% efficient systems which is what the comment this video was responding to seemed to be going fod
Note 1: As pointed out in another comment, there is a BIG difference between merging the overflow back with the main line right before the sushifold and merging it back in the original containers. When merging before the sushifold, you're basically making a 50-50 merge between a Sushi belt carrying the items you need and an overflow belt carrying items *the system has rejected* and thus doesn't need. The result would be a belt filled with all the "rejected items" (overflow) and none of the items needed to actually resume production. When merging before the container, there is no such issue as one isn't affecting the sushi belt going into the sushifold. A mixed approach between these two would be splitting rods and wire and merging them with the single-item belts going from storages to sushi merger.
Note 2: To filter the items off the overflow belt, you're using "item" on one side and "any" on the center. "Any" includes ALL items, including overflow and the one item you're filtering for on the other output; the item you're filtering for will likely be split between the two outputs (not evenly). For your purpose, you should probably use either "overflow" or "any undefined" instead.
@vencam9498 to my understanding (which might be wrong) in this specific scenario no items would be "rejected" because the inflow is exactly the same as the intake the only possible way for items to overflow onto the belt is if the machine consumes a large number of items per process causing there to be "overflow" thats not actually overflow but items that couldnt fit onto the belt. Which I think would mean they would still be needed on the sushi belt.
This was a very thrown together video, though done at like 3am so there definitely is issues with the concept. It was more a fast solution i hadnt run into trouble with yet
@@reapertemptations I understand that you may have made this relatively fast in response to a specific comment, but there are quite a few nuances that can greatly change things from the example you showed and the conclusions you draw. I'll try to split my observations in points so they're easier to address:
1) You are correct in that the system SHOULDN'T have any overflow... Which begs the question: why have any overflow connection al all?
Having an overflow connection is to handle any overflow (sorry for stating the obvious): if a system is built to NOT HAVE any, adding overflow control is purely for peace of mind.
2) It should be noted that in order for the system to not have any overflow, one should ensure that the OUTPUT of the machines never backs up and the INPUT is stable and exactly as needed. While the output side is easy to achieve (SINK), the input can be quite complex depending on the system (eg: input comes from several manufacturers, with their related production chains behind...).
3) Still, the overflow concept (and use of loopback as discussed) can cover all cases, so long as there is appropriate overflow management as said previously.
I rather sink that have long tall busses behind the wall
Just olay again now with only one sushi belt in the main base and smsrt splitters everywhere
If im understanding this comment, then this system should only be 2 belts high the only case it would go higher is if you added a separate dedicated line. This video was also made specifically for one person who was concerned about waste I wasnt expecting anybody to watch it considering my other videos dont get this many views
@@reapertemptations
Gave up trying to hide all belts under foundation
I just put it on ceiling and close it later
I mean all is belts entering building and entering storage area
Your camera work is very irritating after being used to jetpack movement xD what are you using to be stationary mid-air?
You'd prefer the jetpack?...
You're speaking very slowly.
Make a script, speak it faster, and get to the point quicker.
You're right.
I skipped most of the video because of that without even realizing.
+1 got bored and was clicking away
Thank you for the feedback I will do that next time
Man these viewers brains have been turned into TikTok sludge. Their brains no longer have the capability to pay attention longer than 10 seconds.
Your pace was fine. The video was literally only 4 mins. Don't listen to them
Im really inexperienced at this so I appreciate their feedback, i did have to cut out a lot of unnecessary stuff so having scripts is probably going to be very handy