[POLL] Wich difficulty setting you will use ?

[DanSteph]

I hesitate beewteen setting light and altimeter penality to "difficult"
or "no penality" by default (the first time you launch FsP)


POLL:

1-Will you fly with altimeter set to difficult or no penality ?
2-Will you fly with light penality set to difficult , simple or no penality ?

Explainaition of those settings:

Realistic light penality: (Works as in real world)
-beacon must be turned ON when an engine is about to be started.
-strobe and landing light must be turned ON when you leave taxi way and enter the landing strip.
-landing light must be turned OFF above FL100 and ON under FL100.
-strobe and landing light must be turned OFF when you enter the taxi way after flight.
-beacon must be turned OFF only after you have shutdown all the Engines.
-nav ligth must be ON during the entire flight.

Simple light penality:
-Landing lights must be turned ON under FL100 and OFF above FL100

No Light penalty:
-No checks are made and you don't get any penalities for inproper light use.

Altimeter realistic penality:
If this option is set to realistic you will have to set you altimeter setting as in reality:
bellow FL180 (18'000 ft) you must ask ATIS station and set it accordingly to the
current pressure, above FL180 you must set it to standart pressure 1013/29.92.
Otherwise FsP don't check and you don't get any penality for inproper use.

Thanks,

Dan



Post Edited ( 05-14-05 04:02 )

[pagir]

As beta tester, I tried to be serious enough to manage lights... But I failed... In fact, I think it's important... Maybe simple light penalty?...

For the altimeter, it's much simplier...

Pagir

[DanSteph]

I set light penality to simple also otherwise I get penality all the time LOL...
but it's true I make almost all my flight just for testing the current feature I'm working on...

PS: If you fail it's perhaps because the explainaition of how you must set them your light not clear enough ?

in this case heres is a complete flight:

1-all light off
2-turn beacon and nav ON
3-start your engine
4-start to taxi to landing strip
5-just before entering landing strip set STROBE and LANDING LIGHT to ON
6-when passing above 10'000 ft turn OFF landing light
7-when passing below 10'000 ft turn ON landing light
8-land
9-before taxiing to the gate turn OFF landing light and strobes
10-shutdown engine
11-turn OFF all light.

If you start a flight with engine already ON simply make sure beacon are ON and STROBE and LANDING are OFF
before starting the FsP flight...

Dan



Post Edited ( 05-14-05 04:14 )

[JaWood]

So are you getting penalties for simply forgetting your lights, or because it's too sensitive (i.e. you turn off your landing lights at 10,100 ft and
get penalized for having them on above FL 100.) I'd like to be able to use the realistic settings, and so be it if I get penalized every once
and a while I suppose.

The way I see it, FsP should look at flight offences in two categories:

1.) Offences that cause disruption to the passenger's comfort or convenience, or that put passengers in harms way. Examples might
include a hard landing, overspeeding, excesive G forces, etc.

2.)Offences that are in violation of airline or avaition procedure, but don't nesecarilly affect the passengers opinion of the airline.
If you forgot to turn off your landing lights until half way through your flight, or fly without you nav lights on during the day, the passengers
won't know, nor will they care.

So I think type 1 penalties should be much more severe than type 2 penalties. And I think type 2 penalties should hardly affect the reputation of the
airline (as far as passengers are concerned anyways.)

[DanSteph]

I'm glad to announce that this is the case....

There is two kind of penality in FsP:

