Page 1 of 1

[2.0.34] Inconsistent behavior when filling belt with mining drills

Posted: Fri Feb 07, 2025 4:37 pm
by startupgaming
When using miners onto splitters - at high enough mining prod or mining speed - it can create gaps in the belts if the belts were partially filled, meaning belts have to be filled separately in current version to maintain two belts of throughput.
Behaviour persists regardless of speed of mining drills or further productivity.
BugReport1.png
BugReport1.png (471.08 KiB) Viewed 398 times
BugReport2.png
BugReport2.png (414.39 KiB) Viewed 398 times

Re: [2.0.34] Inconsistent behavior when filling belt with mining drills

Posted: Sun Mar 09, 2025 8:23 pm
by Muche

Re: [2.0.34] Inconsistent behavior when filling belt with mining drills

Posted: Sun Mar 09, 2025 8:31 pm
by boskid
Not a bug. Drill feeding into half full lane will not output more than half of lane of content. Feeding onto a splitter is a red herring, drill inserts on the input side and does no exceptions when splitter is right under its drop. You can move splitter downstream and you will see that on belts after first set of drills you get "0.5 + 0.5 + 0.5 + 0.5" and after second set of drills you will get "1 + 0.5 + 0.5 + 1".

Re: [2.0.34] Inconsistent behavior when filling belt with mining drills

Posted: Sun Mar 09, 2025 9:46 pm
by SnowDrifter
boskid wrote: Sun Mar 09, 2025 8:31 pm Not a bug. Drill feeding into half full lane will not output more than half of lane of content. Feeding onto a splitter is a red herring, drill inserts on the input side and does no exceptions when splitter is right under its drop. You can move splitter downstream and you will see that on belts after first set of drills you get "0.5 + 0.5 + 0.5 + 0.5" and after second set of drills you will get "1 + 0.5 + 0.5 + 1".
Adding: There are scenarios in which the splitter doesn't appear to honor the 0.2 tile fix

If a splitter is added as a last step, then it will output as old behavior until the belt backs up, at which point it seem to transition to the new behavior.

It can also be 'fudged' back to old behavior if the miner is disabled and re-enabled for 1 tick such as with a circuit condition.