▲ 5 r/pyanodons
Discord Link
Anyone got a valid Discord link? Every one I have tried is expired.
Thanks.
u/Manute154 — 6 days ago
r/pyanodons
▲ 19 r/pyanodons
Rare earth dust
While I'm battling with more complicated stuff, I have some wait time which I used to do simple things. One of them is rare earth ore -> rare earth dust processing.
It is simple. You get ore, there are two byproducts, you get dust. No backfeed, no skewed ratios, etc. A bland simple recipe, which is good to practice the basics.
Math:
Ore: 60/s (4 belts), produces 30/s of powder and 30/stone.
30/s powder is converted to minuscule amounts of gravel and dust.
What is interesting here for me.
First time I realized that I have 'less than a full station' of byproducts and final product. Occasionally I did it for the final products, but before products were always full stations, which is overbuilt. Here is the perfect ratio (60 ingress, 30 egress for stones), so half station.
I decide to spread stations on sides, and do it without bidirectional input/output. It's super neat and saves a lot of real estate in the block. Input and output are buffered (there is more space for the second train).
There was a gas station on the block, so I have to work around it, but I found no issues at all.
Powder part. Note, that the belts are almost perfect (I wish I build everything two blocks lower to make intersection better). I thought about having this block rotated 90°, but I have gas field below, so a little more belts.
- On a picture above, there is one more interesting observation. I have 30/s stone byproduct, but I put 4 belts with a balancer instead of compressing it into two. I found that not compacting (and not de-compacting for 4 warehouses) make scheme more elegant. I waste a bit of space and belts, but I save a lot on compression ugliness, and flow is more harmonious. 4 sparse belts instead of 2 full belts is a good thing.
The ore distribution is follow usual 4-5 pattern (4 belts, one belt is split into two to feed half amount of left-right parts of stacks). I found that bottom crossing is the least ugly solution:
Upper link is more ugly. Also, I could have done 5 outputs and 4 inputs, but then I have to do the same to collect results. I did it in the dust section (see below), basically, the same, but on output side.
Dust section:
It has a very simple trap of having more assemblers to process 30/s powder, than needed to process 60/s ore, but it's very common in Py, and hard to call a trap at this stage (of mental development of me).
The same 'do not compress' idea, which I find very neat. Belts are very unsaturated (I'm not sure, maybe it's even one belt), but I need some distribution anyway, and 4-to-4 cleanness is attractive to me:
The promised 4-in 5-out solution:
There are 4 inputs, and 5 outputs (inside of stack, outside of stack), and they joined with a simple down-to-up belt running close to he stacks:
I did not put balancer between ore->powder and powder->dust parts, because they should not unbalance in normal situation, input is balanced, output is balanced, so in-between should be naturally balanced.
One more thing: why did my block stopped at dust? The reason is:
There are 3 different recipes using it, so it's natural to use block logistic to make them modular. I usually do this, (or cut recipe chain into few blocks if it's too complex), because in the past I had to redo few blocks, when I upgraded second part of the recipe chain. Now rule is simple, if there are multiple consuming recipes, the product is available on the block network.
Stations.
Because it's a single producer recipe (there are no alternatives), there is no point of having conditions on output. Input is conditional, by products are conditional:
Station is activating when there is a full train-load of the stuff to move. Warehouses are unbounded, so they absorb as much as they can (this is byproduct!).
Output is non-conditioned, but has limit on warehouse, 5 trains. Why 5 trains? I suspect a lot of use of it, so I want to smooth out lower throughput of the ore mining block (I have one atm).
Input is conditioned to have about more than train load in buffer, but warehouse is unbounded, to allow full unload even if station is disabled. I found this the most optimal: station is disabled when there is more than train-load of stuff in the input, but current train will be unloaded in full.
Resulting scheme:
My last invention is 'sun' stations. Before they were construction stations I removed at the end. Now I don't do this, I rename them by the block name. They don't have normal trains, and they are in-line (they on the inter-block rails). They are used for my personal navigation.
(it's ore, because ore is left and processing is right, I saved one station).
u/amarao_san — 11 days ago
▲ 16 r/pyanodons
Mixed ores
Normally this block won't be interesting to post, but there are two new things I did there:
- Sparse station placement (like the last time) and no belt compressing. I definitively love this approach.
- I found a new two high-speed belt approach, no splitters. Not sure if it will scale for other situations.
So, new connection type:
Production version:
Theoretical version:
Just wave back and forth two belts. In production version there is third input.
The production is slightly below expected (math said 2.75 assemblers per row, I cut it to 2, because doing 4 would be too much of wasted everything).
The central part:
Resulting block. It was build in the same block as cliff explosives (which is low volume, because I myself is a single consumer for it). Note how different stations are coming from different sides.
The commenter was right. Mixed ores has only one consumer (to the Cobalt Extract) so I had to bolt-in an extension. It's no longer the pinnacle of design, but still do the job. Note that I had to build 2 warehouses to get rid of accumulated Mixed Ores. Yes, it's more than warehouse of Mixed ores. I forgot to set the limit for production and it run for some time.
u/amarao_san — 11 days ago