FSUIPC for developer version?

[Griphos]

I'm finally taking the plunge with P3D, I think.  I've always just flown FSX with a registered FSUIPC.  Twice in the past (v1 and v2) I've bought a month long developer version of P3D to test it out and both times decided not to get it.  This week I bought a month long developer license for v3.2.  I like the changes and plan to buy the full version.  But, I wanted to install a few things into the dev version to test it with the kinds of addons I usually fly (Orbx region, a few planes, etc).  I thought I'd also try to install FSUIPC to calibrate my controls and set them up the way I do in FSX.

I got the latest full version (.953) and installed it.  It found my FSX and either updated or didn't (I think it was already up to date).  Then it asked for the location of P3D since it didn't find it itself.  I pointed it to the P3D.exe and let it do its thing.  It suggested some problems with registry (which I later realized was because it was looking for v1).  I didn't allow it to make any changes, and it looked for v2 and didn't find it, and then finished.  It never looked for v3.  

Did I bugger things up?  I see the entry for FSUIPC in the dll.xml file for P3D.  Is it the case that FSUIPC doesn't look for or work with the monthly developer version of v3.2?  

Perhaps this is all moot, since I will soon be completely uninstalling this monthly license version before installing the full version, and will just try to install FSUIPC on that one (and not repeat the same mistake since I know it looks for v1 and v2 before looking for any newer version).  Just wanted to see if there's something I should do to make things right before doing that.  

[Pete Dowson]

57 minutes ago, Griphos said:

I got the latest full version (.953) and installed it.  It found my FSX and either updated or didn't (I think it was already up to date).  Then it asked for the location of P3D since it didn't find it itself.  I pointed it to the P3D.exe and let it do its thing.  It suggested some problems with registry (which I later realized was because it was looking for v1).  I didn't allow it to make any changes, and it looked for v2 and didn't find it, and then finished.  It never looked for v3.

I cannot tell what is going on without the Installer log -- one is always produced by the Installer, and contains all the details about what it found and didn't find in the Registry. Please find that and paste its contents complete here.

Pete

 

[Griphos]

