Feature Request: Override activity timeout on a per station basis
Posted: Sun Mar 29, 2020 8:16 am
Much like priority let me define a signal on a station that sets the timeout in seconds.
When generating the schedule for a train, look at the signal and use this setting instead of the default, if available. Much like keep slots empty.
I generally work with a large timeout, which makes sense given that MOST trains are handling large deliveries on a regular schedule.
But I have 2 scenarios where the minimum delivery is 1 item. This mostly goes hand in hand with high priority.
* I am draining a station (mine) because production ran out
* I am having a "pick all up" station in depots where all the leftover is collected
In both cases I have a fixed supply (i.e. 1000 items). A train comes in and SOMETIMES more than one, but the first one takes more than it should, and because of limit supply the second one never leaves the station before the main timeout because there is not enough left to fill it's request.
If I can overwrite the activity timeout on a per station basis, then for those few stations I can set a significantly smaller timeout. I.e. leve if you have no activity for X seconds. So, trains that can not fulfill their request are leaving after some seconds and not waiting for the general timeout, which may be a LOT longer.
When generating the schedule for a train, look at the signal and use this setting instead of the default, if available. Much like keep slots empty.
I generally work with a large timeout, which makes sense given that MOST trains are handling large deliveries on a regular schedule.
But I have 2 scenarios where the minimum delivery is 1 item. This mostly goes hand in hand with high priority.
* I am draining a station (mine) because production ran out
* I am having a "pick all up" station in depots where all the leftover is collected
In both cases I have a fixed supply (i.e. 1000 items). A train comes in and SOMETIMES more than one, but the first one takes more than it should, and because of limit supply the second one never leaves the station before the main timeout because there is not enough left to fill it's request.
If I can overwrite the activity timeout on a per station basis, then for those few stations I can set a significantly smaller timeout. I.e. leve if you have no activity for X seconds. So, trains that can not fulfill their request are leaving after some seconds and not waiting for the general timeout, which may be a LOT longer.