• 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.

Compiling Errors

B

Billy

Messages
3
First of all, great program, made my own airport too! :D I compiled it perfectly and I have been flying at the airport today. I went to edit one airport so slightly. All I did was change the runway number at EGCC from 24 to 23, as they have changed recently. Anyway, I went to compile and looked at the errors and it said the taxiways have no runway to go to (how do I change that?) so I thinking of that I didn't compile it to BGL. I changed the PAPI at GCXO and that's it. I went to compile it, no errors in the checking, but when I compiled it to BGL I got some really long error.

Parsing document: GCXOPAPIFix.xml

INTERNAL COMPILER ERROR: #C2031: Failed element parse <BoundaryFence>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Spain
ERROR: city = Tenerife-North
ERROR: name = Los Rodeos
ERROR: lat = 28.4826527908444
ERROR: lon = -16.3415358960629
ERROR: alt = 631.85M
ERROR: magvar = 7.0
ERROR: ident = GCXO
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <BoundaryFence
ERROR: profile = {5acb60e6-992b-41c7-929b-e31d5343cd29}
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Vertex>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Spain
ERROR: city = Tenerife-North
ERROR: name = Los Rodeos
ERROR: lat = 28.4826527908444
ERROR: lon = -16.3415358960629
ERROR: alt = 631.85M
ERROR: magvar = 7.0
ERROR: ident = GCXO
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <BoundaryFence
ERROR: profile = {5acb60e6-992b-41c7-929b-e31d5343cd29}
ERROR: >
ERROR: <Vertex
ERROR: lat = 28.4883223101497
ERROR: lon = -16.3640785217285
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Vertex>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Spain
ERROR: city = Tenerife-North
ERROR: name = Los Rodeos
ERROR: lat = 28.4826527908444
ERROR: lon = -16.3415358960629
ERROR: alt = 631.85M
ERROR: magvar = 7.0
ERROR: ident = GCXO
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <BoundaryFence
ERROR: profile = {5acb60e6-992b-41c7-929b-e31d5343cd29}
ERROR: >
ERROR: <Vertex
ERROR: lat = 28.4913364425302
ERROR: lon = -16.3626815378666
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Vertex>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Spain
ERROR: city = Tenerife-North
ERROR: name = Los Rodeos
ERROR: lat = 28.4826527908444
ERROR: lon = -16.3415358960629
ERROR: alt = 631.85M
ERROR: magvar = 7.0
ERROR: ident = GCXO
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <BoundaryFence
ERROR: profile = {5acb60e6-992b-41c7-929b-e31d5343cd29}
ERROR: >
ERROR: <Vertex
ERROR: lat = 28.4898994490504
ERROR: lon = -16.3580819964409
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Vertex>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Spain
ERROR: city = Tenerife-North
ERROR: name = Los Rodeos
ERROR: lat = 28.4826527908444
ERROR: lon = -16.3415358960629
ERROR: alt = 631.85M
ERROR: magvar = 7.0
ERROR: ident = GCXO
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <BoundaryFence
ERROR: profile = {5acb60e6-992b-41c7-929b-e31d5343cd29}
ERROR: >
ERROR: <Vertex
ERROR: lat = 28.4905622899532
ERROR: lon = -16.3521158695221
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Vertex>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Spain
ERROR: city = Tenerife-North
ERROR: name = Los Rodeos
ERROR: lat = 28.4826527908444
ERROR: lon = -16.3415358960629
ERROR: alt = 631.85M
ERROR: magvar = 7.0
ERROR: ident = GCXO
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <BoundaryFence
ERROR: profile = {5acb60e6-992b-41c7-929b-e31d5343cd29}
ERROR: >
ERROR: <Vertex
ERROR: lat = 28.4880232438445
ERROR: lon = -16.3440419733524
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Vertex>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Spain
ERROR: city = Tenerife-North
ERROR: name = Los Rodeos
ERROR: lat = 28.4826527908444
ERROR: lon = -16.3415358960629
ERROR: alt = 631.85M
ERROR: magvar = 7.0
ERROR: ident = GCXO
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <BoundaryFence
ERROR: profile = {5acb60e6-992b-41c7-929b-e31d5343cd29}
ERROR: >
ERROR: <Vertex
ERROR: lat = 28.4871592372656
ERROR: lon = -16.3434930145741
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Vertex>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Spain
ERROR: city = Tenerife-North
ERROR: name = Los Rodeos
ERROR: lat = 28.4826527908444
ERROR: lon = -16.3415358960629
ERROR: alt = 631.85M
ERROR: magvar = 7.0
ERROR: ident = GCXO
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <BoundaryFence
ERROR: profile = {5acb60e6-992b-41c7-929b-e31d5343cd29}
ERROR: >
ERROR: <Vertex
ERROR: lat = 28.4860172867775
ERROR: lon = -16.3439521193504
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Vertex>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Spain
ERROR: city = Tenerife-North
ERROR: name = Los Rodeos
ERROR: lat = 28.4826527908444
ERROR: lon = -16.3415358960629
ERROR: alt = 631.85M
ERROR: magvar = 7.0
ERROR: ident = GCXO
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <BoundaryFence
ERROR: profile = {5acb60e6-992b-41c7-929b-e31d5343cd29}
ERROR: >
ERROR: <Vertex
ERROR: lat = 28.4782868251204
ERROR: lon = -16.3211680948734
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Vertex>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Spain
ERROR: city = Tenerife-North
ERROR: name = Los Rodeos
ERROR: lat = 28.4826527908444
ERROR: lon = -16.3415358960629
ERROR: alt = 631.85M
ERROR: magvar = 7.0
ERROR: ident = GCXO
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <BoundaryFence
ERROR: profile = {5acb60e6-992b-41c7-929b-e31d5343cd29}
ERROR: >
ERROR: <Vertex
ERROR: lat = 28.4747332334518
ERROR: lon = -16.3227555155754
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Vertex>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Spain
ERROR: city = Tenerife-North
ERROR: name = Los Rodeos
ERROR: lat = 28.4826527908444
ERROR: lon = -16.3415358960629
ERROR: alt = 631.85M
ERROR: magvar = 7.0
ERROR: ident = GCXO
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: >
ERROR: <BoundaryFence
ERROR: profile = {5acb60e6-992b-41c7-929b-e31d5343cd29}
ERROR: >
ERROR: <Vertex
ERROR: lat = 28.4883223101497
ERROR: lon = -16.3640785217285
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2607: Compilation errors detected, compilation failed!


