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

FSX:SE FSX:SE Install location

Yeah... In my opinion, Steam installer should have warned the user about this situation, warning them that some add-ons won't be able to install properly on Steam edition and giving them a choice of aborting installation to remove CD version first, or continue and install in dual mode.

At least, I don't remember any such warning when I was installing Steam with CD version already there... :confused:
 
Hey Guys!

Sorry to bring this topic up again. From time to time Steam users are complaining that our installer cannot find the installation route. Usually this happens with Standalone steam users.

Currently the installer is looking for the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\DovetailGames\FSX folder . The most of the time even for standalon users it worked fine. Is there any other registry keys where the install location is written in both standalone and dualexistence as well because the HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 is also not present in all cases.
 
Hey Guys!

Sorry to bring this topic up again. From time to time Steam users are complaining that our installer cannot find the installation route. Usually this happens with Standalone steam users.

Currently the installer is looking for the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\DovetailGames\FSX folder . The most of the time even for standalon users it worked fine. Is there any other registry keys where the install location is written in both standalone and dualexistence as well because the HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 is also not present in all cases.
As I understand it, if FSX has previously been installed (and even if subsequently uninstalled) then Steam Edition will use SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0\

If FSX has not previously been installed then Steam Edition will use SOFTWARE\Microsoft\Microsoft Games\flight simulator\10.0\

This is obviously not an elegant use of the registry by the Steam Edition as unless you start rummaging around in the program directories you can never say for certain whether you are looking at the Steam Edition or the original FSX.

I get around it by providing two options for the user. "Steam Edition" and "Steam Edition dual install."
 
Back
Top