Makerunways.exe

[ronzie 21]

Go to rcv4 or rcv4x\data. 
Place a copy of r4.csv into a safe folder for backup. Right click on it and select  open with word or worpad, nor Excel or other database app..

 

Search for ESSA. Copy all of the lines and paste in a reply here.

 

Next right click on r4.csv and get the modified date-time stamp. Do the same r5.csv in your FS folder. They should be close.

 

in your FS folder right click on makerwys.exe. Check the version tan and also the comments, etc. The current version is located at:

 

http://forum.simflight.com/topic/66136-useful-additional-programs/

 

If not close install the new copy of makerwys.exe in your FS folder and run from within the scenery rebuild again.

 

If RC and FS are on the same pc, answer No to the WideFS question, then be sure to give the correct path to your FS folder.

 

If you are using RC on a WideFS client networked to an FS host, then you will first have to run makerwys.exe directly in your FS folder. Then from within RC start the scenery rebuild, answer yes to the WideFS question, and then proceed to enter the network path to your FS folder on the host and proceed as before.

 

I have the older FS9 ESSA from Aerosoft included in the French airports suite. Here is what I have in r4.csv for it:

 

ESSA,0011,59.637245,17.913218,124,7.370,10803,109.90BG,148,3.000,59.651821,17.918495,0,,
ESSA,0012,59.626476,17.950020,124,8.200,8202,0,207,3.000,59.637512,17.954342,0,,
ESSA,0080,59.658478,17.936028,124,72.870,8183,109.55B,148,3.000,59.661217,17.957575,0,,
ESSA,0191,59.648548,17.958664,124,188.200,8202,0,207,3.000,59.637512,17.954342,0,,
ESSA,0192,59.666397,17.923773,124,187.370,10803,110.70BG,148,3.000,59.651821,17.918495,0,,
ESSA,0260,59.663956,17.979122,124,252.870,8183,110.10BG,148,3.000,59.661217,17.957575,0,,

 

The field after the ICAO identification is the runway code ident. Disregard the first number. The next two are the runway primary identification followed by the forth character for 1=Left, 2=Right, 3=Center, or 0=Nothing. Here we are concerned with 0080 and 0260 for 8 and 26. In this version there are no indications of runways closed for takeoff (CT) or closed for landing (CL) near each line end. The runway length in feet is the seventh field here 8202 for 8/26. (Runways less than 1200 feet are disregarded.)

 

The next thing to check is your scenery library priority and path as seen by makerwys for ESSA. Here's how to do it:

 

In your FS folder there is a log file of makerwys operations called runway text. Being huge right click on it and select open with wordpad or word, not notepad. Searches and scrolling may be slow on your PC.

 

A default airport has a single section defining runways and other data. An add-on airport or af type (afcad, AFX, ADE) file has two sections not necessarily together. A deletion section will precede a detailed runway and other data section.

 

Search for "Airport ESSA". The first find will be the default stock airport and at the section head will be a path to that in your AP type file. Search again and you should come across a section with deletion statements. The path should point to the add-on folder for the ESSA scenery or af type file folder if the first instance is all you have. Repeat the search and you should now find a section detailing runwy data, comms, etc. Check the path for that.

 

Keep repeating the search for "Airport ESSA" until no more are found. The last "Airport ESSA" section should have your runway details, etc.,  and the path should point to your add-on ESSA scenery folder. Here in part is my FS9 deletion section for Aerosoft's older inclusion of ESSA in the France suite of airports:

 

