Thank you guys for the kind words! Glad it worked 🙂 .  Thanks go to Nico as well for being open to our suggestions as always. 

By the way, Nico was  abosolutely right about MSFS interfering with AIG light. Those of us using outaded AIG package (mine is 2 years old) won't notice it, but if one is running with recent AIG packages, than the behavior Nico was describing become noticebale. 

It seems that AIG have introducing a new light logic (a model behavior in MSFS words ) to automatically control their arrcrafts lights based on certain simvar conditions. Lights are switched ON and OFF if conditions are met, instead of controlling them manually as PSXT an other programs do.  This logic can be found in this file: \Community\aig-aitraffic-modelbehavior\ModelBehaviorDefs\AIG\Lights.xml

Let's take a look at an example code from that file:

Spoiler

<!-- Strobe Light -->
      
                (E:TIME OF DAY, number) 3 == if{ (A:AMBIENT IN CLOUD, bool) 0 == (A:GROUND VELOCITY, knots) 21 &gt; and (&gt;K:2:STROBES_SET) } els{ (A:GROUND VELOCITY, knots) 21 &gt; (&gt;K:2:STROBES_SET) }
           

 

The above code checks if the TIME OF DAY equals 3 (not sure why though).

• If true, it checks whether the aircraft is not in a cloud (AMBIENT IN CLOUD = 0) and the ground velocity is greater than 21 knots. If both conditions are true, the strobe lights are turned on.
• If the time of day is not equal to 3, it checks only the ground velocity. If it is greater than 21 knots, the strobe lights are turned on.

 

 

On 9/22/2024 at 2:43 PM, kiek said:

How do you explain that there are AIG aircraft that have strobes on/off during taxiing while PSXT does nothing with the strobes? 

@kiekI remember in the original version of this text, you mentionned aircraft taxiing with stobes on, then off when aircraft is taking a turn, then back on again. It sounded strange back then, but now it makes perfect sense!   

We know that PSXT sets the aircrafts airspeed SIMVAR to have turning wheels. What's happenning is that:

• when an aircraft is taxing at a speed higher that 21 knots, MSFS automatically swithes the strobe lights ON, thinking it's in an a takeoff roll.
• When it comes to a turn, it is normal for the airspeed to drop bellow 21kts, so strobe are turned OFF by MSFS.
• Once it exits the corner,  and speed increases beyond 21 kts again , the strobes are ON again by MSFS.

PSXT isn't involved in this.  it’s all down to those fast and furious pilots !  🙂  (though 21 knts is not that fast)

What I did is I renamed the file, edited layout.json to not load it and removed any reference to it in common.xml in same folder . The other untested solution is to edit the Light.xml file to remove all lights section except for LOGO light.

In the end, I was right about the delay, and Nico was right about the MSFS interference! We were both initially unconvinced by each other's theories, but now we've come to agree and ended up uncovering and solving not just one issue, but two.

The final piece of the puzzle is now solved.

Happy flying !

Cheers,

Amine.

 

 

 

Edited September 25, 20241 yr by vcaptain747

17 minutes ago, vcaptain747 said:

 The other untested solution is to edit the Light.xml file to remove all lights section except for LOGO light.

PSXT is controlling the LOGO lights too, so maybe its better to go for an "empty" Lights.xml file

7 hours ago, kiek said:

PSXT is controlling the LOGO lights too, so maybe its better to go for an "empty" Lights.xml file

Genius, Nico and Amine! Thank you, thank you, thank you! I have emptied the Lights.xml file and now everything looks a lot better.

23 hours ago, kiek said:

PSXT is controlling the LOGO lights too, so maybe its better to go for an "empty" Lights.xml file

is there any line to remove for MTL IVAO ? 

 

Thank you

On 9/25/2024 at 3:55 PM, vcaptain747 said:

Thank you guys for the kind words! Glad it worked 🙂 .  Thanks go to Nico as well for being open to our suggestions as always. 

By the way, Nico was  abosolutely right about MSFS interfering with AIG light. Those of us using outaded AIG package (mine is 2 years old) won't notice it, but if one is running with recent AIG packages, than the behavior Nico was describing become noticebale. 

It seems that AIG have introducing a new light logic (a model behavior in MSFS words ) to automatically control their arrcrafts lights based on certain simvar conditions. Lights are switched ON and OFF if conditions are met, instead of controlling them manually as PSXT an other programs do.  This logic can be found in this file: \Community\aig-aitraffic-modelbehavior\ModelBehaviorDefs\AIG\Lights.xml

Let's take a look at an example code from that file:

  Hide contents

<!-- Strobe Light -->
      
                (E:TIME OF DAY, number) 3 == if{ (A:AMBIENT IN CLOUD, bool) 0 == (A:GROUND VELOCITY, knots) 21 &gt; and (&gt;K:2:STROBES_SET) } els{ (A:GROUND VELOCITY, knots) 21 &gt; (&gt;K:2:STROBES_SET) }
           

 

The above code checks if the TIME OF DAY equals 3 (not sure why though).

• If true, it checks whether the aircraft is not in a cloud (AMBIENT IN CLOUD = 0) and the ground velocity is greater than 21 knots. If both conditions are true, the strobe lights are turned on.
• If the time of day is not equal to 3, it checks only the ground velocity. If it is greater than 21 knots, the strobe lights are turned on.

 

 

@kiekI remember in the original version of this text, you mentionned aircraft taxiing with stobes on, then off when aircraft is taking a turn, then back on again. It sounded strange back then, but now it makes perfect sense!   

