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

FSX Error compiling EHAM Aerosoft

johnk51

johnk51

Messages
110
Country
us-washington
I'm now having problems compiling Eham. This is what I get, and then what the xml lines show.

Compiler Errors Found. These were not identified by the Issue Manager. Please let us know
what the compiler error is so that we can improve the Issue Manager.
The compiler message is shown below
ScruffyDuck Scenery Design Engine Compiling
Using BglComp....
INTERNAL COMPILER ERROR: #C1003: Failed to create MSXML object! (0x80040154)
Parsing document: D:\FSX\aerosoft\Amsterdam Schiphol X\Scenery\AFX_EHAM.xml
INTERNAL COMPILER ERROR: #C2430: Unrecoverable error parsing XML!
INTERNAL COMPILER ERROR: #C2006: Parse failed (0x80004005)
INTERNAL COMPILER ERROR: #C2003: Failed to process file: D:\FSX\aerosoft\Amsterdam Schiphol X\Scenery\AFX_EHAM.xml
001002 type="RUNWAY"
001003 lat="52.3005518317223"
001004 lon="4.7840590775013" <<<<
001005 alt="-11.024F"
001006 heading="41.2400016784668"
001007 number="04"

002429 <TaxiwayPoint
002430 index="217"
002431 type="NORMAL" <<<<
002432 orientation="FORWARD"
002433 lat="52.3325619846582"
002434 lon="4.71258401870728"/>

002003 <TaxiwayPoint
002004 index="145" <<<<
002005 type="HOLD_SHORT"
002006 orientation="FORWARD"
002007 lat="52.3037879168987"
002008 lon="4.77327346801758"/>
I bolded the <<<< that are showing. I don't know what that's for but I don't see that on other lines. I don't find anything in fault finder. Any help is appreciated.
 
I don't know how the msxml 4 was missing. I had just updated some other afcads yesterday with no problem. It's working fine now. Thanks
 
Hi,

I got a similar problem. I just wanted to edit the parking codes. Nothing more....

Compiler Errors Found. These were not identified by the Issue Manager. Please let us know
what the compiler error is so that we can improve the Issue Manager.

The compiler message is shown below

ScruffyDuck Scenery Design Engine Compiling
Using BglComp....


Parsing document: E:\MSFS\FS Design Tools\Airport Design Editor 165\!AdeTempWorkOnly\EHAM_ADEX_PvA.xml

