ADE Will Not Compile After Changing Runway Numer in the Properties

[kmanning]

Hi,
I'm not sure if I did this correctly but in FS9, I'm trying to change the runway number for KTPA, Tampa Airport, from 18L/R to 19L/R. The 2007 afcad does not have the correct runway number. This is what came with the scenery file I downloaded and it was the latest scenery file I can find. When I try to compile it after making the changes, I get this error message:

ScruffyDuck Scenery Design Engine Compiling
Using BglComp....


Parsing document: C:\FS9\Addon Scenery\scenery\KTPA_ADE9_KM.xml


***** Duplicate Runway *****ERROR C2031: Failed element parse <Runway>
ERROR C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = United States
ERROR: state = Florida
ERROR: city = Tampa
ERROR: name = Tampa Intl
ERROR: lat = 27.9754722118378
ERROR: lon = -82.5332500040531
ERROR: alt = 7.924M
ERROR: magvar = 3.5
ERROR: ident = KTPA
ERROR: >
ERROR: <Runway
ERROR: lat = 27.9784156009555
ERROR: lon = -82.5418402254581
ERROR: alt = 7.924M
ERROR: surface = CONCRETE
ERROR: heading = 181.720001220703
ERROR: length = 3362.55M
ERROR: width = 45.72M
ERROR: number = 19
ERROR: designator = RIGHT
ERROR: patternAltitude = 304.8M
ERROR: primaryTakeoff = YES
ERROR: primaryLanding = NO
ERROR: primaryPattern = LEFT
ERROR: secondaryTakeoff = YES
ERROR: secondaryLanding = NO
ERROR: secondaryPattern = LEFT
ERROR: >
ERROR:

***** Duplicate Runway *****ERROR C2031: Failed element parse <Runway>
ERROR C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = United States
ERROR: state = Florida
ERROR: city = Tampa
ERROR: name = Tampa Intl
ERROR: lat = 27.9754722118378
ERROR: lon = -82.5332500040531
ERROR: alt = 7.924M
ERROR: magvar = 3.5
ERROR: ident = KTPA
ERROR: >
ERROR: <Runway
ERROR: lat = 27.9756820946932
ERROR: lon = -82.528607994318
ERROR: alt = 7.924M
ERROR: surface = ASPHALT
ERROR: heading = 181.720001220703
ERROR: length = 2536.85M
ERROR: width = 45.72M
ERROR: number = 19
ERROR: designator = LEFT
ERROR: patternAltitude = 304.8M
ERROR: primaryTakeoff = NO
ERROR: primaryLanding = YES
ERROR: primaryPattern = LEFT
ERROR: secondaryTakeoff = NO
ERROR: secondaryLanding = YES
ERROR: secondaryPattern = LEFT
ERROR: >
ERROR:

ERROR: Taxi path #601 references a non-existent Runway #36L at airport KTPA.
ERROR: Compilation errors detected, compilation failed!

Parse complete!

I've already tried the red button at the bottom left and it still won't compile.

Ken.

 

[glottis]

Ken
the clue is at the top, a "duplicate runway", check the runway list.....
just wondering if the file has the crosswind runways active and it is one of those,
I don't have fs9 so I'm only guessing
what does the red button say, duplicate runway?

 

[kevintampa5]

Are you editing stock or someone else modified scenery?

 

[scruffyduck]

As Ray says you have two runways with the same number.

Pease check this: https://scruffyduck.clarify-it.com/d/wjcr96 The Issue Manager is available in all current versions of ADE and will help you fix problems like this.

 

[kmanning]

Are you editing stock or someone else modified scenery?

Hi,
Actually, it's a scenery file called Tampa International Airport - KPTA that I downloaded from AVSIM. The file name is ktpa_full_v1.zip. I was trying to edit the afcad file in that download. This file was added in 2007, so it's not current. The one thing I noticed is that the runway number is 18/36 instead of the current 19/01. I read the issue manager but there're some things that I don't quite understand.

Ken.

 

[kmanning]

Ken
the clue is at the top, a "duplicate runway", check the runway list.....
just wondering if the file has the crosswind runways active and it is one of those,
I don't have fs9 so I'm only guessing
what does the red button say, duplicate runway?