1-penality that disrupt your passengers comfort (typically G excess, bank angle, hungry passengers etc etc)
2-penality that violate flight rules or enfreign aircraft good managment (light, altimeter, flaps, 250kt under 10'000ft)

So passengers don't care at all about light barometer setting flaps or speed under 10'000 ft
as long as you don't shake them and land safely you can end with 100% satisfied passengers
but -5000 point for your pilot and fee for your company...

In contrary you can end with +3000 point for your pilot and 10% satisfied passengers (you had a bad failure
but you landed safely for example... (one can't expect a passengers to be satisfied with one engine
broken and the crew announcing an emergency landing)

About severity it depend of the fault in fact... some fault of type 1 may give more penality than type 2
but it's not always the case... in fact usually type 2 give more penality than type 1
(a small stall for example... for passengers they just had a slight feeling of G in somes case
while this is an extremely bad case for your pilot... one pilot that would stall at low altitude without any failure
hardly deserve anymore the licence of ATPL in reality)

In fact with all penality set to hard I end more often with 100% satisfied passengers (because I didn't shaked them)
but pilot penality point and fee for the company... (because I forgot flaps, light, altimeter or exceeded speed
limit)

So we can resume like that: your company healt depend more of passengers advice on your flight
and your pilot rank and promotion depend more of how went your flight... that seem logical...

About light and other penality, of course there is "safe" range and you will not get a light penality
if you don't set them at 10'001 (in fact internaly it happen at 12'000 ft... 2'000 ft should be large enough
for you to click a switch) all penality are like that, there is a marge that allow you to not jump on things
right on the number.... When FsP give a penality your really outpassed the limit.

Dan



Post Edited ( 05-14-05 05:40 )

[JaWood]

About light and other penality, of course there is "safe" range and you will not get a light penality
if you don't set them at 10'001 (in fact internaly it happen at 12'000 ft... 2'000 ft should be large enough
for you to click a switch) all penality are like that, there is a marge that allow you to not jump on things
right on the number.... When FsP give a penality your really outpassed the limit.

Ok, this is good to know. At this point I'll just have to see how I handle realistic vs. easy settings. I'm glad you're at least giving the option
of changing the dificulty, so as we're not stuck on one setting having to suck it up and deal with it.

One other question. Do you know if Flight Simulator can be set to load all flights with the plane's panels cold and dark, so we can start the engines
up ourselves? I can see a possible problem of constantly getting beacon light penalties because MSFS flights default with the engines running AND the
beacon light off.

[Deacon]

Couldn't agree more with JaWood. If I had the time to truly plan everything, including a detailed walk-around, I suppose I'd also have the inclination
to flip every switch when necessary. Sometimes I do, but in general I'd rather spend time in the dynamic environment with ATC and other traffic as
opposed to concentrating on some of the relatively insignificant (simming-wise) requirements of proper lighting. So I'd use No Penalty.

Altimeter settings is something else entirely. Totally dynamic and required. At transition altitude it goes to STD and vice versa on the way down.
Here I would use Realistic Penalty.

[jeffrey11190]

2

[DanSteph]

JaWood wrote:
up ourselves? I can see a possible problem of constantly getting beacon light penalties because MSFS flights default with the engines
running AND the beacon light off.

In this case you have to prepare your aircraft BEFORE starting your FsPassengers flight... (I explain below)

internally it work like that for beacon and landing light:

1-FsP set immediatelly an beacon penality if one engine is runing with beacon OFF
2-FsP set immediatelly the landing light penality if you have parking brake set and landing light ON (parking brake are for ... parking)

To explain: beacon are extremely important for ground crew so they know that an engine is about to be started or running (deaf ?)
and landing light is more a "polite" usage.. so you get higher penality for beacon than for for landing light and strobe...


So with complexe light penality there is two possible case:

1-Your aircraft start with black cockpit
2-Your aircraft have already engine running as you said

In case 1 nothing to do, all switch are supposed to be OFF so you start a normal start checklist
wich suppose in reality that you switch beacon ON before the engine start...

In case 2 you must first set strobe and landing light OFF and beacon ON THEN only you start the FsP
flight... in this case no penality, FsP is satisfied, beacon are running and landing light are off...


This said if you set to "difficult" the light and barometer you might better have a check-list wich include
that because you will forget something too often otherwise... The copilot can help because he announce
when you pass 10'000 feet and FL180...

So two kind of flight style: "precise checklist" or "relax flying"

Notice a third one is possible: "relax checklist"
You set altimeter to difficult and light to "simple" in this case you
have only barometer setting and you must only turn ON/OFF landing light
when you pass 10'000 ft this is "semi realistic"

Dan



Post Edited ( 05-14-05 06:14 )

[sniperscout75]

Dan, I will fly with all settings set to difficult, I like to make it as real as possible. Cant wait for release, keep up the good work, Jimmy

[georak]

I think if someone uses a proper checklist, nothing should be forgotten during flight. I myself make simplified chechlists for every aircraft I
fly. They may not be official, but I include all practical things that should be done or taken care of, in order not to forget such things. This way
I think the only question is: in real aviation, would a pilot be detected for not using proper altitude and lights setting? I he/she would, than
lets have penalty, and if he/she wouldnt, than the whole question is theoretical. isnt it?

GEO

[DanSteph]

georak wrote:
I think the only question is: in real aviation, would a pilot be detected for not using proper altitude and lights setting? I he/she would, than
lets have penalty, and if he/she wouldnt, than the whole question is theoretical. isnt it?

Well, that's a game vs reality question

Dan

[jboweruk]

Hotseat makes some of the ground light penalties easy to avoid. But that 10K Landing light one will always do me, is there a way maybe
we could set the penalties individually as we see fit? Or is that a little too much to ask?

[DanSteph]

Sorry no way for this anyway the copilot call 10'000 feet and FL180 so his voice my remind you
that you must do something... (you can disable those call btw)

Dan

[Japo32]

In Europe the transition hight is not FL180 is just 5000 ft (if I don't remember bad). Almost in all europe... so if we put that penalty..
and we are flying in europe then we will have allways penalty.

Maybe in Asia and Africa is different also (don't know) so it would be a good idea to define by yourself (the player) the transition of
altimeter, depending where are you flying.