OnCourse Software

Well I managed to get Pete Dowson out of retirement, and here's his answer

Quote:

Right. I should have noticed -- the runway length is less than 1500 feet in those two airports (and in several others in the same BGL).

See this in the MakeRunways README document:

MINIMUM RUNWAY LENGTH
By default MakeRunways imposes a minimum runway length of 1500 feet, otherwise runways are omitted from the data files. This is to eliminate so-called "ghost" runways being included -- very small runways provided only to allow AI Traffic to be directed better for landings and takeoffs.
If necessary you can override this value. Just use a command line parameter in the form:
/>n where n gives the number of feet to be considered the maximum for exclusion. Take care not to make this too small for fear of including those "ghosts", but if you really do want to see all, you can set />0.

pointy56 wrote: *

Tue Jan 03, 2023 5:00 pm

I'm not sure what to suggest - I may try to get access to the source code to see if I can fix this issue.

I know it is rude to hijack a topic - sorry - but if you do go down this avenue there is another small issue which I think must be MAKERWYS and not PF3. If you add an ILS to an airport (in FS2004, at least) it isn't recognised by PF3 and you are still given a visual approach.

I was aware PD wasn't developing it further so hadn't thought it worth mentioning but if changes are likely to be made it is worth considering.

John

Hi John,

Well Pete didn't actually make any changes and he did mention to someone else a short while ago that he was completely retired from programming, so I wouldn't hold your breath. But you can always ask the question on the support forum. How are you making the change?

Quote:

Right. I should have noticed -- the runway length is less than 1500 feet in those two airports (and in several others in the same BGL).

See this in the MakeRunways README document:

MINIMUM RUNWAY LENGTH
By default MakeRunways imposes a minimum runway length of 1500 feet, otherwise runways are omitted from the data files. This is to eliminate so-called "ghost" runways being included -- very small runways provided only to allow AI Traffic to be directed better for landings and takeoffs.
If necessary you can override this value. Just use a command line parameter in the form:
/>n where n gives the number of feet to be considered the maximum for exclusion. Take care not to make this too small for fear of including those "ghosts", but if you really do want to see all, you can set />0.

Please note, this will only work if you enclose the parameter in quotes, like this: MakeRwys.exe "/>500"
However, I can confirm that with this value (500) it will include both LECK and LEMQ in the output (LECK is 861, LEMQ is 1331)

Hope this helps,
Martin

Thanks Dave and Martin. I will re-run MakeRunways again and check for LECK and LEMQ. /Mike

Ok, I ran MakeRwys again and did the database refresh and now PF3 recognizes LECK and LEMQ. The runways.csv file that was showing 82,692 rows (runways) on the normal run, now shows 92,598 rows (runways) now that I asked for all runways >500 feet, with the: MakeRwys.exe "/>500" command. Thanks everyone for your help with this! /Mike

Thank you for getting back to us with the results.