Did you try my suggestions with my post above?

2 hours ago, netshadoe said:

Did you try my suggestions with my post above?

Indeed, try to set MSFS General Options --> Accessibility   "Skip-preflight cinemetics" ON

What I find weird is that stationary aircraft look dark from a distance, but when you come closer in drone mode the Cabin and Logo lights switch on...

Edited September 17, 20241 yr by kiek

The AI fix lighter was for AIG it does not change the pb with lights. And its from SU5...So very old.

I will try to skip preflight and tell u here if I see anychange.

I just landed LIMC and I see psxt live traffic,  some with lights some with no lights (no matter IVAO MTL or JustFligh AI).

I was on VATSIM and all AI have lights .

Will report if something new

11 hours ago, HewPilot said:

I was on VATSIM and all AI have lights .

Will report if something new

That's the third time in this thread that you tell about your experience with VATSIM ...

Report something new indeed 😉

 

So change preflight cinematic setting dont change anything.

Yesterday did a flight LFMN-LFPO, lot of planes around me shown in radar, and some very next to me seen from the window. No Lights.

Thats sad and annoying.

As I record my flights stream I can tell that when the issue was resolved in previous version,  you can see all planes with lights. 

So please Nico investigate in this way something change in coding. 

For now psxt by night seems unusefull.

1 hour ago, HewPilot said:

For now psxt by night seems unusefull.

Well you have TCAS that is more important than looking out of the cockpit window. And remeber, if you see an aircrfat you're probably too close by 😉 

And again, nothing has changed in the coding of the AI lights in PSXT over the last ten years... It is an MSFS/Asobo issue

Edited September 18, 20241 yr by kiek

but in last few update you resolved something which correct lights AI your on Release Note.

Now I use only FS TRAFFIC JUST FLIGHT package as it seems more AI have lights day and night so thats better.

But I also see some AI with lights off.

10 minutes ago, HewPilot said:

but in last few update you resolved something which correct lights AI your on Release Note.

Yes that was a blinking light issue, caused by a change in SimConnnect. It had nothing to do with the normal lights control.

okay so that was blinking.

Will try tonight with only FS TRAFFIC JUST FLIGHT and report my night flight

i’m also experiencing planes with lights off in the air

It’s very inconsistent

Some planes have full lighting while taxing and some have no lights in the air

It’s impossible to pinpoint what triggers that

They are nonexistent in other AI‘s like FSLTL on the ground but all work in the air .

(I am using same models)

mike

exactly same like me

So tonight flight LIRF to LFPO with only Fs traffic package.

I think all aircraft I met in flight had lights. 

So dont know if there is issue between IVAO MTL and PSXT compatibility. 

May investigate this way and see 

Hewpilot 

8 hours ago, HewPilot said:

So dont know if there is issue between IVAO MTL and PSXT compatibility. 

The thing is, there is no such thing as "Aircraft package <-> PSXT compatibility", because they don't talk to each other; in between is the SimConnect API.  

PSXT generates SimConnect API calls.  Aircraft packages (in their models) implement SimConnect API calls.  Aircraft package must be compatible with SimConnect. However, how come that these packages in other contexts (VATSIM, AIG stand alone, FSLTL,  ..)  perform differently?

What role does MSFS/Asobo play? It is all very weird ...

 

 

may be IVAO package connect in different way with their Altitude software as I can see lights when using IVAO. or VATSIM. 

But may IVAO with simconnect so with MSFS have incompatibility. 

I have to confirm but major of JUST FLIGHT FS TRAFFIC seems to work with lights. And Im happy with because by flight night its amazing to see real aircraft with psxt during cruise .

Like many PSXT users, I've noticed recurring inconsistencies with the lighting behavior, especially after the recent updates. While lighting issues have always been around, they seem to have been amplified in the latest PSXT version. So, I decided to dive deep today and investigate.

After a few hours of testing, I discovered that the issue seems to be tied to a recent change in PSXT, which increased the aircraft injection rate to 4 per second instead of 2. This change has amplified an existing SimConnect issue, leading to the lighting problems.

Now, instead of my usual lengthy and complex breakdowns, I'm getting straight to the point this time.

@kiek, I’m convinced that introducing a 500ms to 1-second delay before setting the lights on newly created aircrafts could solve all of these lighting issues. The idea is to allow models and textures to load properly before attempting to control the lights. No delay is needed afterwards to control the lights, only the first time when the aircraft is injected.

In my test code, I used the Sleep() function like below, but not sure if it's even possible to sleep PSXT and what impact it might have.I guess you'll figure that out.

Spoiler

case SIMCONNECT_RECV_ID_ASSIGNED_OBJECT_ID:
    {
        SIMCONNECT_RECV_ASSIGNED_OBJECT_ID* pObjData = (SIMCONNECT_RECV_ASSIGNED_OBJECT_ID*)pData;

        switch (pObjData->dwRequestID)
        {
        case REQUEST_ADD_AIRCRAFT:
            DWORD newID = pObjData->dwObjectID;
            printf("\nCreated new id = %d", newID);
                    
            Sleep(1000); // will only delay lights coming up. Have not impact on spawning other aircrafts.

            hr = SimConnect_AIReleaseControl(hSimConnect, newID , REQUEST_REMOVE_AICONTROL);
            hr = SimConnect_TransmitClientEvent(hSimConnect, newID , NAV_LIGHTS_SET, 1, SIMCONNECT_GROUP_PRIORITY_HIGHEST, SIMCONNECT_EVENT_FLAG_FAST_REPEAT_TIMER);
            hr = SimConnect_TransmitClientEvent(hSimConnect, newID , LANDING_LIGHTS_SET, 1, SIMCONNECT_GROUP_PRIORITY_HIGHEST, SIMCONNECT_EVENT_FLAG_GROUPID_IS_PRIORITY);
            hr = SimConnect_TransmitClientEvent(hSimConnect, newID , TAXI_LIGHTS_SET, 1, SIMCONNECT_GROUP_PRIORITY_HIGHEST, SIMCONNECT_EVENT_FLAG_GROUPID_IS_PRIORITY);
            hr = SimConnect_TransmitClientEvent(hSimConnect, newID , STROBES_SET, 1, SIMCONNECT_GROUP_PRIORITY_HIGHEST, SIMCONNECT_EVENT_FLAG_GROUPID_IS_PRIORITY);
            hr = SimConnect_TransmitClientEvent(hSimConnect, newID , BEACON_LIGHTS_SET, 1, SIMCONNECT_GROUP_PRIORITY_HIGHEST, SIMCONNECT_EVENT_FLAG_GROUPID_IS_PRIORITY);
            hr = SimConnect_TransmitClientEvent(hSimConnect, newID , CABIN_LIGHTS_SET, 1, SIMCONNECT_GROUP_PRIORITY_HIGHEST, SIMCONNECT_EVENT_FLAG_GROUPID_IS_PRIORITY);
            hr = SimConnect_TransmitClientEvent(hSimConnect, newID , LOGO_LIGHTS_SET, 1, SIMCONNECT_GROUP_PRIORITY_HIGHEST, SIMCONNECT_EVENT_FLAG_GROUPID_IS_PRIORITY);
    }    }    

 

Would you be up to try it out?

If anyone’s curious, I’d be happy to share the thought process that led me here!

Cheers,

Amine.

Edited September 20, 20241 yr by vcaptain747