OnCourse Software

Did you try stopping/restarting TGS Display/

Several times, Dave.

John

Sorry, Dave, here's another log.

Made another flight to EYVI and am pleased to say that I was told "gate" on arrival now that I have taken out those dubious taxiway links. That's one thing solved without you having to get involved.

However, once again I had verbal instructions only from the runway to the gate, no visual indications. In fact I cannot get the TGS Display to work at all. I loaded it right at the start of the flight and it showed the same error message throughout, I did try restarting a couple of times.

In Options 1, I do have "Use TGS" and "Visual Guidance" checked. Am I missing something the obvious somewhere?

Best regards,

John

Could you attach the TGSDisplay_Debug.log please. You'll find it in the same folder as TGS Display

Heading your way . . .

John

Thanks John. You've probably seen what the log says... 'Failed to connect to FS'. Quite unusual to say the least.

Please try the attached, if you have the same problem let me see the TGSDisplay_Debug.log again as it will now return the FSUIPC error

Thank you

Morning Dave,

No change with the new version, so here's the log. Looking at that, it is certainly trying. A bit like me, very trying! That's what my mummy used to say, anyway . . .

Hope you can make sense of it.

J

Hi John,

All I can say is FSUIPC is timing out whilst attempting to make connection with FS. I have no idea why that should be, but that's the returned error code. Just bizarre thet PF3 is not complaining about the same issue as they both use the common FSUIPC code.

I'll have to give this some more thought

Going back to the list on page 3:

johnhinson wrote: *

Fri May 17, 2024 11:14 am

1. The "Recent ATC Communication Log" is completely blank for the entire flight on about one in four occasions, at other times it works perfectly. I haven't managed to establish any factors that are causing this yet.

I think I have got to the foot of this one with some testing. The issue seems to be the flight number, if it has letters preceding it.

For instance, in the example I gave for the Fred Olsen airline, I set the Airline to "None" and the Call Sign (i.e. the Flight Number) to "FO252" in Options 1 as the airline name is not one of the range available in PF3. This works fine in PF3, the controllers always call me as Foxtrot Oscar 252, which used to be typical for many airlines that didn't have a designated callsign up until the 1970s, at least. I believe a few small ones still do.

Whilst this works fine from the ATC point of view, it seems the Recent ATC Communication Log cannot record messages if there are letters there. The tests I have made show that it works fine if the letters are omitted, for instance, just flying as "252" causes it to work correctly but of course this sounds odd and is not true to practice.

As I have said before, this is far from a "game-killer" for me, as the main part of PF3 works fine, but I am wondering if it would be possible to adjust the log system one day when I am not mathering you about taxi guidance.

Best regards,

John

Thanks John, that was very useful info and I've now fixed the bug and it will be in the next beta