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

Current status

arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,422
Country
netherlands
Autogen Configuration Merger is a tool that is currently still in development. I almost have a beta version ready that can be tried by other developers. But until it has been tested by enough developers, I don't feel the tool is stable enough to be included with actual scenery addons that are released to users.
 
Hi Arno:

I'm looking forward to testing this, and plan to offer input on the "survey" on this new utility in its new sub-forum, but before doing so, I'd like to better understand what format and location ones custom "Autogen Descriptions" need to be in in order for them to be detected and processed by your forthcoming "Autogen Configuration Merger". :scratchch

Could you tell us a bit more about the initial proposed format and location ones custom "Autogen Descriptions" need to be in so that they can be detected and processed by "Autogen Configuration Merger" ...and we can better reply to the survey ?

Many thanks again ! :)

GaryGB
 
Last edited:
Hi Gary,

Good point. The idea is that the developer just adds a folder called Autogen to his scenery (so besides the scenery and texture folder). In that folder he can put the same configuration files as the global ones (so SPB or XML for AutogenDescriptions, RoofDescriptions, Materials, etc and a default.xml for the library objects). But those configuration files at the scenery only need to contain the new custom definitions that should be added. But the formats are exactly the same.
 
So how will the engine recognise and use this as autogen? Sounds great btw!
 
The tool will merge them into the global configurations when it is run. So FS still only uses the global configuration, but this way it's less likely there are conflicts between addons.
 
I see. So customers will have to have this program with the scenery and run it themselves... What's the license going to be?
 
Yes, the end user needs to have the tool installed as well. I image that it is installed by the installer of the addon and then runs automatically when FS starts. So as little action from the user as possible.

The license will be free, like all of my tools. It can be used for commercial and freeware addons.
 
You must log in or register to reply here.
Back
Top