Hi Obie:
This thread has a mix of terms, concepts and names being used which relate to different FS utilities, which IMHO might lead to confusion for yourself and other readers.
Perhaps a few questions and comments might make things clearer so a workflow more specific to your task(s) might be established.
Thanks Gary I appreciate the response
Are the scenery object library BGLs you are trying to combine into a single larger library BGL ...from other authors ?
Yes, this is basically a housekeeping exercise to consolidate a number of scenery objects into one cohesive BGL library. I have so many "libraries" in the LOM it is unwieldy trying to find a specific object. This question pertains to creating a library solely for use in the LOM.
For instance I might combine a number of objects into a library called "WWII Military Objects.BGL". I am stymied by the inefficiency of the organization of the LOM. It is mostly due to the haphazard organization of the various object libraries imported, not the design of ADE itself. Often it requires looking thru many thumbnails to find a particular object you are seeking.
As I understand it, FSX will look for the object when it is called for in an airport scenery by the GUID, not the library. In my FSX world all these freeware third party libraries reside in an Addon Scenery folder called "Static Objects Library" and it contains most of my addon object libraries.These are separate scenery object BGL's from often different designers.
If so, you should
not plan to distribute the resulting combined BGL to any other person for use on their FS computer ...without first getting written permission of the authors of those original libraries.
Yes Gary in NO way do I plan to distribute these BGL libraries. They are for internal use only.
If the resulting combined scenery object library BGL will be used
only on your own FS computer, first be aware that
having many "separate" scenery object library BGLs installed and 'active' in the FS scenery library does not in itself affect performance at run time during a flight.
I don't think this is an issue, my old XP computer loads slowly anyway but all addon sceneries are on an SSD.
However, having many "separate" scenery object library BGLs installed and 'active' in the FS scenery library will likely result in
only a slightly slower initial start up of FS itself while it "inventories" those BGLs, their internal MDLs, and all mapped textures; after that
performance is not likely to be affected at run time during a flight.
Likewise, having many "separate" scenery object library "placement" BGLs installed and 'active' in the FS scenery library
will not be likely to affect performance at run time during a flight, but would likely result in a slightly slower initial start up of FS itself, as IIUC, placement instruction BGLs mapped to scenery objects are "inventoried" independently along with those mapped scenery objects, scenery object library BGLs and their internal MDLs, and all mapped textures.
So, we might ask if it is even necessary or desirable to combine scenery object libraries or placement BGLs into a single larger library BGL.
Yes the only reason for the complilation is to organize the LOM more efficiently
If some of the objects are FS9 format MDLs and you wish to
convert them to FSX format MDLs, that would involve a workflow utilizing
ModelConverterX (aka "
MCX" by Arno Gerritsen ...and not to be confused with "
MDLC" by Ivan Hsu and/or the windows GUI mod of same "
Mk_Mdl_Ver_2.0+" by Morten Krogstad).
FYI: MCX does have the ability to import and batch convert (with placement info if desired) legacy MDL format scenery object library BGLs and older SCASM (non-MDL code format) scenery object BGLs.
Depending on what format the imported scenery object files are in, additional steps may be required to prepare SCASM source code for processing by MCX so they can be imported and then converted etc..
All files are in BGL format
It would be helpful to more thoroughly identify what your goal is, so a workflow can be established.
I hope I have explained my goal clearly. It is to compile a number of descriptive, logical libraries for quick access in the LOM during airport design w/ ADE.
GaryGB