OnCourse Software

I see from the runways.txt file generated by makerwys that EGLL(for example) is listed more than once as the default and as an add-on. How does PFE ensure that the add-on is used and not the default, bearing mind that the add-on will be an updated afcad2 file.

How can I ensure PFE uses the afcad2 files where listed and not the default files?
Thanks

PFE does not use the Runways.txt file?

PFE does not use AFCAD files

dmarch wrote:

PFE does not use the Runways.txt file?

PFE does not use AFCAD files

I have noticed that every time I have used London Heathrow the taxiing facility gets quite lost. If you don't as you say use afcad files how do you ascertain the correct rwy and taxi structure? Since most of us have upgraded our airfields like Heathrow etc with the latest afcads. For example the latest Heathrow afcad has taxiways that don't exist on previous afcads or the default file. In fact only one third of Heathrow is almost original.

The programme works well once in the air. But it seems still a little dodgy at each end. The "multicom" frequecy of 122.9 for LIMZ was it appears set up by the proflight2000 module.

The problem of being completely misdirected to the south west insted of the North East 20DME SE of rwy 09L at LHR is still of concern.

Also having looked at the PFE_FS9_Runways.dat file I see EGLL is listed slightly differently. In as much as my afcad stippulates rwy 09L-27R as landing only and rwy 09R-27L as t/o it would appear to agree except that the lines for EGLL don't end with double commas as do the others. Is this correct? Or do I need to make an adjustment?

EGLK,0261,51.323284,-0.847222,329,256.000,1640,0,59,-4.000,51.322590,-0.850645,0,,
EGLL,0091,51.477486,-0.489545,80,92.690,12776,110.30BDG,148,-3.000,51.477581,-0.461411,1001,CT,
EGLL,0092,51.464767,-0.486805,80,92.700,11978,109.50BDG,148,-3.000,51.464855,-0.460436,1001,,CL
EGLL,0271,51.464943,-0.434067,80,272.700,11978,109.50BDG,148,-3.000,51.464855,-0.460436,0,,CL
EGLL,0272,51.477676,-0.433278,80,272.690,12776,110.30BDG,148,-3.000,51.477581,-0.461411,0,CT,
EGLM,0030,51.495831,-0.775284,130,32.300,3305,0,148,-5.000,51.499859,-0.771944,0,,


Many thanks
Vololiberista

Quote:

I have noticed that every time I have used London Heathrow the taxiing facility gets quite lost. If you don't as you say use afcad files how do you ascertain the correct rwy and taxi structure? Since most of us have upgraded our airfields like Heathrow etc with the latest afcads. For example the latest Heathrow afcad has taxiways that don't exist on previous afcads or the default file. In fact only one third of Heathrow is almost original.

PFE does not use AFCAD files directly but uses the data generated by the MakeRwys utility, which is why it is important to rebuild the database each and every time you add a new airport or updated airport. Finding a taxiway at any airport is a difficult task and requires a lot of complex algorithms so I am never surprised if I hear about the occasional mishap... I've always said these feature can NEVER be 100% correct, but I would like to think we get it right 99% of the time and the general concensus from the feed back I've had reflects that is the case.

I have tested extensively at EGLL and must admit never had any issues, using both the Aerosoft Mega Heathrow and more lately the UK 2000 Heathrow. This airport, together with KORD, LFPG and EHAM were used due to the sheer size and number of taxiways within each complex. So why you should be having such issues is probably because your database rebuild has not completed correctly and hence PFE is using out-of-sync data. If not then please let me know which addon airport you're using, which gate you departed from, which runway you were directed to and the routing given by ATC. In fact if you have the debug log file that will suffice.

Quote:

The programme works well once in the air. But it seems still a little dodgy at each end. The "multicom" frequecy of 122.9 for LIMZ was it appears set up by the proflight2000 module.

Yes, correct. There is no Multicom facility available for LIMZ in FS so we would have use the original PF data. We always use PF data if we don't have anything else available, but FS data take precedence.

Quote:

The problem of being completely misdirected to the south west insted of the North East 20DME SE of rwy 09L at LHR is still of concern.

Well I would need a lot more info before I could comment because there are many variables concerning the how and why certain approach patterns are adopted. Unfortunately I don't quite understand when you say you were mis-directed to the South West instead of the North East... South East of Rwy 9L. If you were approaching from the south ATC would not direct you through the ILS for 9R

Quote:

Also having looked at the PFE_FS9_Runways.dat file I see EGLL is listed slightly differently. In as much as my afcad stippulates rwy 09L-27R as landing only and rwy 09R-27L as t/o it would appear to agree except that the lines for EGLL don't end with double commas as do the others. Is this correct? Or do I need to make an adjustment?

As mentioned before... PFE does NOT use AFCAD files directly. If you wish to tell PFE to use a runway specifically for takeoff or landing or even close it completely you need to do so using the configurable options available. Changing AFCAD files affect AI traffic accordingly but not PFE ATC

Dave i have sent you an email with the afcad file attached so you can play with it.

I need to know how i can mirror in PFE (or how PFE mirrors) a closed rwy.
Thanks Vololiberista

Vololiberista will you please answer the question I have asked you on multiple occasions now.

Have you deleted all of the files that makerwys creates before running it again?

i.e. Runways.csv, F5.csv, G5.csv, R4.csv R5.csv and T5.csv

Hi Vololiberista,

I have replied to your email... the details you need are in section 7.2.15

As for AFCAD files... I don't use them, sorry... as I explained earlier, PFE use data created by MakeRwys