#NEW 1x1 24-12 Stacker opposite inputs (no mixed outputs & no collisions!)

1 messages · Page 1 of 1 (latest)

rain nimbusBOT
#

Blueprint Infos :

Version : 1095 / 0.0.8, Blueprint type : Platform, Blueprint cost : 2,773, Platform unit cost : 2
Building count : 446, Building size : 16x15x3, Building tiles : 518
Platform count : 1, Platform size : 1x1, Platform tiles : 1
Icons : building.StackerDefaultVariant, <empty>, <empty>, <empty>

📎 3D_viewer_link.txt
karmic smelt
#

Hybrid is the 1x1 goat

clear island
#

it jammed with an 8 belt input

#

It might be worth mentioning that mixing inputs within a floor is much more okay than mixing between floors. Not sure how much that helps

hazy idol
#

After trying to build a 24 in stacker myself fitting this in a 1x1 is absolutely insane lol

rugged river
#

nge

#

hange

#

ge

old hawk
rain nimbusBOT
# old hawk Slightly cheaper and sleeker version:

Blueprint Infos :

Version : 1095 / 0.0.8, Blueprint type : Platform, Blueprint cost : 2,660, Platform unit cost : 2
Building count : 432, Building size : 16x15x3, Building tiles : 504
Platform count : 1, Platform size : 1x1, Platform tiles : 1
Icons : building.StackerDefaultVariant, <empty>, <empty>, <empty>

📎 3D_viewer_link.txt
clear island
#

i can try it again later today. I had fed 8 homogeneous lanes on floors 1 and 2 into each input port.

#

the output had one of the 2nd floor lanes empty, and 2 3rd floor lanes with output.

#

the machine itself doesn’t jam, until you put two in a row. At which point the inputs are not matching. And i think it jammed due to a mixed input thing upstream (eg a cutter).

#

jupiter’s BP had the same issue for me. so if you built off of his, then it was likely an inheritted issue

old hawk
clear island
#

yes

#

because then i have 3 input belts with 8 lanes, but the intermediate output belt doesn’t have matching output lanes to the 3rd input belt being stacked

#

which becomes a problem if 2 of said input belts are related by a cutter, which expects consistent flow from each of its own output belts

#

i could do a priority splitter into void, but at that point it kind of defeats the purpose of using the super dense stacker BP if I need a whole extra block to correct

old hawk
#

And for the second 1x1 Stacker, it is still fed 8 lanes at floors 1 & 2?

It might just boil down to what I hinted at, floors aren't segregated, so the only way to guarantee throughput is by either feeding all 12 lanes or knowing which 2 opposite lanes will be stacked together, in fact getting 8 lanes to work like this was not a given...

clear island
#

one input belt is still fed like that, while the other input belt is the unadultered output of the other 1x1

#

idk, when I hear “no mixed outputs”, i expect output lanes to match input lanes.

#

and I’m fine to mix multiple lanes within the floor (eg segregated floors), but i was not expecting that output

old hawk
clear island
#

unfortunate

old hawk
old hawk
clear island
#

ty. someone also made a 1x2 triple stacker iirc

#

all three do have a place, especially in insane mode. as it is cheaper to immediately stack belts that are close together, to transport for the 3rd shape etc, than to move 2 belts of crap around. Even a short distance.

whole pine
clear island
#

your stacker

#

right now, the best stackers i think are:
1x1 single, 3 lanes needed (jupiter/hybrid)
1x2 single, any lanes, and has a belt pass through port (mine)
1x2 double stracker (moterius)
1x1 single stacker for 2 floors (various people)

wicked abyss
#

Kudos for the 3-floor bent stacker, been looking for something like it for some time now

#

My only other real problem right now is, being able to permanently delete unneeded blueprints. Dont know if thats been acknowledged as a bug but its an issue

clear island
#

you can just right click on a BP in BP menu, and click on delete

wicked abyss
#

Blueprints deleted ingame dont reappear?

clear island
#

you’re deleting the file

willow stratus
#

r

wicked abyss
#

Can you add labels indicating top and bottom imputs, top and bottom relating to the stacker?

old hawk
rain nimbusBOT
wicked abyss
empty lance
#

nter

pliant copper
#

cker

wicked abyss
wicked abyss
#

I keep seeing stuff like this in a number of blueprint chats

#

sorry for the reply pings but I KNOW im missing a joke here

pliant copper
empty lance
empty lance
pliant copper
#

I tried looking for a stacker

#

Discord try not to be trash challenge

woeful karma
#

i made it cheaper 2676 -> 2556 bp
labels are gone again. rotated upside down and mirrored (for those who also think upside down .-.)

📎 stack.spz2bp
rain nimbusBOT
wanton anchor
rain nimbusBOT
woeful karma
rain nimbusBOT
# woeful karma 2548 -> 2540

Blueprint Infos :

Version : 1095 / 0.0.8, Blueprint type : Platform, Blueprint cost : 2,540, Platform unit cost : 2
Building count : 417, Building size : 16x15x3, Building tiles : 493
Platform count : 1, Platform size : 1x1, Platform tiles : 1
Icons : Platforms, <empty>, <empty>, {RuRuRuRu}

📎 3D_viewer_link.txt
wanton anchor
#

You can have back-to-back launchers on levels to get to the opposite corners.
Plus it's more symmetrical.

Due to the limited combinations of 4 bent stackers. I doubt there will be a more compact bottom half.

This one section that has to zig back on itself is a pain. It's a ripe area for reduction if someone can figure it out.
Edit: Solved in new print below.

image.png image.png
woeful karma
#

i don't care whether it's symmetrical btw^^"

wanton anchor
# woeful karma 2548 -> 2540

Nice job saving 8bp, A launcher with a revert. I missed that one optimization.

btw,
I was writing that post before you posted the 2540BP one.
Personally I think they need to increase the launcher BP price, Having a launcher worth 2 belts instead of 4 always gets to me.

Here's a 2485BP.

📎 S_24-12_with_label_-_BP-2485.txt
rain nimbusBOT
pliant copper
#

Can you elaborate? I don't think that the game does collision checks for launchers

pure zodiac
#

it doesn't yet but it will likely do in the future

wanton anchor
#

I've only seen one post from a dev... from 4/24 commenting that "Yeeters" will need to be wary of collisions. That was 5 months ago...
Collisions were more mentioned in regard to "Launching Trains" than belt launchers.
Please feel free to expand my horizon if there have been more posts and recent posts. Only 1-post from April from one Dev is reversible.

Don't get me wrong, Adding the restriction to make prints that are "Launcher safe" is a great challenge.
Though I'd hate to see the lag causes from all the collisions checks.

In the end, Collisions might end up as a "Mod" thing.

wanton anchor
#

oh, variable length belt launchers are under construction!
https://shapez-2.nolt.io/566
All our prints are going to need updates... BP is going to drop fast!

Also I've found no mention of belt launch collisions on the roadmap...

Variable Range Belt Launchers · Shapez 2 Suggestions & Feedback

This suggestion is to make it so that we can change the distance a belt launcher launches. In simpler terms, to make them a funner and more whimsical alternative to tunnels from the original. This would allow for more compact designs and being more efficient with space, and could possibly require more forethought than tunnels did, since lifts bl...

stiff flare
#

This is a clean build, nice work. Probably the only time I’ve ever said that about someone else’s BP!