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

MSFS20 Scenery Output Paths

Rotornut44

Resource contributor
Messages
673
Country
us-florida
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.
 
Last edited:
Here's what I use:

XML:
<AssetPackage Name="rhumbaflappy-airport-c59-lakelawn" Version="0.1.0">
    <ItemSettings>
        <ContentType>SCENERY</ContentType>
        <Title>Lake Lawn Airport</Title>
        <Manufacturer>rhumbaflappy</Manufacturer>
        <Creator>rhumbaflappy</Creator>
    </ItemSettings>
    <Flags>
        <VisibleInStore>false</VisibleInStore>
        <CanBeReferenced>false</CanBeReferenced>
    </Flags>
    <AssetGroups>

        <AssetGroup Name="ContentInfo">
            <Type>Copy</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageDefinitions\rhumbaflappy-airport-c59-lakelawn\ContentInfo\</AssetDir>
            <OutputDir>ContentInfo\</OutputDir>
        </AssetGroup>

        <AssetGroup Name="MarketplaceData">
            <Type>MarketplaceData</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageDefinitions\rhumbaflappy-airport-c59-lakelawn\MarketplaceData</AssetDir>
            <OutputDir>MarketplaceData\rhumbaflappy-airport-c59-lakelawn</OutputDir>
        </AssetGroup>

        <AssetGroup Name="myairport">
            <Type>BGL</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\rhumbaflappy-c59-airport\</AssetDir>
            <OutputDir>scenery\rhumbaflappy\LakeLawn\</OutputDir>
        </AssetGroup>

        <AssetGroup Name="mymaterials">
            <Type>MaterialLib</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\rhumbaflappy-c59-materials\</AssetDir>
            <OutputDir>MaterialLibs\rhumbaflappy\</OutputDir>
        </AssetGroup>

        <AssetGroup Name="mymodellib">
            <Type>ModelLib</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\rhumbaflappy-c59-modelLib\</AssetDir>
            <OutputDir>scenery\rhumbaflappy\LakeLawn\</OutputDir>
        </AssetGroup>

        <AssetGroup Name="myscene">
            <Type>BGL</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\rhumbaflappy-c59-scene\</AssetDir>
            <OutputDir>scenery\rhumbaflappy\LakeLawn\</OutputDir>
        </AssetGroup>

        <AssetGroup Name="myscripts">
            <Type>BGL</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\rhumbaflappy-c59-scripts\</AssetDir>
            <OutputDir>scenery\rhumbaflappy\LakeLawn\</OutputDir>
        </AssetGroup>

        <AssetGroup Name="myshapes">
            <Type>BGL</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\rhumbaflappy-c59-shapes\</AssetDir>
            <OutputDir>scenery\rhumbaflappy\LakeLawn\</OutputDir>
        </AssetGroup>

        <AssetGroup Name="mysimobjectanimals">
            <Type>SimObject</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\rhumbaflappy-c59-simobjects\SimObjects\Animals\rhumbaflappy-c59-Bears\</AssetDir>
            <OutputDir>SimObjects\Animals\rhumbaflappy-c59-Bears\</OutputDir>
        </AssetGroup>

        <AssetGroup Name="mysimobjectmisc01">
            <Type>SimObject</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\rhumbaflappy-c59-simobjects\SimObjects\Misc\AngryGretchen</AssetDir>
            <OutputDir>SimObjects\Misc\AngryGretchen\</OutputDir>
        </AssetGroup>

        <AssetGroup Name="mysimobjectmisc02">
            <Type>SimObject</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\rhumbaflappy-c59-simobjects\SimObjects\Misc\SimpleHangar</AssetDir>
            <OutputDir>SimObjects\Misc\SimpleHangar\</OutputDir>
        </AssetGroup>



        <AssetGroup Name="Secondary aerial">
            <Type>CGL</Type>
            <AssetDir>PackageSources\rhumbaflappy-c59-aerial\CGL\</AssetDir>
            <OutputDir>CGL</OutputDir>
        </AssetGroup>

    </AssetGroups>
</AssetPackage>


Untitled.png


So I'm using just "scenery\<companyname>\" as the packagename already has the airport name and ID.
 
<OutputDir>scenery\rhumbaflappy\LakeLawn\</OutputDir>
This would be the "scenery\<companyname>\<airport>\" format I mentioned above.

"scenery\<companyname>\" would just be <OutputDir>scenery\rhumbaflappy\</OutputDir>

Thanks for the input! :)
 
Thanks Rhumbaflappy, was curious too because the Editor is doing weird things atm, for me at least.

If i add an airport object bgl, the output path is automatically set to something like xxx/sceneries/xxx and when i add a modelLib it autofills to xxx/scenery/xxx. What means one ends up with a weird structure. Why does it autofill it like this, makes no sense to me?
 
Back
Top