Here you go.  Reading through this, it looks as if my pointing to my current P3D v3 install for v1 was written over fine when it found and installed for v3.  Seems like everything should be fine.  It just never reported to me that it installed for v3.  (It also looks like there are still registry entries for the earlier P3D installs I've since deleted).

-------------

Installer for FSUIPC4.DLL version 4.953

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:\MyGames\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 there, so looking in:
     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"
... 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"
... >>>  OK! FOUND Prepar3D v1!  <<< ...
     AppPath=D:\Prepar3D\

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"
... >>>  OK! FOUND Prepar3D v2!  <<< ...
     AppPath=D:\MyGames\P3Dv2\

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
... >>>  OK! FOUND Prepar3D v3!  <<< ...
     SetupPath=F:\Prepar3D v3\
===========================================================

INSTALLATION FOR FSX:
SetupPath="D:\MyGames\FSX\"
Checking version of the FSX EXE:
... Version 10.0.61637.0  (Need at least 10.0.60905.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       D:\MyGames\FSX\Modules\FSUIPC4.DLL
... Version 4.953 found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\MyGames\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Phil\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default.migrated\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\DefaultAppPool\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Phil\AppData\Roaming"
Found FSX.CFG in "C:\Users\Phil\AppData\Roaming\Microsoft\FSX\FSX.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\UpdatusUser\AppData\Roaming"
 ... No FSX.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

INSTALLATION FOR Prepar3D v1:
SetupPath="D:\Prepar3D\"
Checking version of the Prepar3D v1 EXE:
Couldn't obtain Version Info! Asking user to find Prepar3D.EXE ...
User identified path:
   "F:\Prepar3D v3"
Checking version of the Prepar3D v1 EXE:
... Version 3.2.3.16769  (Need at least 1.0.677.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       F:\Prepar3D v3\Modules\FSUIPC4.DLL
... Version 4.953 found.
Prepar3D v1 Modules folder already exists.
Okay -- installed FSUIPC4 into "F:\Prepar3D v3\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Phil\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default.migrated\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\DefaultAppPool\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Phil\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\UpdatusUser\AppData\Roaming"
 ... No Prepar3D.CFG there
Cannot edit the DLL.XML file to activate FSUIPC.
"Modules\FSUIPC Documents" folder already exists.
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
   Installed "SimConnectP3D3.dll" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

INSTALLATION FOR Prepar3D v2:
SetupPath="D:\MyGames\P3Dv2\"
Checking version of the Prepar3D v2 EXE:
Couldn't obtain Version Info! Asking user to find Prepar3D v2.EXE ...
User aborted attempt to find Prepar3D v2. Installation failed.
===========================================================

INSTALLATION FOR Prepar3D v3:
SetupPath="F:\Prepar3D v3\"
Checking version of the Prepar3D v3 EXE:
... Version 3.2.3.16769  (Need at least 1.0.677.0)
Checking compatibility with installed SimConnect:
Checking if there's already a version of FSUIPC4 installed in:
       F:\Prepar3D v3\Modules\FSUIPC4.DLL
... Version 4.953 found.
Prepar3D v3 Modules folder already exists.
Okay -- installed FSUIPC4 into "F:\Prepar3D v3\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Phil\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v3\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default.migrated\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\DefaultAppPool\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Phil\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Phil\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\UpdatusUser\AppData\Roaming"
 ... No Prepar3D.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
   Installed "SimConnectP3D3.dll" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  FSUIPC CHECK
Checking FSUIPC registration ...
Registration check for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************
 

[Pete Dowson]

7 hours ago, Griphos said:

it looks as if my pointing to my current P3D v3 install for v1 was written over fine when it found and installed for v3

Hmm. You should not really have done that. Just bypass it by exiting from the attempt to find V1. It will carry on to the next -- it has already built the list of versions it will be looking for in the first part, from the Registry. Only the second part involves actually going and finding them for real.

Quote

 It just never reported to me that it installed for v3.

Hmm. I see no way in the code for it to bypass that message. The v2 and v3 installation confirmations would have occurred rapidly immediately after the problem because of the v1 registry error.

I have FSX, P3Dv2 and P3Dv3 all installed here on my test PC. I deliberately added the entry you have into the Registry, for v1 and ran the Installer. I pointed it to P3Dv3 for v1 and it worked here as it did for you. If you then told to to go ahead and fix" the Registry, it might not have changed your

HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"

to point to Prepar3D 3, but possibly added this instead:

HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"

So, if you did that and have since deleted the former, you should go and delete the latter one too.

There was also the error that it couldn't install FSUIPC into the DLL.XML file as you did (" Cannot edit the DLL.XML file to activate FSUIPC." ), and once I'd got past all that it reported Installed okay for P3Dv2 and the for P3Dv3. They would have both been very quickly done after the error messages. I think you must have missed one or misread it.

I think I might add some extra sophistication to the Installer. When it can't find the desired folder, instead of going directly into getting the user to find the EXE, prompt saying something like

If this version is installed, press "Find" so you can point the Installer to the correct location.
If it is no longer installed, you can select "Fix" instead to remove the erroneous entry from the Registry.
Or to bypass all this entirely and ignore this version, select "Bypass".

with the three buttons Find, Fix and Bypass.

Pete

 

[Pete Dowson]

I've released FSUIPC 4.954e, inside an Installer which has the improved "bad Registry path" handling in the way I just described above.

It's available in the Download Links subforum, and it's now the official version from the Schiratti site.

Pete

 

[Griphos]

That seems a great improvement.  I'll download the new version.  Should I just install that one over the top, or do something else first to prepare for that?  Should I remove any registry keys?  I'm only very basically familiar with regedit.  I can find the keys, but don't really understand the entries.  

Since the first time it asked for P3D it didn't show a version number, that's why I tried to point it.  As I said, I'm new to FSUIPC for P3D with this install.  I'd removed v1 and v2 a long time ago (each within the month of install to test them out).  I used Control Panel uninstall, so I had thought there wouldn't be registry entries for them still.  I think the new message will help clarify the process greatly.  

Also, since I'll be deleting this version soon and installing the permanent version (on a different hard drive), is there something I should do so that FSUIPC installs correctly on the new install?

Thanks for your help.

[Pete Dowson]

1 hour ago, Griphos said:

Should I just install that one over the top, or do something else first to prepare for that?  Should I remove any registry keys?  I'm only very basically familiar with regedit.  I can find the keys, but don't really understand the entries.  

You never need to do any preparation when updating FSUIPC.

If your registry still needs fixing and the Installer tells you, just select "Fix".

Pete

 

[Griphos]

The new "e" installer worked great.  I let it fix the registry entries for v1 and v2 for me and it installed in v3 successfully.  

Thanks again for the help.

[Sanal]

Pete,

"I've released FSUIPC 4.954e, inside an Installer which has the improved "bad Registry path" handling in the way I just described above.

It's available in the Download Links subforum, and it's now the official version from the Schiratti site."

I want to download 4.954e, . I looked at  Schiratti site but it is not located there? Am I  looking at wrong page?

 

OK. I located  and downloaded working great.

Peter, thanks

 

[Pete Dowson]

3 hours ago, Sanal said:

I want to download 4.954e, . I looked at  Schiratti site but it is not located there? Am I  looking at wrong page?

OK. I located  and downloaded working great.

Where did you find 4.954e? It shouldn't be available anywhere since it was superseded by 4.955 on Monday, 4 days ago!

The Schiratti page in not mine. I cannot change the text there. But the links point direct to the same versions that I post here, in the Download Links subforum -- except the subforum may also host later, interim, updates of just the DLLs themselves.

Pete

 

[Griphos]

Hey Pete,

Sorry.  Didn't notice your post.  I got it from the forum here.  I don't recall how, exactly, since it was more than a week ago.  

I'm just about to get the full v3.3 version of P3D, so I'll download the latest from the forum here for installing with that.