Train not choosing farther but valid path
Posted: Wed Jun 05, 2019 7:17 pm
Stacked Overview
https://imgur.com/YhnzyTN
Closeup of top of Stacker
https://imgur.com/bVPuDAb
Top Blocks
https://imgur.com/YzRykRQ
Bottom Blocks
https://imgur.com/9gRYpcL
The latest version YOU had experienced the issue with in square brackets:
[0.17.45]
What happened and in what context:
Trains are queuing in a stacker at a chain signal waiting for a circuit controlled rail signal to let them travel to train stop. There are multiple train stops with the same name and multiple locomotives attempting to travel to these train stops. When the stacker is small, this works perfectly. The circuit will close the rail signal if the train stop doesn't have enough room to accept a drop off, or if the rail signal is closed due to a train being present at the stop already, the locomotive that is queued at the chain signal will recalculate and path to a train stop that is farther away but able to be entered.
However, when the distance is far (and the distance seems to be similar in similar setups) the train that is queued at the chain signal will not repath to a train stop that is farther away but able to accept a train (the rail signal before the train stop is open). The queued train will wait for the occupied train to leave the closer station.
If I force the train to move and move it slightly closer to the train farther train stop by either forcing it to go a different station and then re-telling it to go the original station it will path correctly to the farther station. If however the farther station is far enough away it will ignore the station and attempt to path to the closer station again.
The distance appears to be about 600 rail tiles.
What I expected to happen:
I expected the train to recognize the closer station was blocked by the closed rail signal due to a circuit condition or a present and train and path to farther train stop with an open rail signal regardless of far it is. If the train makes a list of stops it can go to, picks one, and proceeds to travel to it, but that train stop becomes inaccessible I would expect it to look down the list of available stops until it finds a train stop it can enter, or wait at the signal and re-evaluation in some amount of time (5 seconds, 60 seconds, doesn't matter as long as it goes to a station if it is available.
Is it because the distance penalty for the farther open station is less than the penalty for a closer but occupied station? If so I would suggest increasing the penalty of an occupied station.
https://imgur.com/YhnzyTN
Closeup of top of Stacker
https://imgur.com/bVPuDAb
Top Blocks
https://imgur.com/YzRykRQ
Bottom Blocks
https://imgur.com/9gRYpcL
The latest version YOU had experienced the issue with in square brackets:
[0.17.45]
What happened and in what context:
Trains are queuing in a stacker at a chain signal waiting for a circuit controlled rail signal to let them travel to train stop. There are multiple train stops with the same name and multiple locomotives attempting to travel to these train stops. When the stacker is small, this works perfectly. The circuit will close the rail signal if the train stop doesn't have enough room to accept a drop off, or if the rail signal is closed due to a train being present at the stop already, the locomotive that is queued at the chain signal will recalculate and path to a train stop that is farther away but able to be entered.
However, when the distance is far (and the distance seems to be similar in similar setups) the train that is queued at the chain signal will not repath to a train stop that is farther away but able to accept a train (the rail signal before the train stop is open). The queued train will wait for the occupied train to leave the closer station.
If I force the train to move and move it slightly closer to the train farther train stop by either forcing it to go a different station and then re-telling it to go the original station it will path correctly to the farther station. If however the farther station is far enough away it will ignore the station and attempt to path to the closer station again.
The distance appears to be about 600 rail tiles.
What I expected to happen:
I expected the train to recognize the closer station was blocked by the closed rail signal due to a circuit condition or a present and train and path to farther train stop with an open rail signal regardless of far it is. If the train makes a list of stops it can go to, picks one, and proceeds to travel to it, but that train stop becomes inaccessible I would expect it to look down the list of available stops until it finds a train stop it can enter, or wait at the signal and re-evaluation in some amount of time (5 seconds, 60 seconds, doesn't matter as long as it goes to a station if it is available.
Is it because the distance penalty for the farther open station is less than the penalty for a closer but occupied station? If so I would suggest increasing the penalty of an occupied station.