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

Confused - Proper _Obj.bgl Install Location

jordanal

jordanal

Messages
78
Country
us-florida
Hi all,
I just realized that there may be some confusion regarding the proper install-location of the _Obj.bgl file within FSX. In most of the readme.txt instructions from fine AFCAD developers such AIG and K. Agazi, we are told to unzip the file into same folder as the _cvx.bgl and SomenameAFCAD.bgl. OK, no problem - easy peazy :p

But then I have instructions from other fine folks like Ray Smith who instruct us to put the _Obj.bgl in the FSX\Scenery\Global\Scenery folder. This meathod obviously makes it harder to track AFCAD conflicts, even using the FS Airport Scanner tool (which doesn't track cvx or obj conflicts anyway).

My question, is there really one proper meathod of installing the _Obj.bgl file or is it completely dependent on the developer and some unique meathod they may have used to derive the file?
 
_OBJ and _CVX should go with the airport Bgl File. The file that must go into FSX\Scenery\Global\Scenery is the _ALT file. The _ALT file will only be created in case you have changed the airport altitude.
 
jordanal said:
Hi all,
I just realized that there may be some confusion regarding the proper install-location of the _Obj.bgl file within FSX. In most of the readme.txt instructions from fine AFCAD developers such AIG and K. Agazi, we are told to unzip the file into same folder as the _cvx.bgl and SomenameAFCAD.bgl. OK, no problem - easy peazy :p

But then I have instructions from other fine folks like Ray Smith who instruct us to put the _Obj.bgl in the FSX\Scenery\Global\Scenery folder. This meathod obviously makes it harder to track AFCAD conflicts, even using the FS Airport Scanner tool (which doesn't track cvx or obj conflicts anyway).

My question, is there really one proper meathod of installing the _Obj.bgl file or is it completely dependent on the developer and some unique meathod they may have used to derive the file?
Click to expand...

Placing certain type bgl's into the FS\Scenery\Global\scenery folder is a holdover from FS9. In FS9 the folder name was FS9\Scenery\Generic\Scenery folder.

In FS9 the AFCAD utility did not allow any type excludes, scenery, taxiway signs or approach code to be compiled. We had to hand write those bgl's as a seperate type file. As per MS and the SDk we placed those files in the lower FS9\Scenery\Generic\Scenery folder so they could load first. These bgl's also in most cases had exclusion rectangles so we did not have to worry about naming the exclude bgl with a number prefix.

It gets more complicated then that. AFCAD set the approach deleteAll flag in the execution of the compiler to FALSE. We would hand write the approach code and set the flag to TRUE. Since AFCAD by default set a FALSE flag we had to keep the approach code out of the same folder the AFCAD airport bgl was nesting in.

AFCAD does not have the ability to read files backwards from the Addon Scenery\scenery folder back to the AP9 generic scenery folder then the default airport AP9 bgl.

FS9 on the other hand can read both ways and construct the airport properly. The end result is we write the approach code and unblock the deleteAll approach code tag by using TRUE. This file is placed into the FS9 Scenery\Generic\Scenery folder. Now we build the airport with AFCAd which sets the approach code tag to FALSE. This bgl sets higher and placed into the Addon Scenery\Scenery folder.

ADE9X in all its wisdom eliminated the need for either the FS9 Scenery\Generic\scenery folder or the FSX Scenery\Global\scenery folder. We set ADE9X with proper blocking statements and listed the XML in proper order to handle all the exclusions, scenery, taxiway signs and approach code.

If someone insist on using AFCAD for FS9 and wants excludes, scenery, taxiway signs, approach code, etc. then it becomes important on where some of these multiple bgl's are placed so FS9 can read them properly.
 
You must log in or register to reply here.
Back
Top