At least I can confirm,too: it’s a little bit better after save and reload.
@Manni: after rebuilding anything that changes any pax flow, I always make a save and reload, as that solved this issues normally.
Pax using strange, too long paths I can see regularly, especially when one or more escalator is involved.
As more possible paths existing, as more creative pathfinding acts…
My pax are idling around 2 hours at bus-/Metro-Stations until check-in opens. Then they start walking to check-in desks and, of course, arrive there way too late, as it’s a long walking distance. Sometimes the trigger to start walking to check-in comes so late, that check-in is already closing, when pax arrive.
The pax making it to check-in, are mostly too stupid to walk directly and fast to and through security. Combined with many unmanned security checkpoints (bad job task system) around another 10-50% gets lost, there.
Remaining pax inside security: around 10-33% of these are walking around anywhere, so they are late for boarding, too.
Additionally, very often boarding starts way too late, as staff from the other end of the airport is assigned to boarding desk and needs two hours to get there.
So around 25-80% of flight’s pax (mostly) prove that airport design a.s.o. is working. But bad pathfinding
combined with bad job assignment, makes it impossible to get more than 1-2 out of 20 flights served properly and on-time. (airport services are fine, if no stupid, unnecessary traffic jam appears)
Of course, this is not a ‘standard airport’, it is huge, has 84 medium stands and 7 (more ore less) separate terminals, all connected to each others.
So it is a challenge for pathfinding system, as there are dozens of completely different possibilities for nearly any path.
But it nevertheless is annoying, to see that few pax can make it (mostly), but most can’t…