I am testing PSXT 16.7.0 with RealTraffic Direct in MSFS 2020.

PSXT injects live AI aircraft successfully through SimConnect. My little app receives the aircraft callsign, title, object ID, position, altitude, heading, ground speed and on-ground state.

However, route information is missing for some aircraft. For example, WZZ822_ is visible and taxiing, but no origin or destination is available. With FSLTL, the same type of information was previously available through the FSLTL log/parser.

Could you clarify whether PSXT exposes the following information for injected AI aircraft through SimConnect or another supported interface?

- ATC origin airport

- ATC destination airport

- departure and arrival airports

- flight plan or route string

- SID/STAR, if available

- aircraft registration

- source/provider metadata

- a stable identifier linking the aircraft to the RealTraffic flight

Specifically, should we read SimConnect variables such as:

- ATC ORIGIN AIRPORT

- ATC DESTINATION AIRPORT

- ATC FLIGHT NUMBER

- ATC ID

or does PSXT provide this information through another API, log, file, named pipe, network endpoint or RealTraffic data interface?

I do not want to infer or guess the route from the callsign, nearest airport, LNM data or aircraft position. We need to know whether the route is actually available from PSXT/RealTraffic and how it should be retrieved reliably.

If route data is not available for every injected aircraft, what is the recommended way to distinguish:

1. route data genuinely unavailable,

2. aircraft injected without a flight plan,

3. temporary data loss,

4. an aircraft that has been removed or replaced?

My application only needs the data for observation, display and traffic classification. It must not control PSXT aircraft or make assumptions when origin/destination data is missing.

Best reg

Patric

Lots of questions...

Let me tell you what PSXT injects via Simconnect then you can draw your own conclusions.

To spawn an aircraft PSXT uses this call:
SimConnect_AICreateNonATCAircraft( l_hsimconnect, p.title.c_str(), p.callsign.c_str(), position, requestId );

The title is the title of the livery in the aircraft.cfg file, the position is a SIMCONNECT_DATA_INITPOSITION

After the AI aircraft is succesfully created a very simple flightplan, consisting of origin (IATA) and destination (IATA) only is attached to the objectid. This is what you may see in LNM (and in the Log.txt of course)

Note that origin/destination may not always be available in RealTraffic, or even wrong; you will often see updates in these values on the fly, if GUID changes is ticked in the UI.

That's all there is ...

regards,

Nico

Edited October 4Oct 4 by kiek