vcaptain747

You havn’t mentioned live either. Which models are you using( AIG, FSLTL, JustFlight, IVAO) ? If AIG, are you using the last updated models? Amine.

Hi, I believe the 2 seconds delay was introduced for live aircrafts only, so it’s normal to have static aircrafts without proper lights if the model was not previously loaded. Setting the same delay for static aircrafts would fix that, but that remain Nico’s choice. Cheers, Amine.

NonATCAircraft , that's what PSXT uses and that's what i use in my tool.

Hi @Kaiii3, I've worked on the lights issues with Nico, the developper of PSXT, and the results may give you some pointers. Hope it helps, Amine.

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.

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.

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: 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.

On my end, when using FSLTL or Just Flight models with PSXT version 8.2.0, all aircrafts --whether parked or in flight—have proper lighting. This is not the case with version 8.1.1. I understand the reason, but it seems I haven’t quite succeeded in convincing you yet (I knew from the start it wouldn’t be easy 😄). I'll make one more try. Let's say PSXT is injecting these aircrafts in this order when it first starts: 1. FSLTL B737 KLM 2.FSLTL B787 ACA 3. FSLTL B767 DHL 4. FSLTL B787 KLM 5. FSLTL B737 AFR 6. FLSTL B777 ACA 7. FSLTL B777 KLM With version 8.1.1, the results on my end would be like this: 1. FSLTL B737 KLM : NO LIGHTS as this is the first time the aircraft model B737 is loaded , so it load with a delay and light commands have no effect except on simvar) 2.FSLTL B787 ACA : NO LIGHTS as this is the first time the aircraft model B787 is loaded 3. FSLTL B767 DHL :NO LIGHTS as this is the first time the aircraft model B767 is loaded) 4. FSLTL B787 KLM :PROPER LIGHTS, because a B787 have been loaded already (model is in cahe), so there is no loading delay and light commands are received after the model is fully loaded) 5. FSLTL B737 AFR : PROPER LIGHTS, because a B737 have been loaded already (model is in cahe), 6. FLSTL B777 ACA : NO LIGHTS as this is the first time the aircraft model B777 is loaded 7. FSLTL B777 KLM : PROPER LIGHTS, because a B777 have just loaded (model is in cahe) Now, imagine that the last two B777s take off and go beyond the lateral range, so they get removed from the sim. About 10 seconds later (on my system), the B777 model gets removed from cache (likely due to MSFS memory management or another process. See 2:50 in the video for proof ). The next time a new B777 is injected (say, a landing aircraft), it won’t have proper lights. This happens because the B777 model is no longer in cache, and the sim needs to load it from the Filesystem again, causing a delay. With version 8.2.0, this issue is resolved, not a single aircraft with no light. Regardless of whether the aircraft is in cache or not, the 2-second delay allows enough time for the model to fully load, ensuring all aircraft have proper lighting. I can make a video comparing both versions live if needed. Yes, I confirm that no delay would work with the original AIG package without the light fix. Again , i'm was able to figure out why, but the explanation might sound absurd, so please be patient and bear with me. The reason the delay has no effect is that because AIG are by default loaded with their lights ON since they use the new lights system, same as IVAO. FSLTL and justFlight use the old model so they load with all lights off. If AIG models are in cache, you will see them come up with all lights on, but only if youinject them with the onground =1 or with altitude less then 391 above ground altitude . If the model is not in cache or 390 feet above ground altitude , then they load with lights OFF visually , but still all light SIMVARs are ON. The thing is, when the simvar are set to ON already, trying to set them ON again won't have any effect (tested with another tool). This is why the light are not showing even with a 2 seconds or any other delay value . The only way i'm able to inject AIG aircrafts with propoer lighting at any altitude was is cycle the simvars OFF then ON , then set the desired lights value. I know the 390 feet sounds absurd, but thats where all my testing led me to. Tried it in diffrent airports in the results is the same. At EHAM, ground altitude is -12ft if you inject with altitude= -12+390 = 378 lights show up, beyond that no light. At LULKA, ground elevation is 9330ft, so inject at altitude 9720 you will have light, 1 feet more and no light, and this goes on at every other airport i tested at. Using the code above, You can have proper lights at any altitude with AIG. Please give it a try. Also hoping the explanation above convinces you to bring the 2 seconds delay back, it's really making a diffrence on my end. I know it’s not the easiest post to read, so thank you for taking the time! Amine.