Addon Scenery\SCA2\scenery\AF2_ESSA.bgl
=============================================================================
Deletions check for Airport ESSA:
          Delete all taxiways!


          Delete all runways and starts!

              *** DelBth *** ESSA0011 Lat 59.637245 Long 17.913218 Alt 124 Hdg 7 Len 10803 Wid 148 ILS 109.90, Flags: GS BC

              *** DelBth *** ESSA0080 Lat 59.658413 Long 17.936098 Alt 124 Hdg 73 Len 8183 Wid 148 ILS 109.55, Flags: BC

              *** DelBth *** ESSA0192 Lat 59.666397 Long 17.923773 Alt 124 Hdg 187 Len 10803 Wid 148 ILS 110.70, Flags: GS BC

              *** DelBth *** ESSA0260 Lat 59.663891 Long 17.979193 Alt 124 Hdg 253 Len 8183 Wid 148 ILS 110.10, Flags: GS BC


          Delete all taxiways!


          COM: Delete all frequencies!

 

and now the next search turns up the runway data section (in part:)

 

Addon Scenery\SCA2\scenery\AF2_ESSA.bgl
=============================================================================

Airport ESSA :N59:39:06.9765  E017:55:06.9989  124ft
          Country Name="Sweden"
          State Name=""
          City Name="Stockholm"
          Airport Name="Arlanda"
          in file: Addon Scenery\SCA2\scenery\AF2_ESSA.bgl

          Runway 1L/19R centre: N59:39:06.5554  E017:55:06.5807  124ft
              Start 1L: N59:38:17.3484  E017:54:48.7896  124ft Hdg: 10.4T, Length 10803ft
              Computed start 1L: Lat 59.637245 Long 17.913217
              Start 19R: N59:39:55.3736  E017:55:24.3781  124ft Hdg: 190.4T, Length 10803ft
              Computed start 19R: Lat 59.666397 Long 17.923774
              Hdg: 10.370 true (MagVar 3.000), Concrete, 10803 x 148 ft
              Primary ILS ID = SSA
              *** No matching ILS record - assume provided by another layer
              Secondary ILS ID = NSA
              *** No matching ILS record - assume provided by another layer
              *** Runway *** ESSA0011 Lat 59.637245 Long 17.913218 Alt 124 Hdg 7 Len 10803 Wid 148
              *** Runway *** ESSA0192 Lat 59.666397 Long 17.923773 Alt 124 Hdg 187 Len 10803 Wid 148
          Runway 8 /26  centre: N59:39:40.3750  E017:57:27.2727  124ft
              Start 8 : N59:39:31.5962  E017:56:18.5899  124ft Hdg: 75.9T, Length 8183ft
              Computed start 8 : Lat 59.658478 Long 17.936028
              Start 26 : N59:39:49.3483  E017:58:37.6821  124ft Hdg: 254.7T, Length 8183ft
              Computed start 26 : Lat 59.663956 Long 17.979121
              Hdg: 75.870 true (MagVar 3.000), Concrete, 8183 x 148 ft
              Primary ILS ID = WSA
              *** No matching ILS record - assume provided by another layer
              Secondary ILS ID = ESA
              *** No matching ILS record - assume provided by another layer
              *** Runway *** ESSA0080 Lat 59.658478 Long 17.936028 Alt 124 Hdg 73 Len 8183 Wid 148
              *** Runway *** ESSA0260 Lat 59.663956 Long 17.979122 Alt 124 Hdg 253 Len 8183 Wid 148
          Runway 1R/19L centre: N59:38:15.0484  E017:57:15.6325  124ft
              Start 1R: N59:37:40.3540  E017:57:02.1736  124ft Hdg: 8.2T, Length 8202ft
              Computed start 1R: Lat 59.626476 Long 17.950019
              Start 19L: N59:38:49.9695  E017:57:29.3777  131ft Hdg: 191.3T, Length 8202ft
              Computed start 19L: Lat 59.648548 Long 17.958664
              Hdg: 11.200 true (MagVar 3.000), Asphalt, 8202 x 207 ft
              *** Runway *** ESSA0012 Lat 59.626476 Long 17.950020 Alt 124 Hdg 8 Len 8202 Wid 207
              *** Runway *** ESSA0191 Lat 59.648548 Long 17.958664 Alt 124 Hdg 188 Len 8202 Wid 207

notice the same path at the head.

 

This was the last runway addition section and has priority and the r4.csv values come from this section.

 

