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

P3D v2 Compile error

Messages
293
Country
us-virginia
Using latest version of ADE (v01.66.5555). I got this error.

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:\Scenery Design\ADE1.65\!AdeTempWorkOnly\FTX_SCA_KSMX_ADE2.xml

INTERNAL COMPILER ERROR: #C2451: Display character expected at offset (5) in Taxiway Sign label: ldm12-30
INTERNAL COMPILER ERROR: #C2448: Invalid format for Taxiway Sign label: ldm12-30
INTERNAL COMPILER ERROR: #C2031: Failed element parse <TaxiwaySign>
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 = California
ERROR: city = Santa Maria
ERROR: name = Santa Maria Pub/Capt Hancock
ERROR: lat = 34.8989168554544
ERROR: lon = -120.457444489002
ERROR: alt = 260.997F
ERROR: magvar = -14.5
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 16404.2F
ERROR: ident = KSMX
ERROR: >
ERROR: <TaxiwaySign
ERROR: lat = 34.8982823651022
ERROR: lon = -120.453888438011
ERROR: heading = 332.804170143696
ERROR: label = ldm12-30
ERROR: size = SIZE3
ERROR: justification = RIGHT
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2451: Display character expected at offset (1) in Taxiway Sign label: dl[A]dA7'
INTERNAL COMPILER ERROR: #C2448: Invalid format for Taxiway Sign label: dl[A]dA7'
INTERNAL COMPILER ERROR: #C2031: Failed element parse <TaxiwaySign>
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 = California
ERROR: city = Santa Maria
ERROR: name = Santa Maria Pub/Capt Hancock
ERROR: lat = 34.8989168554544
ERROR: lon = -120.457444489002
ERROR: alt = 260.997F
ERROR: magvar = -14.5
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 16404.2F
ERROR: ident = KSMX
ERROR: >
ERROR: <TaxiwaySign
ERROR: lat = 34.8943713751261
ERROR: lon = -120.445484685404
ERROR: heading = 45
ERROR: label = dl[A]dA7'
ERROR: size = SIZE3
ERROR: justification = RIGHT
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2607: Compilation errors detected, compilation failed!


Parse complete!


Thanks,

Todd
 
OK - this seems to be a taxi sign created by a program that does not conform to the SDK. The immediate solution is to find that sign and fix it. Does the Issue Manager show Red?
 
The issue manager is green. I don't know what other program there could be because all signs were created in ADE.
 
OK, found the problem. The two taxi signs had an extra character in the sign definition that didn't affect the appearance of the sign but apparently mucked up the compilation.
 
That would do it and ADE can't always tell if the sign is bad.
 
Back
Top