That's a LOD issue in the model.xml of some AIG aircrafts. For example, for 777-200 , you need to go to \Community\aig-aitraffic-oci-beta\SimObjects\Airplanes\AIGAIM_TFS_B777-200_PW\model.pw\TFS_Boeing_777-200PW.xml and change this: <LODS> <LOD minSize="60" ModelFile="TFS_B772PW_LOD0.gltf"/> <LOD minSize="45" ModelFile="TFS_B772PW_LOD1.gltf"/> <LOD minSize="35" ModelFile="TFS_B772PW_LOD2.gltf"/> <LOD minSize="25" ModelFile="TFS_B772PW_LOD3.gltf"/> <LOD minSize="20" ModelFile="TFS_B772PW_LOD4.gltf"/> <LOD minSize="10" ModelFile="TFS_B772PW_LOD5.gltf"/> <LOD minSize="5" ModelFile="TFS_B772PW_LOD6.gltf"/> <LOD minSize="1" ModelFile="TFS_B772PW_LOD7.gltf"/> <LOD minSize="0.5" ModelFile="TFS_B772PW_LOD8.gltf"/> </LODS> to this instead: <ModelInfo> <LODS> <LOD minSize="10" ModelFile="TFS_B772PW_LOD0.gltf"/> <LOD minSize="5" ModelFile="TFS_B772PW_LOD6.gltf"/> <LOD minSize="1" ModelFile="TFS_B772PW_LOD7.gltf"/> <LOD minSize="0.5" ModelFile="TFS_B772PW_LOD8.gltf"/> </LODS>

@kiekYou are right! I just tested that and confirm that for AIG, it makes a diffrance if the aircraft is injected on the ground or in the air . I'm unable to get any AIG aircraft in the air with lights using original package with no light fix.

Also, just wondering if any one noticed that FSLTL Taxi and Landing lights are swapped? or is it just on my end.

Sorry for the typo, its just one tool, the one that I created a while ago and shared in this forum.

Yes, thats what i get with the testing tools, and it is supported by Simconnect logs. Please check here, and if you can use the tool to confirm, it would be great. We need to find a pattern

Never noticed such behavior. That's because i'm using AIG model with the Light Fixer tools. AIG and IVAO MTL are both using the new MSFS light systems with electrical cuircuits, which have been proved faulty even by AIG developpers : https://www.alpha-india.net/forums/index.php?topic=43424.0 Using the tool , would see that AIG aircrafts without the light fix are loaded with all their lights on. What i think is happening, is that the aircrafts are reloaded during taxi (which happens when aircraft change callsigns ), so when respawned, they come back with all lights on, but not fast enough to apply the light commands. just a therory...

Hi HewPilot, Thank you for the kind words! Have you tried using the tool I shared in the OP. Can you please do and confirm if you see that initial aircraft loading delay when you inject only one aircraft, and if you see it with AIG only or with other models too. Thanks, Amine.

Hi Nico, I think 200ms is good when injecting multiple aircrafts. if you inject 5 in a row for example, simconnect would have waited a total of 1 second (200ms *5) before starting to handle the creation confirmations and controlling the lights. That's enough time for the aircrafts to load properly and have lights. In this scenario, the more aircrafts you inject in a row, the better the light results are. However, if you inject a single aircraft, then the 200ms is not applied, so simconnect would have waited only 35 msec before sending the light events, which is not enough for the aircraft model to load and show the lights on , even though light SIMVARs are showing the expected value. Off course, that might differ from one system to another. I agree.. and that might the cause of the issue. Simconnect is creating the aircraft and controlling it's light within the 35msec, but the graphic processor (or whatever it is called) is having hard time to catchup when loading the model I ran all my tests with a four years old i9-10850K running at 5Gh, not sure if it's still considered high end but I see light issues with AIG, FSLTL, just flight and IVAO MTL. For version 8.2.0 , can we have the 35msec delay increased to 2 seconds please in addition to the increase of the 200msec delay you mentionned ? I hope you're enjoyed the party 🙂 Thanks in advance! Amine.

Hi Nico, I made a video to show the lighting issues and share my findings with you. I know YouTube videos aren't really your thing, and I’m no YouTube star myself. But trying to explain this in text would’ve been like sending smoke signals in a windstorm — completely pointless! Here is the link to the tool I developed for testing : https://www.dropbox.com/scl/fi/k8qjefviywsv6dbk1nqkk/Traffic-Injection-Lights-Testbed.zip?rlkey=opttmfgbcuhdmesrgi3caqz7j&st=gx6b0her&dl=1 Cheers, Amine.