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

SDK problems

Messages
194
Country
unitedstates
If I understand correctly, Airport Design Editor is not compatible with the original FSX SDK. However, it appears that if you upgrade the SDK, you must also upgrade FSX to the compatible version.....i.e. you must install FSX SP1 to use the SP1 SDK. Is this correct? Is there a work around for anyone who wants to continue with the RTM FSX version, but would like to be able to use FDE?

Thanks.
 
If I understand correctly, Airport Design Editor is not compatible with the original FSX SDK. However, it appears that if you upgrade the SDK, you must also upgrade FSX to the compatible version.....i.e. you must install FSX SP1 to use the SP1 SDK. Is this correct? Is there a work around for anyone who wants to continue with the RTM FSX version, but would like to be able to use FDE?

Thanks.

I don't think so. There is a general problem with the RTM version of BglComp. It does not recognize boundary fences. Maybe someone else will know for sure but if this is just for ADE then I think upgrading the SDK alone should be enough.
 
EDIT*******

Sorry Jon we cross posted



The problem is not that ADE is not compatible with the RTM FSX version but the compiler and schema files have some compiling issues with Boundary Fences that SP1a fixed.

There is a possible solution. You need 2 files from the SP1a SDK. You could add the SP1 service pack to FSX and then load the SP1a SDK.

Copy the BGLComp.exe and the BGLComp.xsd to a temp folder. Now uninstall the SP1a SDK and the SP1 servive pack (in that order) from the settings /Control panel //add/remove window giving you back the RTM versions of FSX. You will probably have to add back the RTM SDK from the original deluxe FSX disk. When you remove the SDK SP1a from Windows I don't think it rolls back to the previous RTM SDK.

Make backups of the RTM BGLComp files and use the SP1a SDK compiler files in their place.

The BGLComp.exe and the BGLComp.xsd are stand alone compiler files. You can place them anywhere including a work folder for ADE. However you must either manually compile your XML with a drag over using the mouse or point ADE to the folder that has the updated BGLcomp files so it can find them.

I have all 3 versions of the 2 compiler files on my computer and they all work except the RTM version if I try and compile a XML that has a Boundary Fence. Each time I upgraded FSX from RTM to SP1 service pack to SP2 I copied the 2 compiler files from the SDK's so I had all 3 versions even though I am now using SP2.

another solution

You could also open the stock airport you are working on and delete the entire Boundary Fence (and possibly any Blast fences). The draw back to this is the RTM compiler will compile the ADE bgl but you will not have a Boundary Fence around the airport.
 
Thanks, Jon and Jim. I'll report back. At this point it seems the simple solution is to delete the boundary fence.
 
Back
Top