FsLabs A320 FSUIPC Nav Light Issue

[THY4216]

I read the Fslabs compatibility guide in documents folder. I followed each step correctly. Everything works fine except navigation light. The other lights are working fine. They turn on/off when I press the assigned button but navigation light doesn't turn on/off. I have to press the assigned button for 4-5 times to toggle it. Has anyone had this problem? If yes, is there any solution for that? Thank you.

[artuncs]

We've completed all updates relating to FsLabs and unfortunately there is nothing more we can do. Many pilots experience issues with the beacon light. I have not heard many about the navigation light. You may be doing something wrong. I don't have experience with FsLabs but once they see a pilot using FsLabs, I'm sure they will write for help.

[THY4100]

I am using a lua script to solve my light problems. I had a persistent NAV Light On issue.

It also allows you to switch lights from 3D cockpit without FDR aircraft systems pop up but I highly recommend keeping aircraft systems on all times for monitoring.
It has a version which guesses baro reference from reading the capt. side knob, it works fine for me but I can't guarantee it being reliable. So again, keep FDR aircraft systems screen on. Redundancy is always a good practice in aviation.

I also have to say, this is literally the unapproved method from Turkish Virtual. Apparently it was too sketchy/not reliable enough to be official fix.

So your mileage may vary.

https://drive.google.com/open?id=1B4LPc ... CIbRqTxGOU

[THY3716]

Actually we didnt know somebody came up with a solution for this issue. If you are sure it works, just send it to us so that we can put the file into the downloads.

[THY4216]

I am using a lua script to solve my light problems. I had a persistent NAV Light On issue.

It also allows you to switch lights from 3D cockpit without FDR aircraft systems pop up but I highly recommend keeping aircraft systems on all times for monitoring.
It has a version which guesses baro reference from reading the capt. side knob, it works fine for me but I can't guarantee it being reliable. So again, keep FDR aircraft systems screen on. Redundancy is always a good practice in aviation.

I also have to say, this is literally the unapproved method from Turkish Virtual. Apparently it was too sketchy/not reliable enough to be official fix.

So your mileage may vary.

https://drive.google.com/open?id=1B4LPc ... CIbRqTxGOU

First of all I would like to thank you. With the help of this script my lights and baro ref work like they should. I've only noticed that I sometimes can not turn landing lights on/off. Do you have any idea about that problem? What may cause that?

[THY4100]

We don't have access to landing light switch positions, FSLabs' LVars are really limited. They stated they will open more with a SDK, but it will require an additional professional license(!).

What we can read is "L:FSLA320_landing_lightX_vis" which is light visibility from individual landing lights (1 & 2). So it is for animation and/or graphics. When both landing lights are "shining" it should set FSUIPC offset "on" and when any of them is off it should set offset "off".

This problem never happened to me but my guess is that it can be related to graphics. Wild guess, maybe FSLabs doesn't set these LVars accordingly when we don't see the lights. Or maybe lights themselves are not working properly.

You can try to power the aircraft, go to external view and check if the lights are extended/on. Note that sometimes lights extending takes some time, they will be lit once they are fully extended. If offset (therefore FDR) is not in sync with visual state of the lights then we can conduct a further investigation. But I am very doubtful we can do much with this limited access to aircraft systems.

Until FSLabs provides a better access to aircraft systems keep your keybinds to lights, QNH and monitor FDR's pop up.

Finally, you are more than welcome, I wish I could do more.

[THY4216]

We don't have access to landing light switch positions, FSLabs' LVars are really limited. They stated they will open more with a SDK, but it will require an additional professional license(!).

What we can read is "L:FSLA320_landing_lightX_vis" which is light visibility from individual landing lights (1 & 2). So it is for animation and/or graphics. When both landing lights are "shining" it should set FSUIPC offset "on" and when any of them is off it should set offset "off".

This problem never happened to me but my guess is that it can be related to graphics. Wild guess, maybe FSLabs doesn't set these LVars accordingly when we don't see the lights. Or maybe lights themselves are not working properly.

You can try to power the aircraft, go to external view and check if the lights are extended/on. Note that sometimes lights extending takes some time, they will be lit once they are fully extended. If offset (therefore FDR) is not in sync with visual state of the lights then we can conduct a further investigation. But I am very doubtful we can do much with this limited access to aircraft systems.

Until FSLabs provides a better access to aircraft systems keep your keybinds to lights, QNH and monitor FDR's pop up.

Finally, you are more than welcome, I wish I could do more.

Thanks for the suggestion !