OnCourse Software

Have a look at this will you please. The log shows the various attempts I made to get to the runway to take off but when I got there I still couldn't get clearance to take off. It just kept repeating instructions to go to the runway.

Thanks

John

If PF3 does not notice that you are at the holding point, use hotkey 6 (not 0) to ask for a take-off clearance.

PF3 thought the closest distance to your departing runway was 858, I think the unit is meters.

Tried hotkey 6 and got no response.

'PF3 thought the closest distance to your departing runway was 858, I think the unit is meters'
Don't know where it got that from, I was sitting there in my Phenom at the holding point not 50 yards away!

However, how's this for a theory? PF3 is probably based on the positions of the default FSX and P3D airports and runways. These are often wildly inaccurate. All my airports and runways in the UK, in much of Western Europe and the western states of the USA have been designed and accurately built in the right places geographically and correctly aligned by outside independent developers such as UK2000, Arm Computers, Scotflight, Blue Sky and several others others on to photographic sceneries.

Which possibly also explains how in quite a few instances, not only this one, the TGS has led me astray.

This is not the fault of the PF3 developers as it would be unreasonable to expect them to place their expectations on anything but the use of the default scenery. However it does mean that I will have to turn off the TGS altogether and try to find my own way possibly using the FSX and P3D taxi guidance system which, and I don't know how it does it, seems always to guide me correctly.

Unless that is, you can find a solution?

John

JohnY wrote:

Tried hotkey 6 and got no response.

'PF3 thought the closest distance to your departing runway was 858, I think the unit is meters'
Don't know where it got that from, I was sitting there in my Phenom at the holding point not 50 yards away!

However, how's this for a theory? PF3 is probably based on the positions of the default FSX and P3D airports and runways. These are often wildly inaccurate. All my airports and runways in the UK, in much of Western Europe and the western states of the USA have been designed and accurately built in the right places geographically and correctly aligned by outside independent developers such as UK2000, Arm Computers, Scotflight, Blue Sky and several others others on to photographic sceneries.

Which possibly also explains how in quite a few instances, not only this one, the TGS has led me astray.

This is not the fault of the PF3 developers as it would be unreasonable to expect them to place their expectations on anything but the use of the default scenery. However it does mean that I will have to turn off the TGS altogether and try to find my own way possibly using the FSX and P3D taxi guidance system which, and I don't know how it does it, seems always to guide me correctly.

Unless that is, you can find a solution?

John

Quite often this is a problem with the afcad file. Broken links, duplicated links etc. Some afcads try to be clever and have routes for incoming and outgoing AI over the same taxiways. Make sure your hold short limits intersect the runway. The number of times that holds are marked on the scenery taxiway but not shown in the afcad is legion and people pay for that!

JohnY wrote:

However, how's this for a theory? PF3 is probably based on the positions of the default FSX and P3D airports and runways.

If this should be the reason, just do a database rebuild from within PF3 options, and it will use whatever you have on your system

Edit: Another theory: The distance I found in the log is 858 feet, not 858 meters: Your aircraft was on the taxiway at the 0 position of the ruler, the end of the runway is 858 feet away.
I just verified in the log that PF3 expected you to be at the end of the runway.

But still Hotkey #6 should work, can you show us a log of that?

The above image doesn't seem to show a holding point on the taxiway either which doesn't help. So PF3 might not know your intention to enter the runway. Try adding a holding point to the afcad.

Thanks for the information.

The only log I had, I attached. I forgot to mention that I was VFR and even on the ground I find that somewhat different from IFR. Should it still respond to 6?

However, not to worry. I've just had a very successful IFR flight on the continent so I'm happy.

John

vololiberista wrote:

The above image doesn't seem to show a holding point on the taxiway either which doesn't help. So PF3 might not know your intention to enter the runway. Try adding a holding point to the afcad.

This was just a screenshot from Google maps, the holding point is a bit to the left: https://goo.gl/maps/RrgsB5NcvDK2

JohnY wrote:

The only log I had, I attached. I forgot to mention that I was VFR and even on the ground I find that somewhat different from IFR. Should it still respond to 6?

The log contains an IFR flight.
If there are Ground/Tower frequencies (or just Tower providing Ground services, too) Ground handling is the same for IFR and VFR.
If there is no Tower, you have to announce taking the runway on Unicom/Multicom (HotKey #6, too).

JohnY wrote:

However, not to worry. I've just had a very successful IFR flight on the continent so I'm happy.

By the way, in my default FSX version of EGTE the taxiway F exists, but is closed.
In the EAD chart (AERO INFO DATE 18 FEB 15) it is usable.
And PF3 did not tell you to use F, so if your add-on scenery includes a usable taxiway F, you still need to run the database update.

Thanks Thomas. You've just added a runway I never knew existed - F!.

I've never heard of runways being designated with a letter - only numbers.

The Exeter Airport I have is what it was exactly like in real life when the developer developed it. It's no doubt changed over the years but a couple of years ago I beta tested some changes and they were put into use with more to come. That never happened as what often happens the developer got involved in some stuff with both Scotflight and firm another now defunct. The result being that any more changes to Exeter are unlikely.

I also believe that UK2000 has made a new 'Extreme' version and I think Aerosoft has one so there's a few about all more than likely different from one another although the runways would remain unchanged. My version only has the one runway and I don't think there's a second defunct one shown.

Anyway, to get back to the main question. That holding point should never be and in real life isn't where your map shows it whatever Google may show. The real holding point is about 50 yards back and at right angles to the runway.

As I said, never mind. I'll go back to Bristol for my 'home' airport now.

John