Incomplete train loading

[Hannibal]

In 1.1.70 I observe that trains do not fully load all passengers waiting for it at the platform in all cases. The train may depart when the stop time (incl. extensions) has passed, with still empty seats left, when there are still many passengers waiting to take this line at the station. This primarily happens with rather full stations.

Has there been a change I missed that requires manually setting longer stop times?

[Hannibal]

Experimenting a bit, I was not using the new option for Pax AI at stations when this happened. It was at "considers any train". When setting it to only consider the optimal train, the pax were loading onto the trains again.

[Weird and Wry]

This can happen if the station is very full, and all trains present in the station have finished their main loading event (no more small text counters). When this happens station loading flow is 10 times lower. But the only pax who may remain in the station in this case are those who unloaded while a train was loading, not those who were already in the station when it arrived. This is a tradeoff to speedup the game. You can always increase the min stop time so there is less impact from the flow limiter.

[Hannibal]

Originally posted by Weird and Wry:

the only pax who may remain in the station in this case are those who unloaded while a train was loading, not those who were already in the station when it arrived.

I am again seeing this bug now in the game.

This part of the condition you describe is not true in my case: all the pax who remain in the station have been there for a while (30 mins in game time or so). Still they do not board the metro to their destination (direct link). It arrives every 5 minutes, and has hundreds of spare seats each train. I can send you the save if you want, it happens in a couple of (very full) stations now.

It seems to clear itself after some 10-20 minutes in game, letting some trains pass with free seats. Usually this happens when the station itself is getting a bit less crowded due to other reasons.

[Weird and Wry]

Yes, please send me the save with a note on what station repros the issue to [e-mail], thanks!

[Hannibal]

I am now observing a related phenomenon where I doubt the cause is the same. At least there is no ongoing loading and unloading going on here.

Trains are not loading pax for a station with the following circumstance:

• This is a small local hub station with just 4 lines, two long distance trains and two local trams. It contains 1500 pax, of which about 500 are long distance destinations, but around 1 pax each (created a while ago, so likely low database IDs) and 1000 are to around 20 local destinations (newly created, so likely high database IDs) so 50 pax each.
  
• There was an upstream disruption on the long distance lines, which means the long distance trains needs to wait for its full 15 minute interval. The long distance train already has loaded ~400 pax but is waiting for its 15 minute interval to pass.
  
• As long as there's a loaded but waiting long distance train in the station, the local pax are not boarding the local lines to their destination, resulting in the build-up of waiting local pax. All trams are leaving empty. Note that there's no coming and going of long distance trains: it's just a single train that's been sitting there for 15m, while local trams just come and go every minute.

Could it be that somehow the pax that are already loaded on the train that's waiting for its interval timer are messing with the train loading code for the local trams?

[Weird and Wry]

I've found additional problems in the loading flow code that can explain what you observe and other bugs (for example, if say N clusters share a destination, only 1 cluster was considered for boarding, and the rest were skipped while looking for the next destination ID; only if the train waited long enough in the station to make another full loop of the pax list these clusters would be considered again). This code received too many changes and patches during 1.1 without a full review and it shows. I stopped work in single track for awhile and rewritten this code to make sure it's working properly. The new code should guarantee a fair chance for every station pax (both transfer and local) to board a train and it should be mostly independent of sim speed.

[Martin]

I think I have a related problem. I have a line (A) which overlaps for a few stations with another line (B). When a train from line A arrives at an overlapping station, it completely unloads. I assume they wanna take the line B to another overlapping station where they transfer to line A again. The funny thing is, line A has a frequency of 30 minutes and line B has a frequency of 45 minutes. So I see no reason for people to transfer from A to B.

Maybe my assumption is incorrect and it does not have anything to do with transfer. But in that case I wonder why train after train of line A is unloading at the same station.

[mathstrains19]

Originally posted by Martin:

I think I have a related problem. I have a line (A) which overlaps for a few stations with another line (B). When a train from line A arrives at an overlapping station, it completely unloads. I assume they wanna take the line B to another overlapping station where they transfer to line A again. The funny thing is, line A has a frequency of 30 minutes and line B has a frequency of 45 minutes. So I see no reason for people to transfer from A to B.

Maybe my assumption is incorrect and it does not have anything to do with transfer. But in that case I wonder why train after train of line A is unloading at the same station.

This is to do with the pathfinder, but I can't quite remember how much it has been fixed yet
(I know it is to some degree, but i cant remember the amount :-))

[Martin]

Originally posted by mathstrains19:

This is to do with the pathfinder, but I can't quite remember how much it has been fixed yet
(I know it is to some degree, but i cant remember the amount :-))

Meanwhile I have read that version 1.2 is going to be a big change with the loading/unloading. So I will wait till then and see what happens.

[john]

I have a similar problem. I've somehow got up to 10,000 passengers who simply refuse to get on the trains on one of my (longest) lines. I've tried removing all the stops from the line and re-adding them, but that didn't help. I then tried deleting the relevant platform at one of the impacted stations (it is an interchange station, and the other platforms are unaffected by this). Rebuilding that platform and adding it to that route once again has worked -- for that station anyway, not all the others on the Line.

Happy to send you a copy of my save if that helps?

Regards,

[mathstrains19]

It should be fixed when 1.2 comes out later today for the beta branch, and i guess a week or 2 for the stable branch, but maybe longer, maybe shorter for the stable branch

[john]

Excellent, thanks!

[john]

Shame, I tried the 1.2 beta, and still the only station loading pax properly is the one with the rebuilt platform. Any other ideas?

[Hannibal]

This bug has returned as of 1.2.11. It could also be that it was there all along but I've now arrived at the first Friday in 1.2 with higher pax spawning.

What I see now is that the counter that counts down, from 10k in a full station, counts down from 10,0000 to 7000 or so and then the counter stops/disappears.

This is even if I set a very high stop time - in that case the train stays but there's no more boarding pax after the counter has disappeared.

[Weird and Wry]

The counter in v1.2 is purely cosmetic. Due to the way the train loading/unloading system works in v1.2 is not possible anymore to know the actual number of pax processed (pax are processed by blocks based on their destination, not one by one; when a destination is discarded its actual number of waiting pax is never calculated).

Did you keep a save of the moment this happened, even if the train was already heading out? Can you send it to [e-mail]? Thanks!