WARNING: #C1102 EHAM 1601191 RUNWAY 5000 Airport (EHAM) has object (RUNWAY) that is 1601191 meters from the ARP with a test threshold of 5000 meters! XML line: 65.
WARNING: #C1102 EHAM 1601191 RUNWAY 5000 Airport (EHAM) has object (RUNWAY) that is 1601191 meters from the ARP with a test threshold of 5000 meters! XML line: 108.
WARNING: #C1102 EHAM 1601191 RUNWAY 5000 Airport (EHAM) has object (RUNWAY) that is 1601191 meters from the ARP with a test threshold of 5000 meters! XML line: 151.
WARNING: #C1102 EHAM 1601191 RUNWAY 5000 Airport (EHAM) has object (RUNWAY) that is 1601191 meters from the ARP with a test threshold of 5000 meters! XML line: 194.
WARNING: #C1102 EHAM 1601191 RUNWAY 5000 Airport (EHAM) has object (RUNWAY) that is 1601191 meters from the ARP with a test threshold of 5000 meters! XML line: 237.
WARNING: #C1102 EHAM 1601191 RUNWAY 5000 Airport (EHAM) has object (RUNWAY) that is 1601191 meters from the ARP with a test threshold of 5000 meters! XML line: 280.
WARNING: #C1102 EHAM 1601191 RUNWAY 5000 Airport (EHAM) has object (RUNWAY) that is 1601191 meters from the ARP with a test threshold of 5000 meters! XML line: 323.
WARNING: #C1102 EHAM 1601191 RUNWAY 5000 Airport (EHAM) has object (RUNWAY) that is 1601191 meters from the ARP with a test threshold of 5000 meters! XML line: 366.
WARNING: #C1102 EHAM 1601191 RUNWAY 5000 Airport (EHAM) has object (RUNWAY) that is 1601191 meters from the ARP with a test threshold of 5000 meters! XML line: 409.
WARNING: #C1102 EHAM 1601191 RUNWAY 5000 Airport (EHAM) has object (RUNWAY) that is 1601191 meters from the ARP with a test threshold of 5000 meters! XML line: 452.
WARNING: #C1102 EHAM 5530 RUNWAY 5000 Airport (EHAM) has object (RUNWAY) that is 5530 meters from the ARP with a test threshold of 5000 meters! XML line: 600.
WARNING: #C1102 EHAM 6974 START 5000 Airport (EHAM) has object (START) that is 6974 meters from the ARP with a test threshold of 5000 meters! XML line: 992.
WARNING: #C1102 EHAM 7013 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 7013 meters from the ARP with a test threshold of 5000 meters! XML line: 2426.
WARNING: #C1102 EHAM 5099 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5099 meters from the ARP with a test threshold of 5000 meters! XML line: 2468.
WARNING: #C1102 EHAM 5054 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5054 meters from the ARP with a test threshold of 5000 meters! XML line: 2474.
WARNING: #C1102 EHAM 5517 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5517 meters from the ARP with a test threshold of 5000 meters! XML line: 2480.
WARNING: #C1102 EHAM 5236 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5236 meters from the ARP with a test threshold of 5000 meters! XML line: 2510.
WARNING: #C1102 EHAM 5357 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5357 meters from the ARP with a test threshold of 5000 meters! XML line: 3248.
WARNING: #C1102 EHAM 5028 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5028 meters from the ARP with a test threshold of 5000 meters! XML line: 3260.
WARNING: #C1102 EHAM 5086 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5086 meters from the ARP with a test threshold of 5000 meters! XML line: 3908.
WARNING: #C1102 EHAM 5017 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5017 meters from the ARP with a test threshold of 5000 meters! XML line: 4616.
WARNING: #C1102 EHAM 5053 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5053 meters from the ARP with a test threshold of 5000 meters! XML line: 4622.
WARNING: #C1102 EHAM 5308 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5308 meters from the ARP with a test threshold of 5000 meters! XML line: 4628.
WARNING: #C1102 EHAM 5412 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5412 meters from the ARP with a test threshold of 5000 meters! XML line: 4634.
WARNING: #C1102 EHAM 5448 TAXI_POINT 5000 Airport (EHAM) has object (TAXI_POINT) that is 5448 meters from the ARP with a test threshold of 5000 meters! XML line: 4640.
WARNING: #C1102 EHAM 5100 APRON_VERTEX 5000 Airport (EHAM) has object (APRON_VERTEX) that is 5100 meters from the ARP with a test threshold of 5000 meters! XML line: 31236.
WARNING: #C1102 EHAM 5003 APRON_VERTEX 5000 Airport (EHAM) has object (APRON_VERTEX) that is 5003 meters from the ARP with a test threshold of 5000 meters! XML line: 31239.
WARNING: #C1102 EHAM 7035 APRON_VERTEX 5000 Airport (EHAM) has object (APRON_VERTEX) that is 7035 meters from the ARP with a test threshold of 5000 meters! XML line: 31270.
WARNING: #C1102 EHAM 6989 APRON_VERTEX 5000 Airport (EHAM) has object (APRON_VERTEX) that is 6989 meters from the ARP with a test threshold of 5000 meters! XML line: 31273.
WARNING: #C1102 EHAM 5399 TAXIWAY_SIGN 5000 Airport (EHAM) has object (TAXIWAY_SIGN) that is 5399 meters from the ARP with a test threshold of 5000 meters! XML line: 31626.
WARNING: #C1102 EHAM 5263 TAXIWAY_SIGN 5000 Airport (EHAM) has object (TAXIWAY_SIGN) that is 5263 meters from the ARP with a test threshold of 5000 meters! XML line: 31633.
WARNING: #C1102 EHAM 5238 TAXIWAY_SIGN 5000 Airport (EHAM) has object (TAXIWAY_SIGN) that is 5238 meters from the ARP with a test threshold of 5000 meters! XML line: 31668.
WARNING: #C1102 EHAM 5221 TAXIWAY_SIGN 5000 Airport (EHAM) has object (TAXIWAY_SIGN) that is 5221 meters from the ARP with a test threshold of 5000 meters! XML line: 31675.
WARNING: #C1102 EHAM 5035 TAXIWAY_SIGN 5000 Airport (EHAM) has object (TAXIWAY_SIGN) that is 5035 meters from the ARP with a test threshold of 5000 meters! XML line: 31717.
WARNING: #C1102 EHAM 5256 TAXIWAY_SIGN 5000 Airport (EHAM) has object (TAXIWAY_SIGN) that is 5256 meters from the ARP with a test threshold of 5000 meters! XML line: 33229.
INTERNAL COMPILER ERROR: #C2591: Taxi path #102 references a non-existent Runway #36 at airport EHAM.
INTERNAL COMPILER ERROR: #C2591: Taxi path #105 references a non-existent Runway #36 at airport EHAM.
INTERNAL COMPILER ERROR: #C2591: Taxi path #186 references a non-existent Runway #36 at airport EHAM.
INTERNAL COMPILER ERROR: #C2591: Taxi path #842 references a non-existent Runway #36 at airport EHAM.


