Penalties

[Quantum]

Hi DK,

My observation on landing light penalty is that it seems to give you only one penalty per flight.

Take-off without lights on I get message saying I have penalty for lights off below 1000ft. I keep lights off, climb to 2500ft (short flight) then descend and land. I expected another landing light penalty as I passed 1000ft in descent but didn't get one.

When I get into a faster aircraft I'll try testing the exceeded speed penalty.

I see we have a new penalty for parking brake, are there any more new ones we should know about?

Regards

John

[DaKurt]

Those are our penalties so far:

#define PY_TAXI 0 //Overspeed while Taxiing
#define PY_WRONGAIRPORT 1 //Landing at wrong airport
#define PY_CRASH 2 //Crashing
#define PY_ROLLING 3 //Rolling after pressing the "end flight" button
#define PY_PARKINGBREAKS 4 //Parkingbreaks after pressing the "end flight" button
#define PY_LANDINGLIGHTS_ON_OVER_10000 5 //Landing Lights on above 10500 feet
#define PY_LANDINGLIGHTS_OFF_UNDER_1000 6 //Landing Lights off under 1000 feet
#define PY_OVERSPEED 7 //>250 under 10.000
#define PY_OUT_OF_FUEL 8 //Aircraft ran out of fuel in flight

I strongly recommend you to wait for the penalties check untill tomorrow. I just recoded the penalties in this moment and will upload a new version with an improved penalties tomorrow ...

Every penalty is only recorded once in a flight. It is not possible to get the same penalty twice ...

[hezza]

#define PY_OUT_OF_FUEL 8 //Aircraft ran out of fuel in flight

Hi.
Many times I see a/c for sale with absolutely no fuel despite having been flown.
IMO the most likely explanation for this is having the engines-stop-when-out-of-fuel option disabled.

Is it possible/desirable to add a penalty (reputation) for "Aircraft with zero fuel at end of flight" ?

EDIT, never mind, as there is also a crash penalty then it seems that the above penalty is in fact what I was asking for

G.

[CAPFlyer]

There is also code in our cheat detection software that runs on the server to detect this situation which will mark the flight as possibly cheated. If so, we can not only set the flight as cheated, but also charge the airline for the proper amount of fuel for that flight (done by a calcutation based on several factors that has proven to be pretty reliable).

[alasizon]

Possibly I am misunderstanding this penalty but after you click end flight, wouldn't your flight be over and the client stop recording?

Parkingbreaks after pressing the "end flight" button

[Quantum]

It basically detects that you had not set the parking brake when you ended the flight and gives you penalty.

Rgds

John

[Quantum]

Hi,

Isn't not setting parking brake and rolling after end flight the same error?

If he doesn't set the parking brake he may roll so an error
If he rolls he hasn't set the parking brake so an error.

Sounds like the same error to me so why penalise twice. Also as you have pressed 'end flight' would the roll after pressing end flight be detected anyway. I think just leave the parking brake error in as that does get detected before you press end flight.

Regards

John

[hezza]

Isn't not setting parking brake and rolling after end flight the same error?

It seems to me they are not quite the same.
Rolling means that the pilot has declared the flight closed before the a/c has come to a stop.
Parking brake not set could be after the a/c has stopped, but the pilot has not completed the shutdown checklist very thoroughly.