In the second biasX="nnn.nnnM" statement removing the M caused no errors in that section. My question is in part if bgl2xml and the XML saved output both have the same error regarding DeleteAllApronLights instead of DeleteAllApronlights tokens if there is an error in a common table used by both utilities, one within ADE.Įditing either XML produced file correcting said delete statement no longer through errors in compiling with bglcompiler. No errors for either airport were noted in a direct compile from ADE. Once again since it was output in decompiling to XML it must have made it into the ADE produced bgl. I don't know if the M was entered in the value directly by the author or was produced by object dragging. Only numerical values are allowed and the type has been predefined as always meters. In one scenery a Vertex group had incorrect BIAS statements as follows:īiasXYX is defined as type ctBias defined as taking a double with no character modifiers such as the M above probably intended as "Meters" if a choice was offered. However compilation did output and decompilation showed the statement remained. Feeding the XML into the bglcompiler with your GUI front end threw the Error Message about DeleteAllApronLights not being a valid token. In the AED XML output and BG2XML output contain the group Delete Airport and within: I also verified the source to schema using the Editix XML editor and it noted the same errors in both sceneries delineated as follows: In trouble shooting two sceneries from different authors I came across a deviation in syntax and allowed variable type in examining a direct XML output generated from a decompiled output using BGL2XML and independently entering the sceneries with Open Airport from BGL in ADE 150.5 for FS9.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |