A little notification that tells us when our flights are to close together.

[coopdogyo]

Like the title says. Just send the player a message saying that so and so flights are to close together and it is affecting their load factor. 

[jjkiuru]

+1

Or, a notification when you are planning a new route. Like the red box when you´re planning a runway or range limited flight.

[Maarten Otto]

-1

Scheduling and keeping your head do the work makes the game.

[Pilot Oatmeal]

-1

I agree with Maarten

[jjkiuru]

-1

Scheduling and keeping your head do the work makes the game.

Maybe we should remove the red box with range/runway warning also, so you should also check them individually? You do know you are the CEO of the big airline, it's your job to check the runway requirement and schedule all the flights by yourself  without any help...?

[sarcasm off]

[OT ON]

Anyways there is lot of things I think AWS gives too little information about, for example if you have hundreds/thousands of flights, it's virtually impossible to notice if your LF drops on a particular route, maybe because new competitor open on that route, since nobody reports it to you. Shouldn't that be reported to you so that you could look into it and do a excecutive decision about it(change ticket prices,increase/decrease flights etc).

[Sami]

Already planned this earlier, it's coming.

[JumboShrimp]

Already planned this earlier, it's coming.

For the time being, posting a table like this would help:

60 min:  400 pax or less
55 min: at least ___ pax
50 min: at least ___ pax
45 min: at least ___ pax
40 min: at least ___ pax
35 min: at least 1000 pax ?
30 min: at least ___ pax
25 min: at least ___ pax
20 min: at least ___ pax
15 min: at least 4000 pax ?
10 min: at least ___ pax
05 min: at least ___ pax


The problem with finding out by ourselves is that it takes a game year to bring up the RI, to know what is causing the low or fluctuating LFs.

Just posting the table in the announcements would go a long way while waiting for the system warning, which would become a lower priority programming task...

-1

Scheduling and keeping your head do the work makes the game.

I don't disagree, but a slightly more detailed guide would be useful.

[jjkiuru]

For the time being, posting a table like this would help:

60 min:  400 pax or less
55 min: at least ___ pax
50 min: at least ___ pax
45 min: at least ___ pax
40 min: at least ___ pax
35 min: at least 1000 pax ?
30 min: at least ___ pax
25 min: at least ___ pax
20 min: at least ___ pax
15 min: at least 4000 pax ?
10 min: at least ___ pax
05 min: at least ___ pax


The problem with finding out by ourselves is that it takes a game year to bring up the RI, to know what is causing the low or fluctuating LFs.

I've done a samekind of table for myself. And another problem is that route planning screen gives you only estimates of the demand(usually ~90% accuracy in beginning), which I think is realistic.