Parse complete!

Any help is appreciated. Thank you
Peter
 

Attachments

Well that appears to be a bgl file created with AFX. AFX does its own compiling and does not always follow the rules of the Microsoft Compiler. The warnings are not errors just that the airport test radius is small or non existent. As for the errors they are what they say. It appears that four runway links have the wrong runway reference on them. I don't think AFX checks or cares about that.

Best to load the AFX file into ADE and save it as an ADE project file, Then change the airport test radius to eliminate the warnings. Also when I load the bgl file the Issue Manager is Red and any errors there should be fixed. Finally go to the Taxi Link List and try to find and fix those bad taxi paths
 
Thank you Jon,

I thought using an original afcad by aerosoft. Obviously I was wrong. Sorry for that. Editing and compiling the original afcad works. Are all afcads by AS compatible to ADE? And how did you find out the other afcad was created with AFX?
Peter
 
You can, of course, use any bgl file that contains an airport with ADE but since the ADE project file contains information not stored in the bgl file it is always best to save the project once loaded to the ADE project format (Save in ADE will do that). Work from that and compile from that. Never load back the Bgl file once you have a project file.

Compatible with ADE is not actually the right question ;) The issue is whether they are compatible with Microsoft's Bgl Compiler. AFCAD and AFX use their own home grown compilers and while the sim will accept the output they do some things which are not allowed in the MS Compiler. We took the decision right at the start to use the official compilers to ensure the best chance the output will work. It also makes it a bit easier when it comes to new features in the compilers - we just need to support generating the right XML code.

I guess the fact that the file name starts with AFX gave that away :) However we can usually tell if we see things that are not allowed in the MS/P3D compilers
 
Thank you for your replies. Do you have the original afcads of AS EHAM? Maybe you have better ones? Unfortunately the backup folder is empty and I´m not a supporter of reinstallations. Maybe all afcads are not original aynmore. The ones I have start all with AFX_EHAM_02_EAST/NORTH/SOUTH/WEST, 138kbs and out of 01.11.2010 indicated in WE.
Looking at the ADE manual is very challenging, and I´m sure to have a deeper study some time, but for now I will stay on course with my AI-Traffic planning. When returning to ADE, I will remember your backup advice.
 
You must log in or register to reply here.
Back
Top