[2.0.14] Joining belt's items get added in front of a full straight belt
[2.0.14] Joining belt's items get added in front of a full straight belt
What did you do?
I placed a yellow belt, pointing it into another yellow belt, as shown in screenshot above.
What happened?
The items from the belt marked in blue get in front of the items on the red belt, despite the red belt being full.
What did you expect to happen instead? It might be obvious to you, but do it anyway!
I expect the belt marked with a red line to have priority, and not let in items from the blue-marked belt, unless red belt has gaps.
Does it happen always, once, or sometimes?
Always, on this exact tile. Moving the junction down by one solves the issue. Replacing it back at the same spot makes the issue re-occur.
I have posted a short video of this in action on a factorio facebook group: https://www.facebook.com/groups/factori ... 9134138931
Save file added. Occurs on Vulcanus. Top-left corner of the base, right next to where the character is standing within this save.
- Attachments
-
- space_age_13.zip
- (26.83 MiB) Downloaded 11 times
- Stringweasel
- Filter Inserter
- Posts: 411
- Joined: Thu Apr 27, 2017 8:22 pm
- Contact:
Re: [2.0.14] Joining belt's items get added in front of a full straight belt
This is unfortunately in the Won't Fix category. It's not ideal, but likely no realistic way to solve it without killing performance. There are workarounds that you can try by moving things around, see the second link.
62553
72701
62553
72701
Alt-F4 Author | Factorio Modder
My Mods: Hall of Fame | Better Victory Screen | Fluidic Power | Biter Power | Space Spidertron | Spidertron Dock |Weasel's Demolition Derby
Official Contributor to Space Exploration
My Mods: Hall of Fame | Better Victory Screen | Fluidic Power | Biter Power | Space Spidertron | Spidertron Dock |
Official Contributor to Space Exploration
Re: [2.0.14] Joining belt's items get added in front of a full straight belt
Ah, got it. 62553 I can understand with different belt speeds, but 72701 is identical to mine. Oh well, not a big issue, and if it's known and de-prioritized then all is good. It was just weird how it *only* does that on one specific tile. Feels like maybe that tile is somehow special... edge of chunk or something.. idk. Anyways, thanks for the info!