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

Another airport, other errors

F

freson

Messages
9
Country
netherlands
Hi,

After the errors in my XML for Rotterdam (EHRD) which were all solved with the help of you guys (thanks again), I again have some errors after editing an airport.

I started updating Amsterdam Airport (EHAM) and during compile I got some errors.
One of the errors has got something to do with a 'leg'. After searching this forum I found that I could be a problem with Bglcomp.
I made sure I have the bglcomp from the SDK sp1a installed so that's not the cause of the problem.

To see if the error was caused by me I decided to compile the original (stock) XML.
The same errors show up.

I understand that the errors are caused by wrong or missing data but I absolutely have no clue were to search or what to search for.

The strange thing is that the error is already in the stock Amsterdam file.

Would you take a look at the problem?
I've included the original (FSX) XML-file and a text file with the error message.

Thanks,
Fred
 

Attachments

I have identified the cause of this error. It's actually the same as one that another user was getting associated with Leg elements. It has been fixed for the next release.

For now the work around is to uncheck the Write Approaches and Delete All Approaches options from with the Prepare Options dialog (Compile -> Prepare Options).

-Russell
 
You must log in or register to reply here.
Back
Top