- Messages
- 8,893
Jose
I have been doing that since FS9 went to XML and my very early uploads such as EHAM on AVSIM uses 2 bgl files.
I used AFCAD to do all the airport work (runway number changes, xwind runways add the new runway, etc.) and then wrote a 2nd XML with all the exclusions, scenery, approach code, etc. I placed the approach bgl into the Generic/Global scenery folder and the AFCAD up in Addon scenery.
FS reads the default bgl then upward to the Global/Generic\scenery then upward again to the Addon Scenery folder.
In that manner the excludes, scenery, taxiway signs, all approach data are read after the default bgl with proper excludes and deleteall ='s but before the AFCAD in the addon scenery folder which uses additional DeleteAll='s.
That creates another problem because AFCAD and ADE/FSXPlanner does not read backwards through the Global/Generic folder and only works in combination with the default bgl.
I don't know how the actual bgl is read but it does load normally first and then FS decides on what to use and not use if airport data is placed at a higher priority.
I am trying to see my way clear because ADE and FSXPlanner can allow for some additional XML that AFCAD did not allow. However there are still some issues that Jon has to sort out of what is allowed in the xml copied from the default bgl.
This may also cause a problem if 2 bgl's have to be made and are placed in the same folder such as the addon scenery\scenery folder. In FS9 this is where the Generic folder worked flawlessly because it is a go between folder.
Rather then 2 airport bgl's to make 1 airport the Generic/Global folder allows for 3 bgl's to make up 1 airport. That may not make sense yet but I have a new topic post coming that explains many of the loading processes FS uses.
I have been doing that since FS9 went to XML and my very early uploads such as EHAM on AVSIM uses 2 bgl files.
I used AFCAD to do all the airport work (runway number changes, xwind runways add the new runway, etc.) and then wrote a 2nd XML with all the exclusions, scenery, approach code, etc. I placed the approach bgl into the Generic/Global scenery folder and the AFCAD up in Addon scenery.
FS reads the default bgl then upward to the Global/Generic\scenery then upward again to the Addon Scenery folder.
In that manner the excludes, scenery, taxiway signs, all approach data are read after the default bgl with proper excludes and deleteall ='s but before the AFCAD in the addon scenery folder which uses additional DeleteAll='s.
That creates another problem because AFCAD and ADE/FSXPlanner does not read backwards through the Global/Generic folder and only works in combination with the default bgl.
I don't know how the actual bgl is read but it does load normally first and then FS decides on what to use and not use if airport data is placed at a higher priority.
I am trying to see my way clear because ADE and FSXPlanner can allow for some additional XML that AFCAD did not allow. However there are still some issues that Jon has to sort out of what is allowed in the xml copied from the default bgl.
This may also cause a problem if 2 bgl's have to be made and are placed in the same folder such as the addon scenery\scenery folder. In FS9 this is where the Generic folder worked flawlessly because it is a go between folder.
Rather then 2 airport bgl's to make 1 airport the Generic/Global folder allows for 3 bgl's to make up 1 airport. That may not make sense yet but I have a new topic post coming that explains many of the loading processes FS uses.