Parse complete!

Can't copy BGL file into the destination folder:
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\BGL Compiler SDK\GCXOPAPIFix.BGL (The system cannot find the file specified)

I have read the forums and seen other errors like this, but it didn't help. I think I have all the updates, I downloaded it straight from zBlueSoftware.

Thanks a lot :)

Billy

P.s This is my destination folder and my BGLComp.exe location C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\BGL Compiler SDK
 
Ha ha, created by Jspring. Yeah, I compile with BGLCOMP.exe and I know I am doing it all right. Becuase now it's the other way around. I can edit and save airports already there but now I cannot compile my own airports as BGL. Is there somthing different that I have done or what. Doesn't make sense to em that I could compile custom built airports and not ones already there but now I can only compile airports already done by Microsoft. :S
 
Gorchi said:
Question is the same as in post:
http://www.fsdeveloper.com/forum/showthread.php?t=5896

Also I have noticed a lot of <Airport> tags in one XML file. Why?
Click to expand...

An XML file can contain more than one airport. So each airport wuld have its own Airport tag.

This is because a bgl file contains more than one airport, so the resulting decompile xml file also does.

I would recommend that if you open an xml file that contains more than one airport that you then perform a save as to create an xml file that only contains information on that airport you are working on.

-Russell
 
rf360m said:
An XML file can contain more than one airport. So each airport wuld have its own Airport tag.

This is because a bgl file contains more than one airport, so the resulting decompile xml file also does.

I would recommend that if you open an xml file that contains more than one airport that you then perform a save as to create an xml file that only contains information on that airport you are working on.

-Russell
Click to expand...
Agreed on that Russell! I saw MS is having more than one airport in one XML but usually a designer only corrects one airport, not the whole bunch of airports in one single BGL. So I do agree with You on the last paragraph too :)

And one thing that should concern all of us, designers. There are few addons that correct original MS files and they replace original ones. I am not in favour of doing this for many reasons, and one of it concerns also copyright on original files by Microsoft.

To go back to the original question - Billy, did a link I have provided helped You in this matter?

Best regards,
 
Gorchi said:
And one thing that should concern all of us, designers. There are few addons that correct original MS files and they replace original ones. I am not in favour of doing this for many reasons, and one of it concerns also copyright on original files by Microsoft.
Click to expand...

I agree absolutely with you here. The only way an original file should be modified is if Microsoft offers an upgrade, like SP1, that make those modifications.

Any other modifications made should create new files that are used as add-ons. This is the concept that FSX Planner, and I think all other utility apps, works with.

-Russell
 
Any other modifications made should create new files that are used as add-ons. This is the concept that FSX Planner, and I think all other utility apps, works with.
Click to expand...

Well, there is one Utility out there that most of us stay away from called Jabbgl.

Its a hex tool that changes parts of the default bgl's and then Users without regards to MS eula upload the bgl as part of their airport scenery work.

Glad to see that FSXPlanner and SDE/ADE took the high road using the deleteALL= statements rather then hex coding of a default bgl.
 
You must log in or register to reply here.
Back
Top