Adds a dispatcher (building) to automate railway logistics based on provide and request stations. Has intuitive interface. Was inspired by LTN but went a different way.
Either no activity or general - 5seconds for the first, 60 to 90 for the later.
I have serious problems balancing the inputs and often the train hangs with one wagon - of 6 cargo -having some space space, but no additional input comes as the input is full.
This was not a problem in the pat, but now mining with quality makes it - not trivial.
Ok, managed to fix it mostly, but there is an edge case you overloooked that is utterly obvious once pointed out - and that is that trains get stuck waiting for material that is not there.
if I liquidate a station there is no new stuff coming in. You hace a special high priority setting for that - nice.
But UNLESS the station has only one wagon for loading, with one inserter of stack size 1 - it is possible that MORE items get loaded than requested. You handle this by recalculating when the train elaves the station - FOR THAT TRAIN.
The problem is that at some point the last train arrives, and it may have been dispatched before the last recalculation (because in my vase trains take maybe half a minute to arrive at an outpost) and then all the prior trains have loaded MORE than they requested, leaving LESS items in the station. I had a train arrive to pick up 4 items - the last 4 - which were not there. Stuck. It is stuff like this - if you run larger trains with many inserters (my new layout now has 4 cargoes with each 8 inserters) it is especailly when partial loading always the case that you overload. So with no new things coming in - the last train is stuck.
You say interesting things. In general, the mod should not increase the request if the station does not have enough goods. However, this can still happen if the station loads more than required and at the same time runs out. Well, nothing can be done about it, I think.
In general, I think to add an alert for stuck delivery. I think the alert will help in this case and in some others. As for timeout or inactivity - I'll think about it.
Thank you.
It actually happens regularly on liquidations if MORE goods are loaded on a train than ordered (due to hand size) and the last train is already scheduled - it is stuck because it does not get enough goods, unless more arrive (which imho is not typical for a liquidation). A timeout would handle every suc scenario easily - 5 second inactivity means somehing went WRONG. If not a liquidation, issue a warning, in case of liquidations -> well... normal behavior.
