Just had a quick moment to do a more thorough test this morning before dashing out.
I have tried the stand-alone taxi gauge but I expect I need to RTFM as it tells me FS/TGS Not Active when they should be.
But I have looked closer at the tgs.gau readings, and those of tgs2.gau which seems to replicate the style of the stand-alone, and they are trying to show me the correct route - if I paid more attention to the "distance to turn" indications I probably wouldn't be led astray! But the fact remains that my FO is telling me to turn when I most definitely should not - see blue text and arrows.
I have modified the airport layout image I uploaded earlier to show (with a red "X") the locations that I believe the taxi system is not recognising, and the points where I am getting misleading verbal instructions. I'm still being guided by the gauges diagonally across the apron where other aircraft may be parked.
route.jpg (19.84 KiB) Viewed 13954 times
So from what you say, Dave, I think it is the guidance system itself, and not the gauges or verbal instructions, that is causing this by ignoring various "via" points. It is not unique to this airport, but I attach a copy of the AF2 file in case you or anybody wants to replicate the situation. (With no weather set you should be sent to the same runway).
If I pay more attention to the distance to turn indications on the gauges, I might make a better job of my trip to the runway, but if there is a way to fix it so that all the intermediate points are used (like I think things once were, a long time back) it would make things so much better.
Best regards,
John
PS - I can see there is a setting in PF3 to reduce the distance when advice is given before the next turn. Currently set at 150, I will reduce this to 75 or even 50 which should improve things.