voske

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.

This is how I did it:

No issues here with the Anniversary update. Just had to register the 777 again.

The normal cruising speed of the Constellation was about 280 knots, according to what I can find. Also, the planned duration includes taxi times.

According to the legend, flights PA130 and PA131 were flown with the Lockheed Constellation and the others with the DC-4. Also, the times are local times according to page 17 and 18 of the timetable. Time in New York is GMT-5 and time in Bermuda is GMT-4. Keeping that in mind, you get the following result. Planned duration of the direct flight from New York to Bermuda DC-4: 4h05m Constellation: 3h15m Planned duration of the direct flight from Bermuda to New York DC-4: 4h35m Constellation: 3h50m