OnCourse Software

Very strange... still working fine here. I wonder if it's another call sign issue?

I don't think the call sign issue was relevant to me (I checked at the time): I just use 'Speedbird', 'Air France' or whatever. The log started working again after I installed the beta mentioned above - not due to anything I did AFAIK. Seemed as if you'd fixed it.. Now it's stopped showing any text again.

Ok, so I start a new flight, minutes after typing the above - and suddenly I am getting text in the com log window. Task now is to find out which variable is responsible. What is the 'low down' again on the callsign?

Well next time it doesn't work let me know what call sign you were using

The previous couple of flights, where it didn't work, it was set to NONE (as the callsigns don't exist in PF3).

Dave, I spent a bit of time testing this tonight and it is indeed a callsign issue.

If there is one (a callsign, that is, e.g. Aegean, Speedbird, Shamrock etc. etc.), then the COM log shows the ATC text just fine. If there is no callsign however, so ATC just leaves it blank and reads back the flight number only (i.e. the value in the pf3_callsigns.dat file is 9999, 98) then no text appears in the COM log, as I suggested in my previous post here. I tried this with a number of airlines with and without callsigns programmed into in PF3 and it was true for every one. Callsign exists in PF3 = COM log working; Callsign absent in PF3 = no text in COM log. So if you choose 'None' in the callsign list, then there's no text in the COM log window.

I attach the log (I restarted PF3 between each test, so not sure how much useful information it gives).

Thanks for that Martin... very helpful. I'm out till mid/late afternoon today but will try and check this out on my return

Something that "might" help, Martin.

I know I'm using a different simulator to you but if I don't have a call sign I set the callsign to "None" and the flight number to something like "BX123", using the two letter IATA code for the airline. For me, at least, this avoids the issue you are experiencing.

John

Hi, thanks. Do you mean that if you don't prefix the flight number with the IATA code, you too get an empty COM log window? Or is it something else?

Hoping Dave can find the problem and is able to fix it... I never had this issue until one of the betas a few months ago, the log window always used to fill up with text no problem, callsign or no.

... I tried 'None' for the callsign and used a valid IATA code before the flight number, but it made no difference. I only get text in the COM window if there is a working callsign in PF3.