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

MSFS SDK MERGING PROJECTS

Messages
13
Country
france
Hi fellow MSFS SDK developers,

I read many threads from FSDEVELOPER, yet I cannot find a reliable process to merge projects.

I have multiple projects.
Each project has a single scenery file (model + textures).

How can I merge these multiple projects into a single project ?
Can you explain a step by step process ?

Thank you for your help and sharing your knowledge
 
You want to combine models and textures from different projects into one project?
Untitled.png


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

All models are combined into one library and the compiled package has one BGL and one texture folder for them.
 
If you don't want to 'categorize' your models, you can just put them all in the same model folder, just like the textures all go into their same folder.
 
Your reply is fast and detailed ! (I love your profile picture ☺️)

What about the scenery.xml files of the different projects ? How do you merge them ?
 
If you don't want to 'categorize' your models, you can just put them all in the same model folder, just like the textures all go into their same folder.
Your reply is fast and detailed ! (I love your profile picture ☺️)

What about the scenery.xml files of the different projects ? How do you merge them ?
 
I think you would need to use a text editor to combine them into one XML.
 
You dont need to merge the scenery xml or model libraries, you can just add any package to your main project and they will be included with that package at export. For instance I keep all of my prop models in a separate scenery model package and just import it to my airport project to use the models, they then get packaged with the airport at export. See:

Adding Further Asset Groups And Packages​

If a package needs to have multiple asset groups - for example, a scenery package may also require ModelLibs or Materials - then this can be done by selecting the package in the Project Editor, and then clicking the Add Asset Group button at the bottom of the Inspector window:

-> https://docs.flightsimulator.com/html/Developer_Mode/Project_Editor/The_Project_Editor.htm

I would however recommend making a single scenery project with all of your scenery models inside the modellib, and building a clean asset library from that rather then merging a bunch of projects together, thats just ripe for issues.
 
You dont need to merge the scenery xml or model libraries, you can just add any package to your main project and they will be included with that package at export. For instance I keep all of my prop models in a separate scenery model package and just import it to my airport project to use the models, they then get packaged with the airport at export. See:

Adding Further Asset Groups And Packages​

If a package needs to have multiple asset groups - for example, a scenery package may also require ModelLibs or Materials - then this can be done by selecting the package in the Project Editor, and then clicking the Add Asset Group button at the bottom of the Inspector window:

-> https://docs.flightsimulator.com/html/Developer_Mode/Project_Editor/The_Project_Editor.htm

I would however recommend making a single scenery project with all of your scenery models inside the modellib, and building a clean asset library from that rather then merging a bunch of projects together, thats just ripe for issues.
Yes I manage to merge different models and textures in a single project as you explained. My concern is each scenery has objects (polygons, exclusion rectangle and hand placed models) and I cannot merge these sceneries inside a single project. Thus, it would imply to rebuild each scenery, one by one from the ModelLibs and textures which are successfully merged. So time consuming !
 
You can pretty much cut and paste elements in ta combined XML file. Attached is an example.
But I do wonder why the models and placements are so scattered into different projects if your intent was to have them all in one.
 

Attachments

Yes I manage to merge different models and textures in a single project as you explained. My concern is each scenery has objects (polygons, exclusion rectangle and hand placed models) and I cannot merge these sceneries inside a single project. Thus, it would imply to rebuild each scenery, one by one from the ModelLibs and textures which are successfully merged. So time consuming !
Dick is absolutely correct, that is the technique I use, there is also the SDK method.


This is overly tedious and bulky for my short attention span, but for some people it is exactly appropriate.
 
It works indeed with the SDK Method but packs are not accepted by the MSFS Marketplace at the moment.
I followed Dick's procedure and it worked out too : it can be a little more tedious with editing the xml file but the final project can be edited for the Marketplace now.

I thank you all for your help and sharing your knowledge.
 
Question, how can I combine an ADE type ground scenery with model libraries? Can I place the files following the ADE project structure?
 
There is a scenery in my sig with merged projects. You can write it into the project.XML, or you can just put everything in the proper directories and then use MSFS Layout Generator to spoof the build process and place it directly into the Community folder. I used MSFS Layout Generator, the SDK says how to merge them all.
 
There is a scenery in my sig with merged projects. You can write it into the project.XML, or you can just put everything in the proper directories and then use MSFS Layout Generator to spoof the build process and place it directly into the Community folder. I used MSFS Layout Generator, the SDK says how to merge them all.
Thanks Rick, will take a look.

I assume it is probably easier to make a model library, ADE taxiways, and placement projects as standalone projects, and then merge after everything is completed. I tried binging models as asset groups into the main scenery project, and although it works in the Dev Tool, the resulting build doesn't load the models.

Same thing if the models are loaded through ADE.....unless there is an existing model library with the loaded models in the community folder....they won't display.
 
Same thing if the models are loaded through ADE.....unless there is an existing model library with the loaded models in the community folder....they won't display.
Everything has to be imported into the Community folder. It is like the old Addon Scenery folder, but we can't just swap elements as before. If you do it all in a single airport project, or if you get all the elements into the Community folder first as individual projects, doesn't matter. You will want to bundle them for distribution but even that is optional.
 
Back
Top