OnCourse Software

In the noble, if futile, pursuit of flightsim perfection, can I ask... I thought that there was an algorithm (?) in PF3 which prevented the pilot and ATC voices being the same at any given time. Maybe not. Not vitally important, clearly, but it does sound a bit strange (like I am talking to myself -...

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

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?

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

I'm sorry to say that the COM log is no longer working. It did work for a while in the beta mentioned above. It opens automatically, but I haven't seen it populated with any text since the new full version

Martin

Everyone loves a bit of 'Schadenfreude'!

Hardly a 'deal breaker' but very strange that, as far as I recall, this has never worked for me. Maybe an 'X-Plane' thing??

Could also be people curious to see how I messed up my approach (since I mentioned that), not realising that only the privileged few can actually see it!

20 downloads of the log ... no ideas as to why I never get the no restriction call?

Fantastic work Dave (et al). Had a couple of great flights with this new version, with no PF3 issues at all (apart from the ongoing fact that ATC always waits until you reach your first climb altitude (if not FL250 or higher, when it doesn't happen) before giving a new one. Subsequently there's alwa...

No, nothing. Set to 100%, Checked the COM log onscreen too, no mention of 'No speed restriction'. Be interested to know what you see in the log.

(Don't look too closely at my approach BTW - HOLD went wrong, and then went overspeed... not usually so 'clumsy'! )