OnCourse Software

martinlest wrote:

The debug_monitor.log, yes?

There is another issue, which it would be good if you'd look at as well while you are reading the log file. I was not cleared to descend further than 8000' as I approached EGAA. ATC told me, about 20 miles from the airport, to turn to 280 degs for rwy25 (about right), but to descend on the ILS from 8000'. At that close distance, totally impossible of course. If I was cleared and missed it, I am not getting any nags at all. My FAF is set at 7 miles and 2500'.

I circled away at 17.05 (time) and started to descend at 17.11, as you'll perhaps see in the log..

Again, had this issue (as have others apparently) before - at different locations. ATC stops giving descent instructions at some point.

Will attach log very shortly (have to go get it from my FS PC).

M

One of the problems that TGS in all its forms has to contend with is the accuracy of the afcad files. As Dave says whatever is in makerwys is read. So if the information in makerwys is not entirely accurate then that inaccurate information is passed on. It is not uncommon to come across broken taxiway links, undefined taxiways, wrong taxiway formats etc., (if you have a runway taxiway link instead of a normal taxiway link this could deceive TGS into thinking has arrived at the runway) all these can create problems. So really the first port of call if the TGS is giving you duff information is to check the afcad file and check that a. All the taxiways "are" linked. b. That they are linked with the correct link form and c. They have correct designations. Also make certain that you pushback facing the right way! Then if you still have a problem with TGS post it here with the logs files and a description or image of the intended taxiway route.

OK, well I'll check out that AFCAD in some detail, see if I can find any problems...

See here - sorry this has turned into a bit of unintentional cross posting!!!

viewtopic.php?f=8&t=1894&p=10761#p10761

martinlest wrote:

OK, attached

If the problem is the last wypt XXX being too high then lower it in the waypoint adjustment page.

No, the previous waypoint is a long way back and I am asked to descend to 8000' in good time. The past few flights it is the descent to a reasonable altitude to intercept the glideslope that comes way to late to act upon.

Thanks.

martinlest wrote:

The debug_monitor.log, yes?

There is another issue, which it would be good if you'd look at as well while you are reading the log file. I was not cleared to descend further than 8000' as I approached EGAA. ATC told me, about 20 miles from the airport, to turn to 280 degs for rwy25 (about right), but to descend on the ILS from 8000'. At that close distance, totally impossible of course. If I was cleared and missed it, I am not getting any nags at all. My FAF is set at 7 miles and 2500'.

I circled away at 17.05 (time) and started to descend at 17.11, as you'll perhaps see in the log..

Again, had this issue (as have others apparently) before - at different locations. ATC stops giving descent instructions at some point.

Will attach log very shortly (have to go get it from my FS PC).

M

Fixed this one in 3.1.3 which should be with you later today

Thanks again

Happened with me in 3.14 early this afternoon from EGLL-LOWW, have noticed 3.15 is available will try again on Tuesday.

I had to reinstall PF3 completely and one of the things I can't get right now is TGS - I don't get anything at all when I start taxiing.

I no longer use the stand-alone TGS display gauge, just rely on voice prompts (and on a really good day, the in-cockpit gauge springs to life too). But I have no audio prompts now. Could someone kindly remind me how to get this facility back? I have all the boxes ticked in Options 1/TGS. I have a vague feeling I have forgotten something (but have forgotten what it could be!!).

Please attach your latest log Martin

Sent from my phone using Tapatalk