This was a bit strange

Author

Message

JohnY

Post subject: This was a bit strange

Posted: Wed May 17, 2017 3:57 pm

Offline

Posts: 471

Joined: Mon Jul 18, 2016 3:42 pm

I planned a flight from LFBO Blagnac,Toulouse to LEMD Barajas, Madrid and the first thing I found was NO TGS.

Never-the-less, it was easy to find the runway. When I got there, Suzy (my co-pilot - I thought she should have a name) got us cleared to take-off.

That was ok and the flight was uneventful until we got approach for a Non ILS runway. I pressed 2 and got the usual message 'We'll check' and got nothing further. So, then they routed us to runway 18 - a non ILS runway. Then they re-routed us to 36R, again a non ILS Runway. I pressed 2 again and got routed to 36R an ILS runway and landed on that. Then, presumably no Parking spots available, I got 'Taxi to Terminal'.

I don't mind this and I'm not a complaining but some of the instructions don't seem logical to me. What do you think?

Log attached so you can tell me what I did wrong.....again!

John

Attachments

debug_monitor.zip
(402.08 KiB) Downloaded 141 times

Top

Profile

Quote

Dave March

Post subject: Re: This was a bit strange

Posted: Wed May 17, 2017 6:26 pm

Site Admin

Offline

Posts: 6197

Joined: Mon May 18, 2009 6:22 pm

Location: Sawtry, Cambridgeshire. UK

Contact: Website

The missing taxi instructions at you departure was due to there being some problem with the taxiway data... undoubtedly the afcad file. Here's the entry from the log... the first routine failed when it was unable to find an unbroken path to the runway (Error 8)

Code: Select all

17/05/2017 13:48:12: 600 - Get Taxi instructions #1 for Runway 14 Left
17/05/2017 13:48:12: 680 - Call Route: LFBO,43.6213769834129,1.38019411586858,43.6373672485352,1.35759699344635
17/05/2017 13:48:39: 930 - Route Found: 8@[]
17/05/2017 13:48:39: 930 - Error from GetRoute: 8
17/05/2017 13:48:39: 930 - #1 End: 13:48:39
17/05/2017 13:48:39: 930 - #2 Start: 13:48:39
17/05/2017 13:48:40: 430 - Oceanic: False - UPIC_Connected: True
17/05/2017 13:48:40: 440 - 
17/05/2017 13:48:40: 440 - SayPFSentence:- RadI\pfchat519B,pfclick
17/05/2017 13:48:40: 440 - 
17/05/2017 13:48:40: 440 - Transcript: 'stand by  '
17/05/2017 13:48:40: 460 - FS Screen :  stand by

So then we give the second routine a go and again this now complained about an invalid taxiway point

Code: Select all

17/05/2017 13:48:43: 520 - Get Taxi instructions #2 for Runway 14 Left
17/05/2017 13:48:43: 620 - Call Route: 72,G685
17/05/2017 13:48:44: 340 - Invalid TO Point!
17/05/2017 13:48:44: 340 - #2 End: 13:48:44
17/05/2017 13:48:44: 340 - No Full Taxi Instructions Available!

Have you added any new scenery to this area/airport recently. If so did you run MakeRwys and did it complete without error. Finally did you rebuild the PF3 database.

The problem with requesting an Instrument approach but getting nothing confirmed by ATC is a bug was the first thing I fixed in readiness for the next release, which will hopefully be by the end of the month.

_________________

Cheers

Dave March

Email: dmarch@oncourse-software.co.uk

I don't know if my memory is getting worse as I get older...
...I just can't remember how it used to be!

[ img ]

Top

Profile

Quote

JohnY

Post subject: Re: This was a bit strange

Posted: Thu May 18, 2017 10:35 am

Offline

Posts: 471

Joined: Mon Jul 18, 2016 3:42 pm

Ok - Thanks for the explanation Dave.

I haven't installed any new scenery since I ran Makerways and PF3 Data Base.

Great news that you're issuing an update at the end of the month that will fix that Instrument Landing request error because I, for one, really need that with some of the 'planes I fly and the equipment I have.

All the best.

John

Top

Profile

Quote

OnCourse Software

PLEASE NOTE: