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

The idea

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,450
Country
netherlands
The idea behind the Autogen Configuration Merger tool is to make it easier to modify the autogen configuration files. FSX and P3D use one set of global configuration files for this, which means that all developers must modify the same files.

This often leads to problems when people replace the existing configuration files when a new addon is installed or when the merging is not done correctly. Attempts to ease this situation by released combined configuration file containing the definitions for different addons might sound helpfull, but that makes updating specific configurations of an addon later on much harder.

Therefore this tool aims to assist in the process of merging the files. Each addon can just put it's custom autogen configuration files locally with the addon (those configuration files only need to contain the definitions of the scenery, no need to include the default ones or those of other addons). Then before starting FS the Autogen Configuration Merger tool will scan over all active addon sceneries and make sure those local configurations are merged into the global ones.

By checking this when FS starts and not only at install time of the scenery, it can also be ensured that your addon keeps working, even after somebody else messed up the global files. Your custom definitions are just added back in.
 
Back
Top