Also look to see if runway 8 or 26 has no indication of a computed start location.

 

Let's see if you discover a failure of RC to copy in your FS folder r5.csv to r4.csv in your rcv4-rcv4x\data folder (same modified date-time stamp) or the last data section is pointing to the incorrect scenery folder for your ESSA add-on scenery. Also insure there is no indication of a computed start or indication of runway closures.

 

Looking forward to your reply.

 

[Vulkan 2]

Here is the lines from ESSA in my r4.csv:

 

ESSA,0011,59.637222,17.913147,124,8.000,10803,109.90BG,148,3.000,59.651768,17.918743,0,,CL
ESSA,0012,59.626583,17.950445,124,8.030,8202,109.35BDG,148,3.000,59.637623,17.954702,0,CT,
ESSA,0191,59.648663,17.958960,124,188.030,8202,111.35BDG,148,3.000,59.637623,17.954702,0,,
ESSA,0192,59.666313,17.924339,124,188.000,10803,110.70BG,148,3.000,59.651768,17.918743,0,,
ESSA,0260,59.663570,17.979528,124,253.420,8183,110.10BG,148,3.000,59.660934,17.957932,0,CT,

 

modified time stamp of r4 is: ‎den ‎22 ‎juli ‎2013, ‏‎06:51:14 (this was the r4 in the rcv4x folder. I also have a r4 in the FS folder, but I havn't touched that one)

modified time stamp of r5 is: ‎den ‎22 ‎juli ‎2013, ‏‎06:51:14

 

When I opened the runway.txt I found that it says that runway 8 is closed for both starting and landing. Might this be the problem? How can I change this? I have already tried to re-install the Arlanda scenario, but that didn't do anything...

 

my makerwys in the FS folder is 4.1.2.0 (your link poted above does not work so I don't know if this is the current version).

 

Area.154 "Stockholm Arlanda X" (Layer=154)

Local=Aerosoft\Arlanda X

=============================================================================

Aerosoft\Arlanda X\scenery\AFX_ESSA.bgl

=============================================================================

Airport ESSA N59:39:06.9765 E017:55:06.9989 137ft

Delete all taxiways!

　

Delete all runways and starts!

*** DelBth *** ESSA0011 Lat 59.637245 Long 17.913218 Alt 137 Hdg 7 Len 10803 Wid 148 ILS 109.90, Flags: GS BC

*** DelBth *** ESSA0012 Lat 59.624722 Long 17.952057 Alt 137 Hdg 7 Len 8181 Wid 148 ILS 109.35, Flags: GS BC

*** DelBth *** ESSA0080 Lat 59.658413 Long 17.936096 Alt 137 Hdg 72 Len 8183 Wid 148 ILS 109.55, Flags: BC

*** DelBth *** ESSA0191 Lat 59.646793 Long 17.960079 Alt 137 Hdg 187 Len 8181 Wid 148 ILS 111.35, Flags: GS BC

*** DelBth *** ESSA0192 Lat 59.666397 Long 17.923773 Alt 137 Hdg 187 Len 10803 Wid 148 ILS 110.70, Flags: GS BC

*** DelBth *** ESSA0260 Lat 59.663891 Long 17.979191 Alt 137 Hdg 252 Len 8183 Wid 148 ILS 110.10, Flags: GS BC

　

Runway 1L/19R centre: N59:39:06.3610 E017:55:07.4754 124ft

Runway 1L closed for landing

Computed start 1L: Lat 59.637222 Long 17.913148

Computed start 19R: Lat 59.666313 Long 17.924338

Hdg: 11.000 true (MagVar 3.000), CONCRETE, 10803 x 148 ft

Primary ILS: SSA 109.90 , Flags: GS BC

Secondary ILS: NSA 110.70 , Flags: GS BC

*** Runway *** ESSA0011 Lat 59.637222 Long 17.913147 Alt 124 Hdg 8 Len 10803 Wid 148 ILS 109.90, Flags: GS BC

*** Runway *** ESSA0192 Lat 59.666313 Long 17.924339 Alt 124 Hdg 188 Len 10803 Wid 148 ILS 110.70, Flags: GS BC

Runway 8 /26 centre: N59:39:39.3708 E017:57:28.5552 124ft

Runway 8 closed for landing and take-off

Runway 26 closed for take-off

Computed start 26 : Lat 59.663570 Long 17.979529

Hdg: 76.420 true (MagVar 3.000), CONCRETE, 8183 x 148 ft

Primary ILS: WSA 109.55 , Flags: BC

Secondary ILS: ESA 110.10 , Flags: GS BC

*** Runway *** ESSA0260 Lat 59.663570 Long 17.979528 Alt 124 Hdg 253 Len 8183 Wid 148 ILS 110.10, Flags: GS BC

Runway 1R/19L centre: N59:38:15.4371 E017:57:16.9312 124ft

Runway 1R closed for take-off

Computed start 1R: Lat 59.626583 Long 17.950445

Computed start 19L: Lat 59.648663 Long 17.958960

Hdg: 11.030 true (MagVar 3.000), ASPHALT, 8202 x 148 ft

Primary ILS: TSA 109.35 , Flags: GS DME BC

Secondary ILS: USA 111.35 , Flags: GS DME BC

*** Runway *** ESSA0012 Lat 59.626583 Long 17.950445 Alt 124 Hdg 8 Len 8202 Wid 148 ILS 109.35, Flags: GS DME BC

*** Runway *** ESSA0191 Lat 59.648663 Long 17.958960 Alt 124 Hdg 188 Len 8202 Wid 148 ILS 111.35, Flags: GS DME BC

FSM ATIS for ESSA=1900

[SteveW 1,792]

Since Windows Vista, there's a lot of unnecessary fuss made about the Program Files folder horrid security and having to Run as Admin and so on. There need not be...

 

All one has to do is, first thing after a default installation of FS9/FSX, is simply set some folder permissions on the FS program folder. So before adding aircraft or making changes to the installation, with explorer add "Modify" and "Write" permissions to the "Users" group and allow the changes to affect subfolders. Beats choosing Run as Admin and having masses of problems installing addons with installers and uninstallers that stopped working after WinXP.

 

Regards

Steve

[Pete Dowson 558]

Runway 1L closed for landing

Runway 8 closed for landing and take-off

Runway 26 closed for take-off

Runway 1R closed for take-off

Looks like the AFD data you are using closes runway 8, but it should still be listed in the RC file and marked CL, CT.

 

my makerwys in the FS folder is 4.1.2.0 (your link poted above does not work so I don't know if this is the current version).

4.12 is far too old. I'm surprised anyone has such an old version. 4.65 or later (currently 4.67 in fact) )is available on both the main Schiratti site (where FSUIPC main releases are obtained) and from my Support Forum.

 

Pete Dowson

 

 

Pete

[Vulkan 2]

Ok, thanks Pete. I will donload that newer version. But that won't solve my problem with runway 08 being closed, will it?

 

Is there anyway for me to change this? And by the way, 01L is used for landings alot, so I would like to change that too if I could...

[ronzie 21]

Since Windows Vista, there's a lot of unnecessary fuss made about the Program Files folder horrid security and having to Run as Admin and so on. There need not be...

 

All one has to do is, first thing after a default installation of FS9/FSX, is simply set some folder permissions on the FS program folder. So before adding aircraft or making changes to the installation, with explorer add "Modify" and "Write" permissions to the "Users" group and allow the changes to affect subfolders. Beats choosing Run as Admin and having masses of problems installing addons with installers and uninstallers that stopped working after WinXP.

 

Regards

Steve

 

There are two kinds of executable file permissions in Win VISTA and 7. One is user access and the other is application level access, a program privilege, not user access.

 

In Win 7 you need to raise the executable file access privilege. In Win 7 to raise the access all the time you set up a shortcut to the .exe file. Then on the shortcut, right click, the properties, then click Advanced. You should see a box to check for run as admin. Click that to set it, then OK to get back to the previous window, then Apply, then OK to close the properties Window.

 

It has been written that unlike VISTA, turning off UAC does not remove the requirement to set run as admin where needed.

 

Applications that need this privilege in Win 7 have code to raise their privilege when needed. RC does not contain this code so the workaround described is needed.

[ronzie 21]

The link to the latest version of makerwys is;

http://forum.simflight.com/topic/66136-useful-additional-programs/

and today is 4.671.

 

The link to the latest version of fsuipc is:

http://forum.simflight.com/topic/66139-updated-modules/

and today 3.999z4 full and partial installation for FS9 is there and 4.909 interim and 4.90 full for FSX/Prepare3D.

 

In the r4.csv extract you posted runway 8 as 0080 is not listed. It should be even though it is closed for take-offs and landings. It does show in the runways.txt section you posted. Try the updated makerwys.exe.

 

RC copies the r5.csv in your host FS folder to rc\data folder as r4.csv so it should be identical except for the file name.

[SteveW 1,792]

There are two kinds of executable file permissions in Win VISTA and 7. One is user access and the other is application level access, a program privilege, not user access.

 

In Win 7 you need to raise the executable file access privilege. In Win 7 to raise the access all the time you set up a shortcut to the .exe file. Then on the shortcut, right click, the properties, then click Advanced. You should see a box to check for run as admin. Click that to set it, then OK to get back to the previous window, then Apply, then OK to close the properties Window.

 

It has been written that unlike VISTA, turning off UAC does not remove the requirement to set run as admin where needed.

 

Applications that need this privilege in Win 7 have code to raise their privilege when needed. RC does not contain this code so the workaround described is needed.

 

 

Some programs were written and tested before Vista came out using accounts with admin privileges, older Windows versions too easily giving regular users admin rights. These programs then failed once Vista and above appeared due to having expected to make changes in parts of the file system that were protected, and expecting to write to parts of the registry that were protected. The two most common problems are having to "Run as Admin" to allow the program registry access, no way round this problem, but those 'only' accessing protected parts of the file system could be fixed by adjusting the privileges as I stated above. The fix I proposed above solves 99% of all problems and is recommended since it's a lot safer.

 

A program that requires admin rights (an installer or uninstaller) should check itself for malware before asking the user to allow it to move up to admin rights. If it suspects malware then it can end there and then. But if you checked the "Run as Admin" box in the desktop link (Icon) and double-clicked it then the payload has been installed under admin privileges already and it's too late.

[ronzie 21]

Once installed RC needs the Run As Admin program privilege to execute makerwys.exe and communicate with fsuipc via Win interapp messaging if fs is in any Program Files hierarchy under Win 7.

 

The installer can be started with the right click-run as admin.

 

If a user doers not want to give RC these privileges then FS should not be installed under the program files hierarchy which has been recommended on several forums for other applications.

 

In addition slightly related because RC has constant communication with fsuipc, some security apps thinks it is malware because of the frequent access to another app so for some antivirus apps it needs to be declared as a safe application. This security heuristic behavior (used to detect unknown viruses) has caused RC to close with a access error after running it with FS after a few minutes. However there should be no problem with a security examining RC as it loads using the antivirus scan on demand feature.

 

Once installed RC does not use the registry.

[Pete Dowson 558]

Ok, thanks Pete. I will donload that newer version. But that won't solve my problem with runway 08 being closed, will it?

I don't think it will stop you selecting that runway, but it may deter RC from actually assigning it automatically. The AI traffic won't use it though.

 

Is there anyway for me to change this?

You can change the file, removing the CL and CT at the end of the line, which will affect RC. But that would need doing everytime you update your scenery and rerun MakeRunways, and it won't do anything for AI traffic. To change the BGL you'd need to use an AFD editor like Airport Design Editor (ADE).

 

Pete