Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hello everyone,

first-time poster, hope I got the right subforum.

I'm having problems with makerwys. Certain airports aren't written into the runways.csv. When that happens, I can't use them in PF3, which is how I came across this in the first place. I have no idea how many airports are affected, I have so far only stumbled across a few.

Attached are two excerpts from the log file Makerwys puts out, for EDRM and LFKX. Both are add-ons, one free- and one payware. From what I can tell, Makerwys recognizes runways, but doesn't write them into the .csv. The airports are added via .xml-method, and the latest version of P4AO is installed.

Any ideas on how I can rectify this?

Kind regards,

Dimitrios

EDRM.txt

LFKX.txt

Posted
29 minutes ago, Demio said:

Attached are two excerpts from the log file Makerwys puts out, for EDRM and LFKX.

EDRM is defined with one 10ft long runways:

              Start 18 : N49:58:16.7341  E007:06:42.4181  919ft Hdg: 180.0T, Length 10ft 
              Start 36 : N49:57:52.1144  E007:06:41.5910  919ft Hdg: 0.0T, Length 10ft 
              Hdg: 180.000 true (MagVar -1.000), Grass, 10 x 3 ft


In fact in this runway seems to be defined as a piece of Grass, 10 feet long by 3 feet wide!  If you read the document which comes with MakeRunways you can see that you need a command line parameter to tell it to include short runways, but 10 x 3 seems too small even for a Helipad!

LFKX has this defined:

              Runway 15  closed for take-off
              Start 33 : N45:24:21.7294  E006:34:42.9276  5638ft Hdg: 333.0T, Length 3ft 
              Hdg: 11.000 true (MagVar 1.000), UNKNOWN 254, 3 x 3 ft


This one has a missing Start point for the runway 15 end, and again it is too short at 3 feet (3 x 3!!!???) and uses an undocumented surface type code (254).

I suspect these sceneries have been made for visual effect and are not intended for use by AI traffic or other external programs.

You would be able to correct these things using something like ADE (freeware), but I'm afraid MakeRunways can only process the data it is provided with in the Airport Definition BGLs.

Pete

 

Posted

Okay, thanks. I will try to run Makerwys so that it includes such short "runways". Since it's only for PF3, and I can live without AI, I hope that will work.

Posted
20 minutes ago, Demio said:

I will try to run Makerwys so that it includes such short "runways".

I'm not sure the parameter will accept such ridiculous lengths. Try and see -- let me know. But in any case it won't include runway 15 for LFKX.

For the commercial one I think you should report this to the authors or company.

Pete

 

Posted (edited)

Hi Pete,

it doesn't seem to work. I've tried "MakeRwys.exe />1" and "MakeRwys.exe />0" (as per the documentation) and the number of resulting runways doesn't change. In any case EDRM and LFKX aren't included. I don't think the program is accepting the parameter at all. (It seemingly accepts "/water" just fine).

Concerning LFKX: It's an "altiport" with steep runway, which can only be used in one direction for landings and the other for take-offs, so that part would be okay. The length is another story...

Dimi

Edit for update: I had to format the command as follows: "MakeRwys.exe "/>0 /water"", and now it seems to work. Thanks!

Edited by Demio
New information
Posted
2 hours ago, Demio said:

Concerning LFKX: It's an "altiport" with steep runway

Ah, the authors would have had to "fiddle" it, as the sim doesn't support sloping runways (yet). The 3 feet part will be flat! ;-)

Pete

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.