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

Installing SODE for users

T

toprob

Messages
1,120
I'm putting together Real NZ Dunedin, which will incorporate SODE, and I just need to get it clear in my head how this would be installed. Really it's just updating SODE which is not clear to me, as anyone who has installed a previous version will need to update to the current version.

When I rerun the SODE installer, it gives me the option to uninstall -- will this uninstall a previous version?

For another third party installer I use, I have my installer check for the version number, and update if necessary, there's no uninstall necessary, so I need to come up with the best solution if SODE needs to be updated -- I am hoping to be able to:

Check if SODE is installed, if not just run the installer;
If so, check the version and if it needs updating, run the installer twice, first to remove the old version.

The idea it to have a reasonably hands-off install of my scenery, the libraries I use, SODE and Autogen Config Merger... you can imagine that it could get complicated for the user otherwise.

Any ideas appreciated!
 
I'm currently using SODE to animate windsocks in my sceneries. I have it bundled with my Object Library Pack, where I have written a batch file to recognize the previous version and update to the new version included with the object library update. Unfortunately, this method still isn't fully automated since the SODE installer must be re-run to uninstall the current version before updating. (Answering your question, yes, it will uninstall the version currently installed)

What would be nice is if the SODE installer could produce a separate uninstall.exe that could be launched from the batch file. This way, with the batch method, the user doesn't have to proceed to uninstall SODE. It can be fully automated. Just a thought.
 
From my experimentation today, the 1.4 installer won't uninstall 1.3.4, it just installs over the top. So what exactly are the pitfalls of not uninstalling?:)
 
The initial installers for the V1.3 series had some problems with dual FSX and FSX:SE installations that lead to incorrect SimObjectPath numbering within the fsx.cfg. Uninstalling would restore the numbering again, that's the reason I was promoting a proper uninstall before a new install.
V1.4 fixed that so in theory, you could install V1.4 just over any other SODE version. This is completely safe with the V1.4 series installers in the future.
So, the V1.4 installer does uninstall V1.3.4, just tested it (and it is supported this way since V1.3.1)
 
You must log in or register to reply here.
Back
Top