FSUIPC Modules folder install location

[von]

Hello,
I upgraded my OS from WIN7 to Win10 because I got a message from Microsoft advising me the end was nearing for security Updates for Win7 from Microsoft.

I ended up resetting the Win10 install because I had problems with some aps and it uninstalled some of my apps.
Now some (not all) aps telling me my registry is not pointing to P3D properly.
So I messed up on my P3D uninstall/reinstalls along the way while learning a new OS.

I ended up reinstalling P3Dv4.5HF1 to F:P3Dv4 (previously on my 😄 drive ,  (was installed there twice).

Currently when I installed FSUIPC and I pointed its installer to my correct P3D install folder F:\P3Dv4.
I am rather sure I got a message from FSUIPC saying there was a problem with the normal P3D location and that FSUIPC could easily correct it and I accepted that.

When the FSUIPC install finished I noticed that FSUIPC Modules folder was installed here :
F:\Modules rather than inside F:\P3Dv4\Modules.

It is working ok but I thought it would install to my F:\P3Dv4 folder.

Note:
Later when I installed the VRS F18 it asked me where my P3D was installed ... I answered F:\P3Dv4 and it created a Modules folder inside my F:\P3Dv4 path for its data files.

So, just wonder how to get the FSUIPC data to normally install to F:\P3Dv4 also?

I copied my FSUIPC log here for a reference:

******
Installer for FSUIPC5.DLL version 5.151

Looking in registry for Prepar3D v4 install path:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4
     Parameter"AppPath"
... >>>  OK! FOUND Prepar3D v4!  <<< ...
     AppPath=C:\
===========================================================

INSTALLATION FOR Prepar3D v4:
AppPath="C:\"
Checking version of the Prepar3D v4 EXE:
This version was not found in this path!
User elected to Find the EXE for this version
Couldn't obtain Version Info! Asking user to find Prepar3D v4.EXE ...
User identified path:
   "F:\P3Dv4"
Checking version of the Prepar3D v4 EXE:
... Version 4.5.12.30293  (Need at least 4.1.0.0)
Checking if there's already a version of FSUIPC5 installed as:
       F:\Modules\FSUIPC5.DLL
... No previous valid version found.
Prepar3D v4 Modules folder created okay!
Okay -- installed FSUIPC5 into "F:\Modules\FSUIPC5.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Vaughan\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v4\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\Owner\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Vaughan\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Vaughan\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC5 section.
... FSUIPC5 section already exists but will be replaced.
... FSUIPC5 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
"Modules\FSUIPC Documents" folder created okay!
   Removed "FSUIPC4 Offsets Status.pdf" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC5 User Guide.pdf" okay
   Installed "FSUIPC5 for Advanced Users.pdf" okay
   Installed "The 2016 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 "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "FSUIPC5 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC5 History.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" 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 "Offset Mapping for PMDG 747QOTSII.pdf" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  FSUIPC REGISTER
Providing FSUIPC registration dialogue ...
Registration for FSUIPC5 was successful! (result code 00)

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

 

[John Dowson]

That does look strange.  I'll look into it and get back you.

John

[Pete Dowson]

4 minutes ago, John Dowson said:

That does look strange.  I'll look into it and get back you.

Yes, there's something odd with the way the Installer has formed up the Modules folder path after being told where to find the P3D EXE..

Really the problem here is that P3D is not correctly installed. There's no correct installation entries in the registry. It looks like either P3D has been moved, or Windows has been restored from a time before it was installed.

This will give many add-on programs problems problems. it would be far better for the user to re-install P3d properly.

Pete

 

[von]

7 hours ago, Pete Dowson said:

Yes, there's something odd with the way the Installer has formed up the Modules folder path after being told where to find the P3D EXE..

Really the problem here is that P3D is not correctly installed. There's no correct installation entries in the registry. It looks like either P3D has been moved, or Windows has been restored from a time before it was installed.

This will give many add-on programs problems problems. it would be far better for the user to re-install P3d properly.

Pete

 

Add-on products (aircraft/scenery) that have ask me to point to my p3d install folder have installed ok.

All add-ons and scenery that I have installed are working properly, including FSUIPC, except that FSUIPC installs to the F:\ instead of where I pointed FSUIPC to: F:\p3dv4.

 

 

 

 

[von]

I found this information on the internet when looking for information on P3D registry data.:
http://drzewiecki-design.net/forum/viewtopic.php?t=293

Prepar3Dv4:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Lockheed Martin\Prepar3D v4 - key name is "SetupPath"
I do not have this data entry.

HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4 - key name is "SetupPath"   
Mine is StupPath F:

HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4 - key name is "AppPath"  
Mine is AppPath F:\P3Dv4\...

Are these the registry entries that FSUIPC is looking for?
Are they in error on my setup?

 

[John Dowson]

Yes, as Pete said, there is something strange in your installation. However, as you selected the P3Dv4 directory when you installed FSUIPC5, this is the directory that should have been used, so there is also an issue in the FSUIPC5 installer that I will look into. As the original problem is your P3Dv4 installation, it would be better going forward for you first to correct that, then you can re-run the FSUIPC installer to install to the correct place.

I will be releasing a new version later this week (5.152), so I'll correct this installer problem before I release.

John

 

 

[von]

5 hours ago, John Dowson said:

Yes, as Pete said, there is something strange in your installation. However, as you selected the P3Dv4 directory when you installed FSUIPC5, this is the directory that should have been used, so there is also an issue in the FSUIPC5 installer that I will look into. As the original problem is your P3Dv4 installation, it would be better going forward for you first to correct that, then you can re-run the FSUIPC installer to install to the correct place.

I will be releasing a new version later this week (5.152), so I'll correct this installer problem before I release.

John

 

 

John,

Thanks for the follow up.

From the information I posted do you happen to know what the problem is with my P3D install and what I could do to correct it?

[John Dowson]

You could try editing your registry. Make sure you take a back-up first. Then:

17 hours ago, von said:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Lockheed Martin\Prepar3D v4 - key name is "SetupPath"
I do not have this data entry.

Ignore this.

17 hours ago, von said:

HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4 - key name is "SetupPath"   
Mine is StupPath F:

Presume 'StuPath' is an error? Anyway, change so that you have SetupPath set to 'F:\P3Dv4\'

18 hours ago, von said:

HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4 - key name is "AppPath"  
Mine is AppPath F:\P3Dv4\...

Thats ok.

You will also need to remove and re-install FSUIPC. To do this, remove the FSUIPC5 entry at HKEY_LOCAL_MACHINE\SOFTWARE\FSUIPC5, and manually delete the F:\Modules folder.

If you then re-run the FSUIPC5 installer, it should hopefully find your P3D installation and install in the correct place, as well as correcting your dll.xml file.

Alternatively, maybe uninstalling and then re-installing the P3Dv4 client may correct your registry for you, but I'm not sure on this.

Let me know if you have any issues.

John

 

[John Dowson]

Oh - you may want to make a copy of your key and ini files from your old Modules directory (if you have them), and drop them into the new one once FSUIPC5 is installed, or just rename your f:\Modules folder (rather than delete) so that you still have access to them, if needed.

[von]

18 minutes ago, John Dowson said:

You could try editing your registry. Make sure you take a back-up first. Then:

Ignore this.

Presume 'StuPath' is an error? Anyway, change so that you have SetupPath set to 'F:\P3Dv4\'

Thats ok.

You will also need to remove and re-install FSUIPC. To do this, remove the FSUIPC5 entry at HKEY_LOCAL_MACHINE\SOFTWARE\FSUIPC5, and manually delete the F:\Modules folder.

If you then re-run the FSUIPC5 installer, it should hopefully find your P3D installation and install in the correct place, as well as correcting your dll.xml file.

Alternatively, maybe uninstalling and then re-installing the P3Dv4 client may correct your registry for you, but I'm not sure on this.

Let me know if you have any issues.

John

 

John,

Thanks for the additional information on the registry.

Maybe someone with a proper registry for P3Dv4.5HF1 (where their FSUIPC install worked ok) could do a quick check and confirm the suspected bad entry and show what their entry is.

[John Dowson]

I have correct registry entries for P3Dv4.5HF1.....no point showing you my value though, as I have it installed in a different place....

[von]

2 minutes ago, John Dowson said:

I have correct registry entries for P3Dv4.5HF1.....

Ok,

When you mentioned " Presume 'StuPath' is an error? Anyway, change so that you have SetupPath set to 'F:\P3Dv4\' "

I wanted to verify prior to making any changes that that is what FSUIPC was looking for.

Thanks again for confirming. Much appreciated.

[Pete Dowson]

7 minutes ago, von said:

Maybe someone with a proper registry for P3Dv4.5HF1 (where their FSUIPC install worked ok) could do a quick check and confirm the suspected bad entry and show what their entry is.

Yes, john is correct. My P3D4 is on drive E: and the entry as exported directly using RegEdit is:

[HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4]
"SetupPath"="E:\\Prepar3D v4\\"

Your "StuPath" makes no sense really. Not sure how that can have been produced except by careless editing.

Pete

 

 

 

[von]

14 minutes ago, Pete Dowson said:

Yes, john is correct. My P3D4 is on drive E: and the entry as exported directly using RegEdit is:

[HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4]
"SetupPath"="E:\\Prepar3D v4\\"

Your "StuPath" makes no sense really. Not sure how that can have been produced except by careless editing.

Pete

 

 

 

Ok,

Thanks for confirming your P3Dv4 registry entry.

As for my wrong registry entry I have no idea how it got there ... I have not edited the registry.

 

I went back and seen I had made a typo error when posting in the forum.

I should have type SetupPath.

 

[John Dowson]

I assumed it was a typo! So the key is correct but the value wrong. Change it from 'F:' to 'F:\P3Dv4\'.

[von]

14 minutes ago, John Dowson said:

I assumed it was a typo! So the key is correct but the value wrong. Change it from 'F:' to 'F:\P3Dv4\'.

Ok,

Thanks again for the follow up.

I first have to find out how to back up the Win10 registry.

I will search the internet.

[John Dowson]

You can just use the 'Export' facility from regedit....

[von]

6 minutes ago, John Dowson said:

You can just use the 'Export' facility from regedit....

Ok,

Thanks for the follow up.

I will have a look at it this afternoon.

[von]

John,

I made notes from the forum posts then :

"You will also need to remove and re-install FSUIPC.
To do this, remove the FSUIPC5 entry at HKEY_LOCAL_MACHINE\SOFTWARE\FSUIPC5, and manually delete the F:\Modules folder."

** I backed up the entire current F:\P3Dv4\Modules folder (it has VRS TackPack data and my current fsuipc.ini files).
** Also, backed up my current fsuipc.ini file F:\modules folder (out of extra caution).
** Renamed current F:\ modules folder (in case I need it later).
** out of caution I also exported (as you mentioned) the reg key : HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4 and also exported the entire registry (a really large file).
** removed (deleted) the FSUIPC5 entry from the registry.
 

"If you then re-run the FSUIPC5 installer, it should hopefully find your P3D installation and install in the correct place, as well as correcting your dll.xml file."
Yes, FSUIPC v152 installer worked and installed ok as far as I can tell. I will use / test the new version setting  up buttons in the VRS FA18E later today.

The FSUIPC install log found my P3D folder :

"Looking in registry for Prepar3D v4 install path:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4
     Parameter"AppPath"
... >>>  OK! FOUND Prepar3D v4!  <<< ...
     AppPath=F:\P3Dv4\"

Note: the FSUIPC installer did not have to look for reg entry SetupPath.

 

And it updated my dll.xml as you said it would.

Pete and John Thank for you kelp.
Much appreciated.