OnCourse Software

I took my first couple of PFE flights and things went pretty well. It's going to take some getting used to, as I've been using Radar Contact for years, but overall I'm impressed and glad I decided to try it.

I ran into one problem with both flights, which departed from different airports. I'd get clearance to taxi the runway, TGS is on, VCP in mode 3. I get to hold short point and TGS confirms this and shuts off. I'm sure I'm at the correct runway and well within 700 feet of it. VCP contacts tower and requests takeoff, and tower never responds. There is no ai approaching the airport or on the runway. I tried several time pressing 6 to repeat the takeoff request, but no response. I think I may have heard just the slightest bit of static, as if a sound file were trying to play. I tried C+S+D to turn off ai detection, and again repeated the request. Still no response. I finally just lined up and took off, tower handed me off to departure, and the rest of the flight went normally. If it makes any difference, the plane I'm flying is the PSS Dash-8. I had no other problems.

Maybe this section of the debug log will be of some use....

4/27/2013 6:59:35 PM: 740 - SayPFSentence:- ProFlightW\pfchat122E,ProFlightW\pfac97E,ProFlightW\pf5E,ProFlightW\pf5E,ProFlightW\pf7E,ProFlightW\pf7E,ProFlightW\pfchat247E,ProFlightW\pf3E,ProFlightW\pf5E,ProFlightW\pfatc12E,ProFlightW\pfchat312E,pfclick
4/27/2013 6:59:35 PM: 750 -
4/27/2013 6:59:35 PM: 750 - Transcript: 'Tower US Air 5577 runway 35 left ready for takeoff '
4/27/2013 6:59:54 PM: 140 - --> TargetHDG set to 185
4/27/2013 6:59:54 PM: 140 - --> subPlayDigits called with value: 185
4/27/2013 6:59:54 PM: 140 - --> subPlayDigits called with value: 6
4/27/2013 6:59:54 PM: 140 - --> subPlayDigits called with value: 35
4/27/2013 6:59:54 PM: 140 - --> TargetHDG set to 310
4/27/2013 6:59:54 PM: 140 - --> subPlayDigits called with value: 310
4/27/2013 6:59:54 PM: 220 -
4/27/2013 6:59:54 PM: 220 - SayPFSentence:- ProFlightW\pfac97B,ProFlightW\pf5B,ProFlightW\pf5B,ProFlightW\pf7B,ProFlightW\pf7B,ProFlightW\pfchat96B,ProFlightW\pf1B,ProFlightW\pf8B,ProFlightW\pf5B,ProFlightW\pfchat71B,ProFlightW\pf6B,ProFlightW\pfchat247B,ProFlightW\pf3B,ProFlightW\pf5B,ProFlightW\pfchat88B,ProFlightW\pfchat125B,ProFlightW\pfchat559B,ProFlightW\pf3B,ProFlightW\pf1B,ProFlightW\pf0B,pfclick
4/27/2013 6:59:54 PM: 220 -
4/27/2013 6:59:54 PM: 230 - Transcript: 'US Air 5577 Winds 185 at 6 runway 35 Left Cleared for takeoff fly heading 310'
4/27/2013 6:59:54 PM: 530 - Error in NET SaySentence: Error in the application.
4/27/2013 6:59:54 PM: 530 - Loop kicked: 16
4/27/2013 6:59:54 PM: 530 - C:\Programs\PFE\FS2000\ADV\Wav\ProFlightW\pfchat559B.wav
4/27/2013 6:59:55 PM: 590 - --> TargetHDG set to 310
4/27/2013 6:59:55 PM: 590 - --> subPlayDigits called with value: 310
4/27/2013 6:59:55 PM: 690 -
4/27/2013 6:59:55 PM: 690 - SayPFSentence:- ProFlightW\pfatc36E,ProFlightW\pfchat559E,ProFlightW\pf3E,ProFlightW\pf1E,ProFlightW\pf0E,ProFlightW\pfac97E,ProFlightW\pf5E,ProFlightW\pf5E,ProFlightW\pf7E,ProFlightW\pf7E,pfclick
4/27/2013 6:59:55 PM: 690 -
4/27/2013 6:59:55 PM: 700 - Transcript: 'Roger Cleared for takeoff. fly heading 310 US Air 5577'
4/27/2013 6:59:55 PM: 770 - Error in NET SaySentence: Error in the application.
4/27/2013 6:59:55 PM: 770 - Loop kicked: 1
4/27/2013 6:59:55 PM: 770 - C:\Programs\PFE\FS2000\ADV\Wav\ProFlightW\pfchat559E.wav

You have some missing audio files which is usually due to a bad installation.

Please download and instal the latest cumulative updates package from our support forum, when installing please ensure you stop ALL other programs, especially your anti virus and any other security type programs you might have.

If you're running Windows Vista or later do NOT instal into the default "c:/program files" folder, because Windows regards that as a protected area and will prevent certain files being written and/or updated. I appreciate the installer defaults to that location but the publisher wrote the instal script long before Vista hit the shelves.

Sent from my Dumbphone

I'll do as you suggested, Dave. On the next flight I made after I posted about this problem, it worked fine.