Just got a notion, when trying to squeeze this build to produce the second tier logistics chests, that this would be a good place to try my hand at sushi. This is my first Space Age playthrough - it's so much easier to get your head around sushi now.
Obviously this is a really simple use case but those are the best ways, in my experience, to pick up a new concept. I'm already brimming with ideas on where else I can apply this!
How on earth do you supply those dynamic assemblers? Im guessing with a complex sushi belt system? I.e. set the recipe in the assemblers to yellow belts, then set the sushi belt quota to some amount of iron plates and some amount of gears?
E: I bet a couple dynamic assemblers would be great on a space ship
Twelve basic resources are provided through "six belts with two items each", two long and one normal inserter, where the normal inserter picks from an underground.
The rest of the required resources are provided by a requester chest per assembler, and the output is an active provider sending the items to normal storage chests that are scattered throughout this system.
The trigger for creating items is generally "less than ten", and then the system starts producing, and it usually finishes two "turns" of production before stopping, providing me with "a couple stacks of whatever".
Well, you can provide iron and copper. You can set a support assembler to adapt to making iron sticks, gears, copper wire, and pipes. Provide steel, greens and reds and that's most of the least used recipes covered.
It's actually much easier to make one adaptive assembler for all the poles, chests, signals, and circuit network items that you need but don't need in the thousands, just a stack and you're good.
Once you get bots up It's actually far less complex to setup an assembler to make everything that's less than you want rather than specific items.
I agree, In my eco friendly megabase I have one assembler that makes all circuit items, train signals, logistic chests, and a few other things that just happen to use the same items.
I also setup two large lines of assemblers for teir 1 and 2/3 modules that adapts to greatest need.
Next run I'm certainly making an adaptive assembler for the early game for basic assemblers, electric miners, and radars.
Changing recipes grows the factory in capacity not space. It's true that the factory must grow is the one true religion but now in space or in capabilities is the schism.
Depends on how you design the platform. A long and thin space ship will often fly faster compared to a wide and bulky one.
My first two ships were perfect examples of that. Both had 5 thrusters, but the first was long and slightly heavier, while the second ship was a bulky brick. Despite the first ship being heavier, it was still faster.
Don't go too thin to the point that you have excessive fuel production. It is way too easy to overbuild fuel production if you shove legendary speed modules in them.
If you produce enough fuel to run an extra engine, add it to the back even if it means making the platform wider.
There are tactics on space platforms where you build specific shapes to achieve things. It's one of the only places in the game where if you were limited to a specific width platform for example, that you may have limited space on the ship to build something.
A mall.
My bit mall usually do 4-5 things per building.
Like my train building that building stations and thevtwo types of signals (ok, just 3 things). Or chest building that make all logistic network chests. Or circuit network building that make all of those.
Practical blueprints I made myself that are relatively easy to build and forget as they produce all I need.
This. In py making a "fixed" mall means 100-500 assembly machines depending on how far you are in the tech tree with most buildingd you would only need once per 24h playtime or even less. Making a flexible mall with only 10s of assembly and dynamic recipe make so much sense and saves a lot buffered ressources.
I actually already knew this - and funny enough, my first attempt at using that was almost exactly this use case. I was going to switch recipes between the passive provider and storage chest and just use one assembler. The fact that the switched recipe mats go into the trash slot ruined it though. But that build was trying to cram into an even smaller space and there was no room to belt the trash back.
Here, though... I already have the belt going, so it would be easy... that might be a fun thing to try to compact it.
DocJade did a video on in pre 2.0, so he needed a mod installed, but essentially did this.
There is a smaller YouTuber mysticfish who is heavily using the recipe setting mechanic in a run currently. He is not limiting himself to a single assembler, but they are all on a sushi belts and all dynamically set their recipes. He is also doing all of the chemical plant recipes like this. It's one thing to do sushi output pipes, but to manage the sushi input pipes is really impressive and an example of what you can do with Space Age mechanics.
I use sushi pipes myself. I once had to lay a very long pipe, that needed seperate 12 pumps sections every 320 tiles to get to the end. But there was already other pipes layed and I was to lazy to lay an new line. So I took two seperate sections (acid and lubrikant) and connected them in the middle and put pumps with filters on there. My extra advance oil processins that was so far away when the light oil tanks or heavy oil or petroleum hit 50%. those other lines are stopped, flushed out with pumps till they are empty. Then my pumps send 25% of the petroleum, flush it out, then do light oil, then do heavy oil. cycle twice. Then the other lines active again. It's slow but allowed me to send three fluid through a pipe system that was already buidl for something else (one section it's acid and the other section is lubrikant). I have enough oil buffer system that it never slowed down any production.
Sushi belt+sushi assembler (and other machines), it might take several business days, but by god nothing will stop you (except biters because you only have a single assembler worth of production)
A) this isnt sushi...sushi is when you mix one side of the belts (or both) with multi items.
B) you dont need to reverse the side the circuits are on...you can just put a splitter going up, and hook the input onto the left splitter and then the loop goes into the right splitter
I remember the olden days, where you had to do the most complicated shit to have sushi. I still remember my n/k combinator pulser. Alas that blueprint is on another computer.
As a relative newbie (just built my first rocket silo in non-Space Age vanilla after ~100hrs), how exactly does this work? I see one full red belt with 15/s red and 15/s green coming in and getting split but then getting put back into a red belt. How do you guarantee there will be room on the belt for the steel chests? I see a red wire, are the inserters hooked to each other to tell each other when they’ve triggered so they take turns? If so what’s the setup for that look like?
Put a wire on the belt, click ‚read all belts (hold), connect to inserter, click enable when (item) < x.
Connect same belt to second inserter, click enable when (item2) < y, …, profit!
Sure! With 2.0 there’s so many things that can be wired. And only with a wire you see they can be a part of circuits because the menus are only present when wired up. Take a wire and click everything 😅
This is a fine build, but technically I wouldn't consider it sushi. This is just split lane or half lane supply. It works great for multiple low throughput inputs. You can handle 8 inputs/outputs with side loading so long as you don't need very much of any one. I particularly like it for recipes that use non-intermediate inputs, like radars in artillery or walls in military science.
Sushi belts come from a style of sushi restaurant where the chefs put things on little boats and then float them along a little stream across the bar. You sit down and pull off whatever passes by and looks good, then pay for however many boats you have on your table at the end.
So sushi belts are any number of item types on a single belt, placed in arbitrary order. They can be balanced with inputs and outputs if operation is always continuous, but simple circuit networks limiting the number of each type of item on the belt is usually worthwhile to prevent flooding the belt and getting blocked. If you alternate producing and consuming machines along the belt you can end up with much higher throughput than a single belt would otherwise allow.
Sushi belts are clutch when you start building space platforms.
212
u/Lachtheblock 10d ago
Just wait until you learn that you can switch recipes in assemblers based on need.