OnCourse Software

Quote:

No that shouldn't happen Martin but it does raise its ugly head now and again unfortunately

... keeps happening (not that often, true, but when it does, it's very odd in its effect )

I take it, from your reply Dave, there's no tweak you can make to prevent it?

Hi. Is there an option somewhere to turn off speed calls between FL140 (is it?) and FL100? The generic (i.e. same every flight) 'Reduce speed to 260 knots", or whatever, never matches speeds in my FMS and I'd far rather manage my speeds as I get close to 10,000' AGL myself - or let the autopilo...

Thank you

Quote:

This one has now been fixed and will be in the next beta

I guess you must be rather 'beta-ed out' after v.3.21!

Even so, just wondering when you might put the first one out for 3.22 Dave, as it would be good to have the com log showing properly again

Wow, Dave that's great!! Thank you

Yes, worth testing

... 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.

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...

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...

yes there is away to stop it...on Options #1 i believe,there is a tab called exclude voices and depending which voice you don't want just click on checkbox and hopefully you won't hear yourself again... Hi. I don't think the problem is with any particular voice: if I restricted any given one, chanc...