David Rogers Posted December 20, 2014 Share Posted December 20, 2014 One thing I've noticed regarding FSX:SE from 3 or 4 FS forums, is that not everyone is seeing the same results from trying to install the same existing addons into FSX:SE.I installed FSX:SE whilst still having the original FSX installed. My experience of then installing existing addons in to FSX:SE has been remarkably positive. Almost all (including all Orbx ones so far) installers are automatically finding and pointing to my FSX:SE location. Those that don't, usually let me manually change the file path to the FSX:SE location anyway. But I've seen other people attempting to install the same addons that I had no issues with, into the same virgin FSX:SE installation that I have, and seeing different results; eg. that the file path is still pointing to MS FSX. - Here's the crux of this post, in almost all of the cases where I've seen people have these problems where the installer still tries to find the MS FSX location, it's been users who have only FSX:SE installed. (In other words they uninstalled the box version first, or never had it installed in the first place. It seems that when you install FSX:SE, and already have original FSX installed, FSX:SE 'takes over' the registry key (thus most installers that look for FSX will now find the FSX:SE file path, not the MS FSX one). But it seems that people who just install FSX:SE (without having MS FSX installed) somehow get a different registry outcome, and a lot of installers still try to find the MS FSX file path. Just talking aloud here, in hte hope that these observations may be useful to Jon et al, in looking at options for the installation of Orbx products into FSX:SE. Although it seems counter-intuitive, I'm pretty sure that those that have both original FSX and FSX:SE installed, end up with a registry situation that means most addon installers are automatically finding the FSX:SE file path. Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.