Landing lights detection failure with PSS A319

[CAPFlyer]

John, I guess we'll just have to disagree on this issue then. It's not a matter of changing it not affecting those who aren't affected by it now. It's a matter of by changing the rules it DOES affect all users because it means that those whom have no problem operating within the current requirements of the client and are dinged when they do forget to operate within the limits (i.e. they forget to turn on or off the landing lights) now won't get dinged for forgetting them because the limits have been made too easy for them.

As for the terrain issue - there's a simple fix for it everyone seems to just ignore and was proposed when it first started cropping up - when the client enters "cruise" mode, the landing light penalty is disabled. That way, if you're cruising close to mountains, it won't ding you for not having your lights on since you're in "cruise". It even works for step climbs and descents because if you watch the client, it will change from "cruise" to "climb" or "descent" when it detects a sustained climb or descent and then return to "cruise" when it detects that you've leveled off.

[Quantum]

I guess so Chris. I personally have no problem with the lights as-is but offered it as suggestion for those that did have issues. Re the terrain issue, it's more for the high elevation airfields where your approach on the glide path starts above FL100 and have a very small window of opportunity for switching the lights on once below FL100. There's one airfield in Bolivia or Colombo (can't remember exactly) where the field elevation is just short of 9000' AMSL so the 1000'agl limit for lights to be on only gave me a couple of hundred feet window between penalty conditions. Not sure how Konny is going to deal with that but I'm guessing he'll maybe have to raise the upper limit to clear all possible airfields.

Rgds

John