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

Almost There

Hi Arno:

If we have a static Sketchup 3D model mapped with (1) custom photo-real texture Material sheet, Geo-located (and placed with AGL / Heading etc.):

* Can MCX import that ex: *.KMZ, convert, and export it as a 'placed' MSFS Scenery project ...ready for processing by the MSFS-2020 SDK package compiler ?
Hi Gary,

No, at the moment that is not supported. Since I feel it is not efficient to make a separate package from each single object, MCX can only export the glTF object at the moment. It is up to the developer to place it in the right package.

* Can MCX import that ex: *.KMZ, convert, and export it as a 'compiled' MSFS Scenery package ...ready to add to the MSFS-2020 \Community sub-folder ? :scratchch
This one is related with the one above. Since MCX makes no complete package, it can also not compile that package to a BGL file.

If many developers think it is useful to be able to export packages, I can of course add that. But at the moment might feeling is that this is not really useful, as you don't want each object to become a separate package.

Thanks, Arno. :)

IIUC, via MSFS SDK, one may: :scratchch

* combine multiple glTF objects in (1) project

...with:

* (1) PackageSources\ModelLib local sub-folder chain for each Project

...consisting of:

* (1) locally paired \[object name] sub-folder chain (named for each such glTF object)

...and:

* (1) locally paired \Texture sub-folder

...which are collectively:

* compiled to (1) ModelLib "library-type" package

...that outputs:

(1) *.BGL containing multiple glTF objects

...mapped to texture Materials within:

(1) Package output \Texture sub-folder



[012] Multiple Custom Models In One Project​



GaryGB
 
Last edited:

rhumbaflappy

Administrator
Staff member
Resource contributor
Hi Gary. MCX already can do multiple conversion with a small amount of extra work. Use batch conversion. Convert whole library BGLs to different ModelLib folders. Each folder needs it's own texture folder.
XML:
<AssetPackage Name="cfs2-scenery-rhumbaflappy" Version="0.1.0">
    <ItemSettings>
        <ContentType>SCENERY</ContentType>
        <Title>Cfs2 Conversion Libraries</Title>
        <Creator>rhumbaflappy</Creator>
        <Description/>
    </ItemSettings>
    <Flags>
        <VisibleInStore>false</VisibleInStore>
        <CanBeReferenced>false</CanBeReferenced>
    </Flags>
    <AssetGroups>
        <AssetGroup Name="ContentInfo">
            <Type>Copy</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageDefinitions\cfs2-scenery-rhumbaflappy\ContentInfo\</AssetDir>
            <OutputDir>ContentInfo\cfs2-scenery-rhumbaflappy\</OutputDir>
        </AssetGroup>
        <AssetGroup Name="modellib01">
            <Type>ArtProj</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\CFS2-vehicle-modelLib\</AssetDir>
            <OutputDir>scenery\rhumbaflappy\</OutputDir>
        </AssetGroup>
                <AssetGroup Name="modellib02">
            <Type>ArtProj</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\CFS2-inf-modelLib\</AssetDir>
            <OutputDir>scenery\rhumbaflappy\</OutputDir>
        </AssetGroup>
    </AssetGroups>
</AssetPackage>

This sets up 2 modelLib folder libraries.

multiple.png


packages.png


result.png



And just for fun, I had MCX export the textures as JPG.
 
Last edited:
Thanks, Dick, for posting that interesting 'worked example'. :)


This may be a good excuse for me to re-install CFS2, so I can walk through the same steps to directly visualize this process. :coffee:

Hmmm... that may then compel flying my Abacus PBY Catalina, and shooting some (loud !) tracer rounds into the South seas. :cool:

GaryGB
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Hi Gary,

Yes, I know the SDK can make libraries. But most packages will contain more than that library. So therefore I don't feel it makes sense to export a library only package from MCX. Because the entire package needs to be processed at once by the package tool.
 
Top