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

Installer integration

arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,427
Country
netherlands
Since I'm not so familiar with installers for scenery, let me start a topic about how the integrate Autogen Configuration Merger with installers. I'll outline my current approach here, any suggestions are more than welcome.

The idea is that the installer executes the ACM installer to make sure it's installed. As an argument you need to pass which version of FS you are installing to.

Next after your installer has added the scenery to the scenery.cfg file, you can call ACM from the installer to make sure the initial merge is done.

Or now that I'm typing this, maybe I should reverse this and let the ACM install automatically do the initial merge.
 
The closest thing I do in my installers is that they will check that the required scenery object library is installed and up to date, and this is done by checking the registry which has the current library version. Because my installer checks this, it will only run the library installer if required, which simplifies things a bit.

My installers check for installed sims, and let you choose, and the Library installer is no different, so this results in the user having to make the choice twice for one install, which is kind of weird but workable. Parsing the result from the initial choose would be better, but not better enough to make me rewrite the installer...

I normally try for less steps, which for me means less to go wrong:) but I don't have your coding skills or young brain...
 
Thanks for the inside. It seems calling one "installer" for ACM from a scenery installer would be best.

Do you allow installing to FSX and P3D at once in your installer or would the user have to run it twice in that case?
 
Thanks, I guess most developers will do it like that. In that case my installer also doesn't have to support installing to multiple versions at once.
 
You must log in or register to reply here.
Back
Top