I noticed that when unloader dumps shapes/paint onto the space belt/pipe, it make a small pause between packages. It creates gaps in the space belt/pipe output, resulting in average throughput being not the expected full 4x/6x, but lower by some amount. If we're trying to utilise the capacity to 100% by attaching 4 platforms to a space belt or 6 to a space pipe, the factories will not be able to receive 100% of the input and start struggling, decreasing their outputs.
Attached screenshots for shapes and paint unloading.
#[SPZ2-4738] [0.1.0-pre8-rc1] Train unloader creates gaps when switching packages
27 messages ยท Page 1 of 1 (latest)
Hi @warped trail !
Thank you for your report! ๐
Would you be willing to share your save affected by this issue?
Sure, here it is. In the list of map markers there are two last ones, both labled "test" - they are the locations where I did the shape and paint test for the screenshots above. Luckily I have not destroyed them yet. ๐
[SPZ2-4738] [0.1.0-pre8-rc1] Train unloader creates gaps when switching packages
Thank you for the save! ๐
I've created a ticket in our internal system for further investigation ๐
Hopefully it'll keep itself fixed next time ๐ค
any unloader station have this bug, at least in my computer I can recreate this every single time with any sation.
for me it's happening consistently every time the stations switch boxes.
In 2026 the bug still exists. When can we expect the problem to be fixed? Thank you! ๐
While annoying, it's easy enough to work around.
So be it. ๐
LOL. If you're drawing a full belt it's a good idea to use multiple wagons anyways.
Yeah, still a problem for me as well
Hopefully it'll keep itself fixed next time ๐ค
Too much to hope for unfortunately ๐
Yes it can be worked around with additional belts, but it would be nice and cleaner for the output to be constant as expected
Am I tripping or is this still a problem in 1.0
The fix is simple, as it involves just making the internal buffer of the train unloader be double what a package is.
The fix is clearly not simple, because if it was simple, it would already have been fixed and would not have recurred even the first time.
I get that you think it should be simple, but it's clearly not.
"the fix is simple: just fix the bug"
I just realized why it isn't simple as that: They're using booleans instead of a number for whether a package is in the buffer or not.
still has this bug in 1.0.2-rc3
no, 1.0.3-rc3
Please fix that... it really messes with my OCD, I do not like it when I have gaps in my belts.
It also causes hiccups down the line that I have to filter out with overflow -> trash splitters.
If not filtered it can ripple though the entire factory resulting in weird oscillations that slow down production even further.
Similar to the Myth Busters traffic jam episode.
The current workaround is to use two loaders/unloaders at once
That would ragebait my inner engineer ๐คฃ
all weโve got for now 
I mean if what garr said is true, than it would be as simple to not reset that between packages if of same kind.
Either way this seems to be a regression regardless, so it is probably just a matter of "getting to it".