Rotornut44
Resource contributor
- Messages
- 673
- Country

I've had this question brewing for a while and would love to hear other's input on this.
This discussion is about the file output path/directory for scenery, which is set in the inspector window.
In the beginning, it was recommended to use "scenery\global\scenery\" (Used for Object Libraries) and "scenery\world\scenery\" (Used for all other BGLs) output paths for BGLs. I have always used this method, but in their samples, Asobo still has their outputs set to "scenery\mycompany\", which I'm pretty sure has been the same since the first SDK versions.
However, looking at airports currently in the official packages folder, Asobo/Microsoft currently uses "scenery\<companyname>\<airport>\".
Considering what I believe about how MSFS mounts packages, this seems like a more compatible structure to serve the files to MSFS. Especially when you consider the odd times that the scenery editor names your BGL(s) CVX(_etc).bgl instead of the file name that you set on the XML. I would think that if you had several instances like this, not just CVX naming, but conflicting file names in general, having them all mounted in world/global paths would cause a conflict at some point?
So, why was it recommended to use global and world structures in the first place?
I'd love to hear anyone else's take on this. From here on out, I'm considering switching to "scenery\<companyname>\<airport>\" format, as it seems, to me, to be the better option.
This discussion is about the file output path/directory for scenery, which is set in the inspector window.
In the beginning, it was recommended to use "scenery\global\scenery\" (Used for Object Libraries) and "scenery\world\scenery\" (Used for all other BGLs) output paths for BGLs. I have always used this method, but in their samples, Asobo still has their outputs set to "scenery\mycompany\", which I'm pretty sure has been the same since the first SDK versions.
However, looking at airports currently in the official packages folder, Asobo/Microsoft currently uses "scenery\<companyname>\<airport>\".
Considering what I believe about how MSFS mounts packages, this seems like a more compatible structure to serve the files to MSFS. Especially when you consider the odd times that the scenery editor names your BGL(s) CVX(_etc).bgl instead of the file name that you set on the XML. I would think that if you had several instances like this, not just CVX naming, but conflicting file names in general, having them all mounted in world/global paths would cause a conflict at some point?
So, why was it recommended to use global and world structures in the first place?
I'd love to hear anyone else's take on this. From here on out, I'm considering switching to "scenery\<companyname>\<airport>\" format, as it seems, to me, to be the better option.
Last edited:

