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

Compiling Errors due to Fences

F

fcerven

Messages
2
Country
us-idaho
I am getting compile errors when I try to compile any airport with a fence to a BLG. This happens even if no modifications have been made to the file.

For example, I load KGEG ( Spokane Intl.) and then try to re-compile without changing anything and I get dozens of compile errors having to do with the fences. And this is without changing the ones that came with the file originally. If I remove the fences, the file compiles without error. I have tried several other airports and get the same results.

So, I can change anything I want but can't keep the fences. But I like the fences.:)

Am I missing something?

Thanks in advance for any help.
 
Exactly as Meshman said, the original SDK's BglComp.exe had a bug which caused boundary fences to create errors when being compiled. Updating your SDK to the lastest version will fix this problem.

-Russell
 
Thanks for the quick reply guys. You were right, it was an outdated SDK.

I should have provided pertinent specs for my machine in the first post but forgot. System specs are a C2D E6300 OC to 2.6 GHz, 2 GIG 800GHz memory, NVidia 7900GS, XP SP2 32 bit,and FSX SP1 Deluxe.

Turns out my FSX SDK was version 1. Updating to a newer version for FSX SP1 solved the problem.

Thanks again.
 
You must log in or register to reply here.
Back
Top