Hi Ray,
No, it says Taxipath is assigned to non existent runway 00L. Just below the button that says "Fix," it says Set path type to 'PATH.' I pressed the Fix button and tried to compile again. It still will not compile. I'm not sure what you mean by "dulicate runway." I also don't understand what is meant by crosswind runways, unless it's referring to runways 10/28 which would be the crossing runway. Is it because I did not change these runway numbers because I did not change them. I'll try it and see if that's the problem. I did not think about that.

Ken.

Ken.

 

[kmanning]

Hi Ray,
No, it says Taxipath is assigned to non existent runway 00L. Just below the button that says "Fix," it says Set path type to 'PATH.' I pressed the Fix button and tried to compile again. It still will not compile. I'm not sure what you mean by "dulicate runway." I also don't understand what is meant by crosswind runways, unless it's referring to runways 10/28 which would be the crossing runway. Is it because I did not change these runway numbers because I did not change them. I'll try it and see if that's the problem. I did not think about that.

Ken.

Ken.

Hi Ray,
I think I understand this now. I checked the Runway List and it listed 14 runways, and Tampa International doesn't have 14 runways. It listed some that doesn't even exist. Why is that? I think I understand what you mean by crossing runway being active. When it says True, it's active. When False, it's not active. I deleted all of the runways other than runways 19L/19R, 01L/01R, and 10/28. Now it will compile and the runway numbers are correct. I noticed that the heading says 181.72 but it's actually 186.50. When I tried to change this, it place the runway in the wrong location, so I assume that I should not change the heading.

Ken.

 

[FlyingAxx]

I noticed that the heading says 181.72 but it's actually 186.50. When I tried to change this, it place the runway in the wrong location, so I assume that I should not change the heading.

Ken.

Ken, the runway rotates a bit clockwise around its centre, of course, and this is remarkable as all other feature will not. Taxipaths, buildings etc. will remain where they are. Usually, you urgently need reference points in order to correct such positions as in most cases a shift in any direction is required, too. You might want to use ADE's position marks for this purpose or even the existing Start Points. Just double-click a runway start in order to show the properties, click on the box "Set by Drag" in order to input manually the correct position (the button turns green). You can copy and paste it directly from the runway properties of the next link as ADE understands the format: http://www.airnav.com/airport/KTPA. If the deviation is remarkable you may decide whether it's worth to do the work or not.

ADE itself is capable to do the job, However, you need a bit of experience (at least patience). A Pro-key would help but you need to know what to do with it. But hey, it's fun - isn't it?

Axel

 

[jvile]

I noticed that the heading says 181.72 but it's actually 186.50.

The 186.50 is the Mag heading and we do not have control over that value unless you change the MagDec.bgl.

Runways in FS are set to True heading so for Tampa that is 181.720001

 

[scruffyduck]

The 186.50 is the Mag heading and we do not have control over that value unless you change the MagDec.bgl.

Runways in FS are set to True heading so for Tampa that is 181.720001

Just to re-iterate that. Runways are physical things. The true heading of a runway cannot be changed unless you dig it up. Since magnetic variation changes over time then the mag heading will change. Runway numbers are based on Magnetic heading which is why they are changed from time to time. Runways in FS (and ADE) are based on true heading so once set there is not reason that they should ever be changed.

 

[glottis]

Hi Ray,
I think I understand this now. I checked the Runway List and it listed 14 runways, and Tampa International doesn't have 14 runways. It listed some that doesn't even exist. Why is that? I think I understand what you mean by crossing runway being active. When it says True, it's active. When False, it's not active. I deleted all of the runways other than runways 19L/19R, 01L/01R, and 10/28. Now it will compile and the runway numbers are correct. I noticed that the heading says 181.72 but it's actually 186.50. When I tried to change this, it place the runway in the wrong location, so I assume that I should not change the heading.

Ken.

Ken,
the list of runways (11 are fake) is how we use Jim's great technique of activating non parallel runways, this fools runways to think they are all parallel, thus FSX is able to use all 3 runways at KTPA for take-off/landing,
no problem deleting them, all that does is revert back to the default runway operation,
if there are no "Duplicate" runways in the original list of 14 then ADE will give you a warning they are outside the airport "test radius" (the red circle) but will still compile

 

[FlyingAxx]

The 186.50 is the Mag heading and we do not have control over that value unless you change the MagDec.bgl.

