09-08-2005, 07:58 AM
I read in another thread somewhere about how you can only serve 2 hot meals per flight. and that because of this, some long range
flights tend to have the Passengers go hungry prior to landing.
I have not yet made such a long flight ( 12 + hours )... Yet
But I was wondering how many sandwich services are there? is it also 2?
Assuming this is the case. 1 past suggestion made, was to add a 3rd hot meal. This would give 4 more Hours to the satisfaction time
rate.
Another inventive Idea made was to allow a sleep variant on long flights. Since many people would definitely sleep at some point during
a 16 Hour flight.
My idea... If not already mentioned.
Is to adjust the satisfaction time based on the company food quality setting.
Example:
A hot meal at 50 % quality would give us the default 4 hours satisfaction time.
A hot meal at 100% quality would give us 8 hours satisfaction time.
I mention 8 hours for 100%.. because I’m sure at some point FSP pilots have noticed when taking off shortly after dinner time will show
the attendant note: The passengers just ate and will be hungry in about 7 hours.
So I figure if they ate at the airport and then headed to the gate for security and baggage checking etc. etc. this would surely take up to an
hour. leaving the onboard pre takeoff number of 7 hour till hungry again.
<-- PS my attempt at meshing Real Life to FSP

Same with sandwiches:
50% = 1 hour
100% = 2 hours
And Drinks:
50% = a weak wine
100% = dern near moonshine.
Oops… 100% quality drinks may shoot the woozy factor to 8% instead of 4%... Insta drunk pax for our listening pleasure.
* Heard in the pilots lounge after a flight *
A380 pilot- “ You should have seen that last landing in our A380. We feather kissed the Ash fault “
737 Pilot- “ Oh yeah?.. Why don’t you kiss my Ash fault “
A380 Pilot- “ Flight attendant brought you some pretty strong drinks again huh? “
737 Pilot- “ nope just 2.. but the fog was thick when I landed.
Shakin up 737 Co-Pilot- “ What fog?!? You nearly went blind from those 2 drinks “
In any case.. would this be something that could be coded in the future upgrades? Or does our illustrious programmer have another fix in
mind already?
Meco
flights tend to have the Passengers go hungry prior to landing.
I have not yet made such a long flight ( 12 + hours )... Yet

But I was wondering how many sandwich services are there? is it also 2?
Assuming this is the case. 1 past suggestion made, was to add a 3rd hot meal. This would give 4 more Hours to the satisfaction time
rate.
Another inventive Idea made was to allow a sleep variant on long flights. Since many people would definitely sleep at some point during
a 16 Hour flight.
My idea... If not already mentioned.

Is to adjust the satisfaction time based on the company food quality setting.
Example:
A hot meal at 50 % quality would give us the default 4 hours satisfaction time.
A hot meal at 100% quality would give us 8 hours satisfaction time.
I mention 8 hours for 100%.. because I’m sure at some point FSP pilots have noticed when taking off shortly after dinner time will show
the attendant note: The passengers just ate and will be hungry in about 7 hours.
So I figure if they ate at the airport and then headed to the gate for security and baggage checking etc. etc. this would surely take up to an
hour. leaving the onboard pre takeoff number of 7 hour till hungry again.


Same with sandwiches:
50% = 1 hour
100% = 2 hours
And Drinks:
50% = a weak wine
100% = dern near moonshine.
Oops… 100% quality drinks may shoot the woozy factor to 8% instead of 4%... Insta drunk pax for our listening pleasure.

* Heard in the pilots lounge after a flight *
A380 pilot- “ You should have seen that last landing in our A380. We feather kissed the Ash fault “
737 Pilot- “ Oh yeah?.. Why don’t you kiss my Ash fault “
A380 Pilot- “ Flight attendant brought you some pretty strong drinks again huh? “
737 Pilot- “ nope just 2.. but the fog was thick when I landed.
Shakin up 737 Co-Pilot- “ What fog?!? You nearly went blind from those 2 drinks “

In any case.. would this be something that could be coded in the future upgrades? Or does our illustrious programmer have another fix in
mind already?

Meco