FSUIPC Ver. 4.945 Not Installing FSX-SE

[George_M]

Hi Pete:

 

I've downloaded and installed the latest version of FSUIPC.  I presently have a parallel installation of both FSX and FSX-SE.  The installer found the legacy version just fine but the installation log shows that it did not find the FSX-SE installation.  The previous version of FSUIPC I had installed (Ver. 4.939e) found both versions and installed fine.  Here is the log from the 4.945 install:

 

Installer for FSUIPC4.DLL version 4.945


Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=D:\FSX\

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"AppPath"
... NOT found! ...
===========================================================

 

For reference, here is the log from the 4.939e install (showing the path where it found the FSX-SE installation:

 

Installer for FSUIPC4.DLL version 4.939e


Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=D:\FSX\

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"AppPath"
... >>>  OK! FOUND FSX-SE!  <<< ...
     AppPath=D:\FSX_Steam\steamapps\common\FSX\

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

===========================================================

 

As you can see, the paths are completely different between 4.945 and 4.939e.  I checked my registry and there are no entries for either <HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX> or      <HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX>.  The install path on my system is the same as it was when I installed 4.939e - <HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0>.  I am presently running FSX-SE version 62615.

 

Thanks.

 

George S. Marinakis

 

[Pete Dowson]

As you can see, the paths are completely different between 4.945 and 4.939e.  I checked my registry and there are no entries for either <HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX> or      <HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX>.  The install path on my system is the same as it was when I installed 4.939e - <HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0>.  I am presently running FSX-SE version 62615.

 

Hmm. That's very strange. I specifically changed it to look for DoveTailGames because many folks were finding problems with the original method. Mind you, i did change it a long time ago -- version 4.939e was back in FSX-SE 62611 days, in February/March 2015. There have been many versions of FSUIPC4 since then as well an other versions of FSX-SE. How come you missed all those? Have been away for a few months?

 

I am a little bemused on two counts:

 

1. Why, when the change to look for the DoveTailGames install details has been around for at least two FSX-SE releases (62613 and 62615) and many FSUIPC updates, has no one mentioned this problem before, and

 

2. Why hasn't your specific registry got this entry when the FSX-SE install creates it? Have you rolled back at some stage?

 

I'll look to see what i can do to overcome these bewildering differences, but meanwhile, obviously, you can deal with your specific problem by simply copying the updated files from your FSX Modules folder to your FSX-SE Modules folder.

 

Pete

[George_M]

 

Hmm. That's very strange. I specifically changed it to look for DoveTailGames because many folks were finding problems with the original method. Mind you, i did change it a long time ago -- version 4.939e was back in FSX-SE 62611 days, in February/March 2015. There have been many versions of FSUIPC4 since then as well an other versions of FSX-SE. How come you missed all those? Have been away for a few months?

 

I am a little bemused on two counts:

 

1. Why, when the change to look for the DoveTailGames install details has been around for at least two FSX-SE releases (62613 and 62615) and many FSUIPC updates, has no one mentioned this problem before, and

 

2. Why hasn't your specific registry got this entry when the FSX-SE install creates it? Have you rolled back at some stage?

 

I'll look to see what i can do to overcome these bewildering differences, but meanwhile, obviously, you can deal with your specific problem by simply copying the updated files from your FSX Modules folder to your FSX-SE Modules folder.

 

Pete

 

I just installed FSX-SE in mid-August which would have been build 62613 (I believe).  It looks like I didn't update FSUIPC at that time.  I'm usually more diligent about those sorts of things but it appears I just used the last version I had which would have been 4.939e.  I only get my FSUIPC updates directly from you and I can see that I downloaded 4.939e on or about March 9, 2015 (that's the timestamp for the folder I created when it was downloaded).  I did take a break from flight simming for most of June and July but I can't imagine I missed that many updates.  Looks like I may have.

 

Either way, when I acquired and installed FSX-SE, that's the install path it created.  It has since auto-updated to 62615.  As I said, I've only had it about a month.

 

What I find interesting is that you say that the install details for DoveTailGames has been around since 62613.  I'm fairly certain that when I purchased FSX-SE that (62613) was the current version at the time.  So the question is why did my version use the older installation path?  Weird.  I have not rolled back my computer or FSX-SE in any way.

 

I have already copied the latest version of FSUIPC into my FSX-SE Modules folder and that's an easy enough fix for future updates.  I agree with you that it is odd that this is the first you have heard of such an issue.  Maybe it is unique to my install?

 

Thanks for looking into it and the quick response.

[Pete Dowson]

What I find interesting is that you say that the install details for DoveTailGames has been around since 62613.  I'm fairly certain that when I purchased FSX-SE that (62613) was the current version at the time.  So the question is why did my version use the older installation path?  Weird.  I have not rolled back my computer or FSX-SE in any way.

 

FSX-SE build 62613 was not supported by FSUIPC 4.939e. The first FSUIPC version supporting 62613 was 4.939j, released on 1st April.

 

Anyway, I'll do some checks here and maybe change the installer to try and deal with all the alternatives. it's quite a complex puzzle with so many different possibilities which have been reported. And things are different again if someone has attempted to uninstall FSX-MS before installing FSX-SE. It doesn't clear out all the references.

 

BTW, I have both Registry paths for FSX-SE installation on my PC -- the DoveTailGames one and the Microsoft one. The DoveTailGames one was created by one of the DoveTail updates (don't actually know which). Maybe you missed one and they stopped doing it.

 

Pete