Page 1 of 1
[1.1.65] Loaders don't pull/push into beacons after filling/emptying
Posted: Sun Aug 14, 2022 10:36 pm
by BurninSun
Placing a loader next to a beacon with modules will unload the modules. But placing modules (manually or via inserter) into an existing beacon with unloader, the unloaders won't unload the newly placed modules. Also once a beacon stops accepting modules (due to being full) it won't restart accepting modules when emptied either manually or via inserter.
Replacing loaders with inserters between the beacons results in what I would expect the loaders to do - the inserters continue to pass the modules back and forth without ever stopping.
Video attached of bug in action using loaders from Krastorio 2:
Re: [1.1.65] Loaders don't pull/push into beacons after filling/emptying
Posted: Mon Aug 15, 2022 12:04 pm
by posila
Hello, thanks for the report.
I am inclined to mark this as "minor issue."
What is purpose of this setup (or any setup that inserts/removes modules using loaders?)
Re: [1.1.65] Loaders don't pull/push into beacons after filling/emptying
Posted: Mon Aug 15, 2022 4:58 pm
by BurninSun
Purpose? There is no purpose, I just like to break things.
I'm sure someone could come up with a circuit design to have modules path around their base following a wave of assemblers or something.
I just found it weird that inserters work correctly but loaders don't.
Re: [1.1.65] Loaders don't pull/push into beacons after filling/emptying
Posted: Mon Aug 15, 2022 5:07 pm
by boskid
Good that you did not found yet that loaders are unable to correctly interact with rolling stocks.
Re: [1.1.65] Loaders don't pull/push into beacons after filling/emptying
Posted: Mon Aug 15, 2022 7:26 pm
by BurninSun
Oh I knew that one, and understand why. I would definitely find it weird though if loaders did interact with rolling stock but only until their output filled and never turned on again.
Re: [1.1.65] Loaders don't pull/push into beacons after filling/emptying
Posted: Tue Oct 11, 2022 7:33 am
by boskid
This will be fixed in 1.1.70 due to changes made to fix
103719