kiek

>Only small portion of RT planes is shown, Are you sure you miss RT parked? Do you see more in the Radar screen? If so it might be caused by lat/lons that do not match with stands in your airport file. You can check that in log.txt. I will look into that when I am home from vacation. >if this option is selected that results in departing AI simply popping on a taxiway instead of pushing out from gates. That has really nothing to do with RT parked traffic. RT parked is about static parked, not live parked

In PSXT you can 'block' an aircraft, so it disappears, then you can take its place in the sequence

I assume that I would not see dumb take offs or landings on the wrong runway (or the wrong end of a runway) with PSXT? No you would not, because they represent their real live counterparts with a delay of 30 seconds.

See FAQ #14

Looks like a commercial to me. And that for a first post ;-)

A slightly different ICAO code means a different ICAO code. If you now follow the matching rules again, with this in mind? What would happen? EDiT: PSXT does not have the concept similar airline ( like similar model) However it does know the difference between airline and operator, if applicable and defined in its dbase.

No support, no updates, no TBLO processing till June 8th Please help each other. Enjoy the traffic!

Maybe a next project? :-) Btw that board was generated by ChatGPT's codex. "He/she/it" converted my website into a modern look, and good visible on mobile devices, in say 45 minutes. Really amazing what AI can do.

That all depends on your parameters (target %, max fit, week, soft, ..... read all about it in the manual), and how many models/liveries you have installed. Btw you do not need to press park now. Parking goes automatically. Only if you change some parameters and want to see the effect immediately, then you press Park

Welcome to PSXT! That download problem is already soved. See this thread Please re-download 15.3.0 from my web site, install and run an airports scan.

Hi, I see the problem. .... oops. For airports that do not have a version attached, like INIBUILDS KPSP, I forgot to make the change from .xml to .enc. Stupid of me. But now fixed. Please download 15.3.0 from my web site, and re-install. Hope to hear the good news soon :-) Nico

No, no misunderstanding at all: EJU95ZU_ FCO->FRA EJU B736 =6= JustFlight_AI_737-7_White The first callsig has a trailing _ meaning it is a ghost, and may be replaced later by the right livery (without an underscore). That ghost had B736 and because your matching depth allowed it it became a =6= match. Later the correct callsign became availabe and the aircraft was correctly re-matched. If you don't want to see this, set depth at <= 3

Please read the Manual about matching, or FAQ #33

Well, you probably do not have a B736 instaleld ... Please pay attention to this: How to hide large texts when posting - PSXseeconTraffic for FSX | P3D | MSFS - The AVSIM Community

See my other post. Exit PSXT and restart.

Don't think it is related to my updates, cause nothing has changed. It is more likely caused by SU5. Don't know what the problem is. However, I've improved the robustness of the SimConnect airport scan, with graceful recovery from exceptions. So hopefully your scan will continue. Could you download and install 15.2.2 again from my web site and test it? Thx.

I have tested at EGCC and the RT Quality data has improved a lot, average and deviation figures around 4. Balt has made some changes too.

I will add that average for a sessio

And other models not? Then it is likely an RT issue. PSXT treats all models the same.

Thx for letting me know, will do.

YES! or just run a scan for airports. Please next time do not post large amount of text. Use the spoiler function to hide it. You can read how to do that in one of the pinned posts of this Forum ( at the beginning).

You were talking a Indeed, but especially gap_sd. And if gap_max <= 30 seconds you will not have any freezing.

Delete the contents of ../airports/my_thirdparty, but it should not be necessary.

Hi guys, Although it is Ascension Day, I have added a continuous test to monitor the quality of the RT traffic data. Quality here means whether data arrives regularly and continuously. I am not testing the validity of parameters such as altitude, latitude, longitude, and so on. Large gaps between incoming data updates can cause aircraft on the ground to enter a holding state for the number of MaxHoldingMinutes you have set in the UI. After every 15 RT data batches received, roughly every 1 to 1.5 minutes, you will see something like this in the message line of the UI (and in Log.txt): RTQ samples : 1674 gap_avg : 5.2 gap_sd : 4.1 gap_min : 1.0 gap_max : 44.6 Interpretation : samples: 1674 → number of update intervals collected during the aggregation period (15 * the number of aircraft in a data batch) gap_avg: 5.2 → average time between actual RT updates gap_sd: 4.1 → variability of update intervals (= standard deviation) gap_min: 1.0 → shortest observed update interval gap_max: 44.6 → longest observed update gap Gap times are expressed in seconds. They represent the difference between the timestamp of newly received data and that of the previous data packet. Do note that you need to measure for at least an hour or so to obtain meaningful results. The 15.1.2 version of PSXT (MSFS) with this monitor can be down loaded from here. This update only contains the .exe, just overwrite your existing one. Nico