Runways in FS are set to True heading so for Tampa that is 181.720001

Jim, the deviation to the reality should be negligible, indeed. The chart from JAN 2010 says indeed 186.5° with a mag. deviation of 4.8°W and an annual rate of change of 0.1°W/a. Actually, I didn't even think on this as I was fixed on the absolute LAT/LON values that I usually take for reference. For other regions with a lack of free available maps and similar information I'm taking such information in case of doubts from my PMDG navdata - if available - or I use Google's or Bing's satellite pics as background reference.

 

[kmanning]

Ken, the runway rotates a bit clockwise around its centre, of course, and this is remarkable as all other feature will not. Taxipaths, buildings etc. will remain where they are. Usually, you urgently need reference points in order to correct such positions as in most cases a shift in any direction is required, too. You might want to use ADE's position marks for this purpose or even the existing Start Points. Just double-click a runway start in order to show the properties, click on the box "Set by Drag" in order to input manually the correct position (the button turns green). You can copy and paste it directly from the runway properties of the next link as ADE understands the format: http://www.airnav.com/airport/KTPA. If the deviation is remarkable you may decide whether it's worth to do the work or not.

ADE itself is capable to do the job, However, you need a bit of experience (at least patience). A Pro-key would help but you need to know what to do with it. But hey, it's fun - isn't it?

Axel

Hi Axel,
Yes, that's what it did. It rotated around it's center. So, I just left it as it is.

Ken.

 

[kmanning]

The 186.50 is the Mag heading and we do not have control over that value unless you change the MagDec.bgl.

Runways in FS are set to True heading so for Tampa that is 181.720001

Oh, okay. So, FS runway headings are set to True Heading, NOT Magnetic Heading.

Ken.

 

[kmanning]

Just to re-iterate that. Runways are physical things. The true heading of a runway cannot be changed unless you dig it up. Since magnetic variation changes over time then the mag heading will change. Runway numbers are based on Magnetic heading which is why they are changed from time to time. Runways in FS (and ADE) are based on true heading so once set there is not reason that they should ever be changed.

Hi Jon,
Okay, so it's physically placed and chaning the heading in the Runway Properties DOES NOT change the magnetic variation but it physically places the runway on a True Heading. It's like building a new runway from the start. It makes more since to me now and if I understand correctly, True Heading never changes, which is the physical runway. Do I have that correct?

Ken.

 

[kmanning]

Ken,
the list of runways (11 are fake) is how we use Jim's great technique of activating non parallel runways, this fools runways to think they are all parallel, thus FSX is able to use all 3 runways at KTPA for take-off/landing,
no problem deleting them, all that does is revert back to the default runway operation,
if there are no "Duplicate" runways in the original list of 14 then ADE will give you a warning they are outside the airport "test radius" (the red circle) but will still compile

Hi Ray,
Yes, there were duplicate runways in the original list of 14. So was deleting the duplicate runways the correct way to fix the problem? Let me make sure I understand correctly. Are you saying that in order to use these runways for take-offs and landings, you have to have duplicate runways or fake runways? I'm not sure what you mean by Jim's great technique of activating non parallel runways.

Ken.

 

[glottis]

Hi Ray,
Yes, there were duplicate runways in the original list of 14. So was deleting the duplicate runways the correct way to fix the problem? Let me make sure I understand correctly. Are you saying that in order to use these runways for take-offs and landings, you have to have duplicate runways or fake runways? I'm not sure what you mean by Jim's great technique of activating non parallel runways.

Ken.

well deleting them is one way but i would have simply changed the number to one that wasn't the same as any of the others
i list my fake runways in order so when in FSX using ATC it calls all runways in order that way i know if they are going to work, but you can call the fake runways what you like as long as they are not the same as the real runways
you only need the fake runways if you want to activate the crosswind runway 10/28 so all three runways will be used, otherwise the default will be used,
I cant remember if the default used is 10/28 or the two parallel ones.............

 

[scruffyduck]

Hi Jon,
Okay, so it's physically placed and chaning the heading in the Runway Properties DOES NOT change the magnetic variation but it physically places the runway on a True Heading. It's like building a new runway from the start. It makes more since to me now and if I understand correctly, True Heading never changes, which is the physical runway. Do I have that correct?

Ken.

Yes that is correct.

Sent from my Sony Xperia with Tapatalk 2