OnCourse Software

Great Dan. Thanks so much for helping!! I guess I am being a bit of a pain, but as I said, I am sure that some of the issues I am having can't be just because I am doing things wrong, and hopefully they will help other newcomers in the future. (I have read the printed manual, but not all of the pdf files. They make my eyes hurt!).

Now you will see there is a runway incursion issue! Hahahaha!!! (Manic laughter)

OK, I'll email PFE support about ATC pushing me in front of other aircraft, as it is beginning to spoil the whole FS experience, especially at FS9 ATC always gave 'hold short.. a/c on short final' instructions. PFE seems to be ignoring any AI traffic.

An easier question: I have looked and looked in the pdg files but can't find an answer.. I seem to recall that I checked a box somewhere that activated a black window with green writing on it which was the record of ATC transmissions. As ATC gave instructions, I could read it on this large window. It's not the ATC text window that comes up if you activate closed caption (that looks like the little frequencies window): this is larger and altogether more 'substantial'. How do I call up this window so that I can check back on the ATC conversation?

Hi Martin,

Not trying to disregard your concerns about the AI incursions but it might be best to let the experts help out with that issue.

On the second subject, you might be referring to the Say Again ATC Log, which can be configured to work with your "Say Again" hotkey (Ctrl+Shift+=). I think it will show the last 10 ATC commands. Check the User Manual, sections 7.3.3 and 8.56 (pages 73 and 99) for more info. (Apologies if I'm off the mark and you're referring to something else.)

Dan

I'll have a look re. 'say again' log. Got fed up with the ATC today: spent ages setting up a flight, FDC, AES, programming CDU etc. etc. then PFE ATC spoiled it all, firstly by letting me onto the runway then letting AI traffic both land on top of me AND allowing AI traffic behind me onto the runway too which then taxied right through my a/c.

To add insult to injury: I was taking off (or planning to) from Rwy 29 at VIDP. It has a huge threshold displacement and ATC had directed me right to the far eastern end of this. The take-off point is 1/3 of the way along and as I taxied along, ATC kept repeating 'taxi into position and hold', over and over - every ten seconds. I heard it easily 30 times by the time I got to the take-off point. Then an AI plane landed right in front of me... and I closed the whole thing down and turned off the PC!!!! I'm still in a bad mood !!!

Emailed support re. AI traffic issue...

M. (Oh, thanks for the reply!!).

There are a few settings on the Options #1 page of PFE that you might try to adjust, although I don't think they will completely eliminate your AI traffic problems. On the right side of the page are settings for "Hold for Jets" and "Hold for Props" which adjust your hold-short instructions when traffic is inbound:

Hold for Jets and Hold for Props - sets the distance at which you will be told to
hold for inbound traffic while waiting for takeoff clearance.

Experiment with the settings to see if there is any difference; you can always return the settings to their original values if you want. As I said though, this won't address all of your concerns.

Dan

Hi Dan, As you say, I don't think the problem is there, but I have tweaked the settings a little just to see. As I said to Dave M., I may just be unlucky in having chosen airports the past few days which have some innate problem (I have corrected some of them in the AFCAD), rather than the issue being with PFE or my settings.

There seem to be constant little 'niggles' though - some, if not most of which are probably due to the fact that I haven't got my PFE settings quite right. For instance, I am flying (as I type, on my other PC) a PMDG 747 from Bangkok to Hong Kong. When I got to the runway, ATC gave me a message which I didn't catch. (The $64000 question: did they say clear for take-off or hold short? I could see an aircraft coming in to land). I pressed the shortcut keys for 'Say Again'. Nothing... So I waited rather than go onto the runway, just in case. Then when the incoming a/c was down, I was told to line up: great, seems to be working! But why no repeat of the ATC message when I asked for it? Small niggle but one of many I seem to encounter. (I need to have the 'kneeboard' open so that I can check back what has been said - I have the option for ATC to be incomprehensible set very low BTW! If I can't rely on the 'Say Again;' function, I had best set it to zero probability).

Also ground traffic does stop when it crosses my path, but not before it has almost crashed into me (and sometimes too late!). That was an issue before PFE though - not sure if it's 'tweakable' soemwhere.

Hope no one at Oncourse sees this mammoth list of apparent problems as me whingeing about nothing! I've had quite a few other problems that I haven't mentioned and have been able to fic them myself. I guess when I have been using PFE longer, I'll feel happy with all it has to offer, as I do with FDC, which I tweak to my heart's content now!

.. oh, one other thing occurs to me. When other a/c are on short final, will PFE ask me to line up and hold, or to continue holding on the taxiway hold short point? If I am told to taxi onto the runway and hold, OK (is that real though? I can't remember from real-world ATC: may well be, given the turnover rate expected now at busy airports. But don't incoming pilots get fazed by seeing an aircraft actually holding on the runway? How do they know it's not going to start its take-off run?).

As long as I am not cleared for TO just as the a/c is about to touch down though, which has happened a few times (hence the post!).

Check the SayAgainOp entry in the [config] section of the PF_Emulator.ini file. I think this should be set at 2 if you intend on using both the ATC log and "say again" features:

SayAgainOp=2...will display the new ATC log showing the last 10 ATC commands PLUS you will hear the normal 'Say Again' request/reply.

(There is mention in the manual of setting this at 3 but I think that is a typo; I've set mine at 2 and it works.)

Dan

Dan,

Sorry, my fault. I meant I must get around to it!

I now have the entries like this:

SayAgainOp=2
AtcSayAgainLargeFont=1
AtcSayAgainNoFontResize=1
ShowAtcLog=1

Martin

Yes, the 'SayAgain' window now appears. The only problem is that it pops up behind my FS window (full screen) and causes FS to minimize to the Task Bar. I can't see a way to have it open on my second monitor. I have the (payware) Desksoft WindowManager installed but it doesn't recognise the SayAgain window. I suppose it is a pop-up window which doesn't have its own process?