• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Will not compile stock KEWR

M

mlswartz

Messages
10
I tried moving a helipad start point at KEWR and then I kept getting a compilation error. As a test I tried to compile the stock KEWR airport and also got the following error:

Parsing document: FSX_AF2_KEWR.xml

INTERNAL COMPILER ERROR: #C2576: This LEG has parts in it that are not allowed ((23, 000E1DD1 000E3BF1 00000400)
Extra: Rho,
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Leg>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = United States
ERROR: state = New Jersey
ERROR: city = Newark
ERROR: name = Newark Liberty Intl
ERROR: lat = 40.69249738007784
ERROR: lon = -74.16866093873978
ERROR: alt = 5.486M
ERROR: magvar = 13.1
ERROR: ident = KEWR
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <Approach
ERROR: type = ILS
ERROR: runway = 11
ERROR: designator = NONE
ERROR: suffix = 0
ERROR: gpsOverlay = FALSE
ERROR: fixType = TERMINAL_WAYPOINT
ERROR: fixRegion = K6
ERROR: fixIdent = JEENO
ERROR: altitude = 457.2
ERROR: heading = 94.24476
ERROR: missedAltitude = 914.4
ERROR: >
ERROR: <MissedApproachLegs
ERROR: >
ERROR: <Leg
ERROR: type = VR
ERROR: flyOver = FALSE
ERROR: recommendedType = VOR
ERROR: recommendedRegion = K6
ERROR: recommendedIdent = TEB
ERROR: rho = 0.0M
ERROR: magneticCourse = 107.0
ERROR: altitudeDescriptor = A
ERROR: altitude1 = 518.16M
ERROR: altitude2 = 0.0M
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2607: Compilation errors detected, compilation failed!


Parse complete!

Can't copy BGL file into the destination folder:
X:\SDK\Environment Kit\BGL Compiler SDK\FSX_AF2_KEWR.BGL (The system cannot find the file specified)

I made changes to several other airports (KJFK, KTEB and KLGA) without any problems. Any idea what is wrong at KEWR?

Thanx.
 
The problem you seem to have is with an approach. Have you edited any of the approach information?
 
No, I simply opened the stock KEWR -- Find Airport, Search using SDK's fs10.Airports.dat file, Find airport ICAO code, then placing KEWR in the Find box -- and then immediately tried to compile. Then I got the above error.
 
Which version of the SDK are you using? If you are using the one that comes with the FSX DVD then you should update it to at least SP1a. There are a number of bugs in the compiler shipped with the original DVD. I just opened and compiled KEWR here without any issues. SP1a of the SDK can be downloaded from here:

http://www.microsoft.com/downloads/...FamilyID=24910e66-96b0-4543-9b4a-647b7e28f212


If you do have SP1a or later then please email me the xml file you generated -zip it up and email is to jon AT scruffyduck.co.uk
 
Last edited:
I got and fixed the XML. The problem was that for a VR missed approach leg the xml contained a Rho property in place of a Theta property and that caused the compile to fail. If the approach data was not modified then it may be there is a small bug in the program when it comes to generating the xml for this approach leg type.

Also unless you really want to compile approach code make sure that you set the compiler pre-requisites to not compile approaches and not delete them from the stock airport.
 
You must log in or register to reply here.
Back
Top