We know that PSXT sets the aircrafts airspeed SIMVAR to have turning wheels. What's happenning is that:

• when an aircraft is taxing at a speed higher that 21 knots, MSFS automatically swithes the strobe lights ON, thinking it's in an a takeoff roll.
• When it comes to a turn, it is normal for the airspeed to drop bellow 21kts, so strobe are turned OFF by MSFS.
• Once it exits the corner,  and speed increases beyond 21 kts again , the strobes are ON again by MSFS.

PSXT isn't involved in this.  it’s all down to those fast and furious pilots !  🙂  (though 21 knts is not that fast)

What I did is I renamed the file, edited layout.json to not load it and removed any reference to it in common.xml in same folder . The other untested solution is to edit the Light.xml file to remove all lights section except for LOGO light.

In the end, I was right about the delay, and Nico was right about the MSFS interference! We were both initially unconvinced by each other's theories, but now we've come to agree and ended up uncovering and solving not just one issue, but two.

The final piece of the puzzle is now solved.

Happy flying !

Cheers,

Amine.

 

 

 

Do I need the light fix for MTL IVAO ?

I just noticed a pinned message about lights' fix for AIG planes. Keep in mind that this fix should be apply after each AIG model update as it happens quite often (1-3 times per quarter)

2 minutes ago, G-YMML1 said:

I just noticed a pinned message about lights' fix for AIG planes. Keep in mind that this fix should be apply after each AIG model update as it happens quite often (1-3 times per quarter)

I know.

My first idea was to let PSXT overwrite that file with an empty file, which is ofcuorse a lot easier and lots of users may forget to update the file. However, if users want to use their AIG models/liveries with the AIG traffic manager too, I cannot do that.

 

2 hours ago, kiek said:

My first idea was to let PSXT overwrite that file with an empty file, which is ofcuorse a lot easier and lots of users may forget to update the file. However, if users want to use their AIG models/liveries with the AIG traffic manager too, I cannot do that.

You could maybe make PSXT check the content of the Lights.xml at startup and display a warning if its content is not emptied and/or add a check box to Override AIG light Control , that if checked would make a backup of the original file than overwrite its content, and reverse the action if the check box is not ticked.

Edited September 26, 20241 yr by vcaptain747

3 hours ago, HewPilot said:

Do I need the light fix for MTL IVAO ?

No. That fix applies for AIG only.

If you're seeing some IVAO airplanes models taxiing with TAXI lights OFF , but nav and logo ON , that's due to issues in the model and lights definitions in systems.cfg.   

You can always try to use the Light Fix tool with IVAO and see if it makes any diffrence.

Edited September 26, 20241 yr by vcaptain747

Hi man, just tested no difference.

I have some models without any light but I think thats model issue with IVAO MTL.

Thank you. 

Hewpilot 

13 hours ago, vcaptain747 said:

You could maybe make PSXT check the content of the Lights.xml at startup and display a warning if its content is not emptied and/or add a check box to Override AIG light Control , that if checked would make a backup of the original file than overwrite its content, and reverse the action if the check box is not ticked.

See this nice solution offered by AIG

 MSFS: Lights fix for AIG aircraft package - PSXseeconTraffic for FSX | P3D | MSFS - The AVSIM Community

 

Using AIG and FSLTL with priority to AIG - FSLTL only for models not available with AIG.

It seems the lights issue is not completely solved. I see NO position lights on any parked aircraft, live or static...also no position lights on aircraft on takeoff roll, or landing roll. The only time I see position lights is on aircraft in the air. Position lights = the red and green lights on the leading edge of the wingtips and in most cases white lights on the trailing edge of the wingtips. At least with live parked and while taxiing position lights should be on. During takeoff, flight, and landing strobes should flash

From the PSXT manual:

4.7   Nav Lights while parked.
Default: true
Navigation lights of static and live parked aircraft will be on.

I am assuming "Nav lights" = the red and green wingtip lights.

11 hours ago, somiller said:

Using AIG and FSLTL with priority to AIG - FSLTL only for models not available with AIG.

It seems the lights issue is not completely solved. I see NO position lights on any parked aircraft, live or static...also no position lights on aircraft on takeoff roll, or landing roll. The only time I see position lights is on aircraft in the air. Position lights = the red and green lights on the leading edge of the wingtips and in most cases white lights on the trailing edge of the wingtips. At least with live parked and while taxiing position lights should be on. During takeoff, flight, and landing strobes should flash

From the PSXT manual:

4.7   Nav Lights while parked.
Default: true
Navigation lights of static and live parked aircraft will be on.

I am assuming "Nav lights" = the red and green wingtip lights.

Try toggling the Nav Lights checkbox a few times.

And if that does not help, there must be a problem at your end.

I think the light effect loading still needs to be delayed slightly

After very tedious observations I clearly can see on some models lights loading or not depending on some thing so what I did is I observed a specific model without lights and then very quickly restarted PSXT and the lights came on on that model.

I have definitely observed  different behavior after restarting very quickly

 

mike

5 hours ago, mike stryczek said:

I think the light effect loading still needs to be delayed slightly

After very tedious observations I clearly can see on some models lights loading or not depending on some thing so what I did is I observed a specific model without lights and then very quickly restarted PSXT and the lights came on on that model.

I have definitely observed  different behavior after restarting very quickly

 

mike

Hi, 

I confirm and see this behaviour.

Some models dont have but major of them are okay so I dont want to add work to Nico.

But yes I think it can just be adjust as I restart psxt same model can appear with lights. 

I confirm major of them have lights just a few (either JustFlight models or IVAO) dont have. 

Thanks 

Hewpilot