01-10-2006, 02:52 AM
Hi all; This was the fifth leg of a DreamFleet 727 trouble-free flight across the US. I'm using FSNav to plan, ASv6 for the weather, and, a week ago
purchased ImagineSim's KDEN, and then two days ago downloaded a freebee KSLC from AvSim. Apart from serving the booze a bit late (85% pax served) -
all was ok until I printed off the report - and then the above message, saying I had not landed at KDEN, and that some pax felt I should get a
-350-point penalty!!! Well - HUH!! I landed at KSLC. This was the destination indicated in the report header. KDEN is the departure
airport, and it plainly indicates this. I checked out the FAQ's, but this (below) is the only input on the subject.
"FsP ask the Fs2004 GPS about the closest airport when you end the FsP flight, so to check you may look at the Fs2004 GPS that will show you the
nearest airport when landed. This can help you detect 'fake' airport or other scenery problem."
If this could be the case - then Provo has an airport which is closer than Denver. I expect there are other airports around Salt Lake, too, so I don't
know how it could mistake Denver for Salt Lake. If I were to even suspect this after landing - how on earth would I be expected to think that I
could be at the wrong airport and to then check the MS GPS??? - (even if I knew what the MS GPS was). Is the FAQ talking about the Map view, or the
Garmin that comes with some of the aircraft.?? . and - (finally) - how do I "fix" my screwed-up flight. This takes some two hours from startup to
shutdown, plus the planning and printing involved - a three-hour time-slot that I've now basically lost. On top of this I now have to listen to my
wife's comments re my sanity. Any help REALLY appreciated. . .thanks..
purchased ImagineSim's KDEN, and then two days ago downloaded a freebee KSLC from AvSim. Apart from serving the booze a bit late (85% pax served) -
all was ok until I printed off the report - and then the above message, saying I had not landed at KDEN, and that some pax felt I should get a
-350-point penalty!!! Well - HUH!! I landed at KSLC. This was the destination indicated in the report header. KDEN is the departure
airport, and it plainly indicates this. I checked out the FAQ's, but this (below) is the only input on the subject.
"FsP ask the Fs2004 GPS about the closest airport when you end the FsP flight, so to check you may look at the Fs2004 GPS that will show you the
nearest airport when landed. This can help you detect 'fake' airport or other scenery problem."
If this could be the case - then Provo has an airport which is closer than Denver. I expect there are other airports around Salt Lake, too, so I don't
know how it could mistake Denver for Salt Lake. If I were to even suspect this after landing - how on earth would I be expected to think that I
could be at the wrong airport and to then check the MS GPS??? - (even if I knew what the MS GPS was). Is the FAQ talking about the Map view, or the
Garmin that comes with some of the aircraft.?? . and - (finally) - how do I "fix" my screwed-up flight. This takes some two hours from startup to
shutdown, plus the planning and printing involved - a three-hour time-slot that I've now basically lost. On top of this I now have to listen to my
wife's comments re my sanity. Any help REALLY appreciated. . .thanks..
pj
ASUS P5B, 4MB L2; Conroe Core2 Duo E6600 oc @ 3.0 gig/1366meg bus
ATI Radeon X1950XTX 512 meg DDR4; OCZ PC2-8000 2 x 1 gig DDR2 Platinum at 1gHz; Gateway 21inch at 1680 x 1050: Homebuilt yoke & pedals, throttle quadrant and 6-pack thrust levers
ASUS P5B, 4MB L2; Conroe Core2 Duo E6600 oc @ 3.0 gig/1366meg bus
ATI Radeon X1950XTX 512 meg DDR4; OCZ PC2-8000 2 x 1 gig DDR2 Platinum at 1gHz; Gateway 21inch at 1680 x 1050: Homebuilt yoke & pedals, throttle quadrant and 6-pack thrust levers