voske

I had the same issue with PSXT in "RT Direct" mode. Switching to "RT App" and using the RealTraffic app solved that for me.

Sorry, I wasn't clear: I'm putting them in a text file for them not to be used (and I compared the LiveriesScanned.xml before and after I put the liveries that I didn't want to be used in the text file, and that worked). Now I only have generic liveries for airline ZZZ.

Perfect, thanks! And now that I think of it, I can improve my chances of getting an actual generic livery by creating a text file in "my regcodes" and putting a lot of the stub liveries in there without a registration code.

Looking through my log file, I noticed something about the matching when it comes to cargo flights where the registration is not showing. Here is part of the log file: I have liveries for these cargo aircraft. Here is a part of the LiveriesScanned.xml (sorted in the same way as the log file): What seems to be happening, is that when the registration is missing, PSXT looks for a non-cargo livery, but can't find one (because these are cargo airilines) and therefore picks a non-cargo ZZZ livery. Is there anything I can do to make it pick a cargo livery?

It's an old topic, but the problem might have returned (in version 14.5.0 it selects MA17 when parked at gate A21). Slewing solved it though.

Now that you mentioned it, I realised that I'm stil running 11.0.1. Looking through the log file, I noticed this entry: "GetDlgItem failed for ID 32853" between my parameters. Just checked it, and it's also in yesterday's log file and the day before yesterday's log file. Parameters section of today's log file:

That's also what I meant, but I wasn't really clear (I added the correct parking spots for the traffic that departed/landed while I was parked in KDTW).

True. Coverage has improved, but still leaves a lot to be desired. But that's also why I noticed the problem: I had put some time in my learned airport file for KDTW to counter the bad coverage (by manually inputting the correct parking spots) and now I'll get to do that again ;).

That solved it, thanks!

I've noticed an issue with my learned airport files: the contents are overwritten every time the files are saved and it only keeps the most recent updates and not the previous updates. Is that supposed to happen or is there something wrong with my installation? For example, from my current log: 17:54:24 "airports\learned\thirdparty\INIBUILDS\KDTW.xml" saved with 3 updates and one or more parameter changes 20:01:55 "airports\learned\thirdparty\FlyTampa\KBOS.xml" saved with 88 updates Looking at those learned airport files, the KDTW file contains 3 updates (all day 6) and not the past updates (I've done quite a number of flights into KDTW in recent days). The KBOS file contains 88 updates (all day 6), and not the past updates. Edit: just returned to KDTW. Logfile says: 21:44:15 "airports\learned\thirdparty\INIBUILDS\KDTW.xml" saved with 6 updates Learned airport file contains 6 updates and doesn't contain the 3 updates from earlier today.

Perfect, thanks!

After updating to 10.7.9 I've noticed that on occasion traffic will suddenly disappear and not return. In those cases the log files show multiple lines with the same message: "===> traffic exception: narrowing_error". Once this error occurs, there will be no traffic until I restart PSXT. After a restart, traffic will reappear. However, the error might return after some time (sometimes a very short time, sometimes after hours). Is there anything I can do to prevent this from happening? I'm not sure whether it's relevant, but I'm flying the Inibuilds A350. Log file also includes:

I don't believe the distance to the TOD is the issue, but the distance to the airport: I've seen this happen with the Fenix on two STARs where the TOD is quite early (LENDY8 into KJFK and ROBUC3 into KBOS).

I've seen similar things happen. Looking through the log file and the airport files, I found that aircraft overflying the airport while I was parked there, were saved by PSXT in the airport files as parked aircraft.