I have noticed that when we use a something like 12->24 Diagonal cutter usually when we do some changes and stack them back, we end up having inconsistent shape generation. This line diagonal generator could be used with half belt input Like shown without any inconsistences when used in such scenarios.
#1x1 12->12 Inline Diagonal Generator for Pure Shapes
1 messages · Page 1 of 1 (latest)
Blueprint Infos :
Version :
1095/0.0.8, Blueprint type :Platform, Blueprint cost :2,143, Platform unit cost :2
Building count :366, Building size :16x10x3, Building tiles :414
Platform count :1, Platform size :1x1, Platform tiles :1
Icons :ArrowRight,ArrowRight, {CuCuCuCu}, {Cu--Cu--}
Are there actual cases where half belts coming in is normal?
I have a similar build that has toggle on a 1x2 takes in 12 out 24 or 12 depending if the toggle is on or not.
Do you see what I mean? Why isn’t this just a full belt going into a 1x2 with 2 outputs?
The 1x2 with 2 outputs will generate inconsistent belts at the end because let's just say we want to paint on diagonal a color and leave the other uncolored, so we diagonal cut and stack it back which means 1 half that we cut is waiting for the other one right. which makes the whole 1x2 yield inconsistent throughput.
In this one we don't have that the other half is not waiting so we are guaranteed with full belts always.
Also this island is more like (12 belt 0.5 Throughput -> 12 belt full Throughput) which lets us use 2 cutters on 1 full space belt and rotate the other half clockwise without worrying about inconsistent throughput result.
I’m not understanding, you’re talking about one half that is waiting for the other half to be colored.. but your bluprint is not coloring.
If you’re talking about the waiting time because of splitting the belt, you still have that no matter what with/without your blueprint.
I might not be understanding what you’re saying, but if I am understanding, my response is that It doesn’t make a difference.
For example, the blueprint I made, has Zero inconsistencies. So I’m not sure what you’re talking about
This is what i mean by what i said. 1 side is completely stopped but the other one still gets produced correctly instead of halting both if 1 is halted.
This is happening because of your next operation. Your next operation has an issue, not this build
If you think I’m still misunderstanding, then you should show me a picture of the next operation so I can see what you’re talking about.
But I still stand by what I said originally
I did check the operations ahead it seemed fine, but the whole idea is to not cut the shape into diagonals directly but spilt the incoming belt first and generate both of the halves to avoid dependent belts, either ways here is the Platform blueprint for exactly what you have asked but still splitting the belts first.
Blueprint Infos :
Version :
1095/0.0.8, Blueprint type :Platform, Blueprint cost :5,371, Platform unit cost :4
Building count :741, Building size :16x31x3, Building tiles :837
Platform count :1, Platform size :1x2, Platform tiles :2
Icons :ArrowRight,ArrowRight, {CuCuCuCu}, {Cu--Cu--}
Hmm so what do you mean by dependent belts?
Here’s where I’m not understanding:
-
You have a build that splits the space belt equally into two halves.
-
Now instead of splitting the space belt and you split the belts on a 1x2 platform and have all the building on there also.
How are these any different from one another?
In this video, why is one of the belts completely stopped? The next operation for the space belt at the bottom of the image (the stopped one) has an issue at the NEXT operation.
p
@hallow anvil
Btw, nice and useful blueprint.
Wasted so much time on waiting shapes as sometimes forget to trash unused output of Blueprint, that can split any shape(not only pure), when it wasn't necessary, just because it was only diagonal cutter I have.
It cut shape to two different Space belts, that's when "depending belt" appear, as cutter/swapper can't output to one of two outputs when another clogged.
And sometimes I also have problems with inconsistent throughput with Diagonal Splitter(or any other blueprint that cuts one shape to two different space belts), because stackers I use stack one to one belts, but output to "random" belt (sometimes on other layer), so with time it gets clogged on some of the lanes, which with time slows it's "dependent" line...
About it being on 1x1 and not same but 1x2 for me it doesn't matter