a conflict with something else on my system, possibly my FS98 version of GB
Airports, which is a shame, as I've got some nice tracks for Heathrow and
It is possible that it may be related to a concerted aircraft not "taking"
properly. If you use FSTraffic, you'll know that the earlier version flatly
refused to convert aircraft with moving parts, wheras the latest version will,
but with mixed results. This is the likely cause according to the makers of
FSTraffic when e-mailed.
I use the FSD Seneca V as my default start-up plane, with Alexander Lawrence's
panel, and haven't had any problems myself.
I can avoid this problem by shutting off FSTraffic when over the UK.
Hope this gives you a few pointers,
Thanks for the reply, prompt as usual. I checked my FS Traffic folder and sure
enough the Playintf.dll (or player interface) was there. On checking the
configuration settings, I found it relates to the distance between the user
aircraft, and tracks involving either landing or departing aircraft. If the
distance is less than pre set parameters, the relevant track is discarded. On
each occasion the error has occurred, as I said, I happened to have the Seneca
V loaded, and I was flying from an airport in Australia I had designed using
Airport 2.6. I tried other aircraft at the same airport without any problem,
and I have flown the Seneca in other sceneries with no trouble. It would
definitely seem to be related to FS Traffic. I also have problems with FST
occasionally, but these seem to be aircraft related, as selective deleting of
some aircraft from the library within FST cures the fault. I also contacted
Lago and was given a similar reply to you, i.e., some aircraft do not "take"
Thank you again for your help,