Andy Blair Posted September 12, 2014 Report Share Posted September 12, 2014 Hi everyone, I'm beginning the long process of a complete rebuild of my P3D after a component failure in my PC. I had FSUIPC working fine in P3DV2.2 when I installed them both for the first time back in May this year but having downloaded both the latest versions of P3Dv2.3 and FSUIPC today, I can't seem to get past the point of the FSUIPC installer where it asks me to locate my FSX.exe file. I manually point it to the Prepar3D.EXE file that resides in my E:/Prepar3Dv2 folder but when I click on it and then try to 'OPEN' it, the installer just keeps asking me to locate FSX.exe. I was careful to run Prepar3D before I attempted to install FSUIPC. FSX and P3DV2.2 were both installed on my PC previously, however, to the best of my knowledge, they were uninstalled correctly i,e. the main installation directory and the 'AppData/Roaming' directories were all deleted after using the Windows uninstaller to uninstall P3Dv2.2 and then I ran CCleaner to clear out the registry too. Surely that was sufficient? In any case, I never had this problem when I tried to install FSUIPC into P3Dv2.2. Here is the text from the installer: Installer for FSUIPC4.DLL version 4.936 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... Looking in registry for ESP install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\ESP Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" ... >>> OK! FOUND Prepar3D! <<< ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... =========================================================== INSTALLATION FOR FSX: SetupPath="E:\Prepar3D v2\" Checking version of the FSX EXE: Couldn't obtain Version Info! Asking user to find FSX.EXE ... User identified path: "E:\Prepar3D v2" Checking version of the FSX EXE: Couldn't obtain Version Info! Asking user to find FSX.EXE ... When I then hit cancel, I get an error message saying "Cannot edit the Prepar3D DLL.XML file to activate FSUIPC. Please make sure you run Prepar3D at least once before installing FSUIPC!" As I say, I already ran Prepar3D several times before I tried to install FSUIPC. There is then another alert saying "FSUIPC4.DLL version 4.936: Installed into Prepar3D! etc, etc... BUT it may not because it is not included in the DLL.XML file. Please re-run this installer after running Prepar3D." I checked the DLL.XML file and it appears to have a line relating to FSUIPC4.dll in it: 4<?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> Also, when I run Prepar3D and look under my add-ons, FSUIPC appears to be running. Can anybody tell me what's going on? Has FSUIPC been installed properly? I would attach the FSUIPC4 Install.log file for you to look at but I am being told I am not permitted to attach such files... I have cut and paste the contents instead. Installer for FSUIPC4.DLL version 4.936 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... Looking in registry for ESP install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\ESP Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" ... >>> OK! FOUND Prepar3D! <<< ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... =========================================================== INSTALLATION FOR FSX: SetupPath="E:\Prepar3D v2\" Checking version of the FSX EXE: Couldn't obtain Version Info! Asking user to find FSX.EXE ... User identified path: "E:\Prepar3D v2" Checking version of the FSX EXE: Couldn't obtain Version Info! Asking user to find FSX.EXE ... User aborted attempt to find FSX. Installation failed. =========================================================== INSTALLATION FOR Prepar3D: SetupPath="E:\Prepar3D v2\" Checking version of the Prepar3D EXE: ... Version 2.3.11345.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 195 (ESP Orig) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: E:\Prepar3D v2\Modules\FSUIPC4.DLL ... Version 4.936 found. Prepar3D Modules folder already exists. Okay -- installed FSUIPC4 into "E:\Prepar3D v2\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Andy Blair\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\Andy Blair\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\Public\AppData\Roaming" ... No Prepar3D.CFG there Cannot edit the DLL.XML file to activate FSUIPC. =========================================================== INSTALLATION FOR Prepar3D v2: SetupPath="E:\Prepar3D v2\" Checking version of the Prepar3D v2 EXE: ... Version 2.3.11345.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 195 (ESP Orig) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: E:\Prepar3D v2\Modules\FSUIPC4.DLL ... Version 4.936 found. Prepar3D v2 Modules folder already exists. Okay -- installed FSUIPC4 into "E:\Prepar3D v2\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Andy Blair\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Andy Blair\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Andy Blair\AppData\Roaming\Lockheed Martin\Prepar3D v2\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\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\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 "SimConnectP3D2.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 "FSUIPC4 Offsets Status.pdf" okay =========================================================== All installer tasks completed. *************** End of Install Log *************** Thanks in advance for any assistance. Andy Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 12, 2014 Report Share Posted September 12, 2014 I'm beginning the long process of a complete rebuild of my P3D after a component failure in my PC. I had FSUIPC working fine in P3DV2.2 when I installed them both for the first time back in May this year but having downloaded both the latest versions of P3Dv2.3 and FSUIPC today, I can't seem to get past the point of the FSUIPC installer where it asks me to locate my FSX.exe file. I manually point it to the Prepar3D.EXE file that resides in my E:/Prepar3Dv2 folder but when I click on it and then try to 'OPEN' it, the installer just keeps asking me to locate FSX.exe. I was careful to run Prepar3D before I attempted to install FSUIPC. You simply need to abort the FSX part of the installation -- i.e. press "Cancel". It is asking you to find FSX.EXE because your Registry still says it is installed. You cannot install for P3D in the FSX part of the installer's sequence! This shows that your FSX has not been properly uninstalled, or maybe that something else has re-added the FSX install data: Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... The path given by the Registry is the same as your P3Dv2! INSTALLATION FOR FSX: SetupPath="E:\Prepar3D v2\" which seems very strange. Maybe you've used some fiddle to get FSX programs installed into P3D? When I then hit cancel, I get an error message saying "Cannot edit the Prepar3D DLL.XML file to activate FSUIPC. Please make sure you run Prepar3D at least once before installing FSUIPC!" As I say, I already ran Prepar3D several times before I tried to install FSUIPC. There is then another alert saying "FSUIPC4.DLL version 4.936: Installed into Prepar3D! etc, etc... BUT it may not because it is not included in the DLL.XML file. Please re-run this installer after running Prepar3D." Actually, before both of those you would have seen this: Your FSX installation has not been found, even with your help. No changes have been made for this by this program The "cannot edit" and the DLL.XML alert messages are both for Prepar3D, not for Prepar3D version 2! Again, your Registry says you have FSX, Prepar3D (version 1) and Prepar3D version 2, all installed. Therefore the installer tries to install FSUIPC for all three of them. Look: Looking in registry for Prepar3D install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" ... >>> OK! FOUND Prepar3D! <<< ... and INSTALLATION FOR Prepar3D: SetupPath="E:\Prepar3D v2\" again, the same P3Dv2 path!!! But that registry entry is ONLY used for version 1 of P3D!!!! I don't know how you got the Registry into this mess, but it hasn't really done any harm except confuse you. Even then, if you actually read EXACTLY what the messages were saying you'd see that the only one you care about, P3D v2, was completed successfully -- something which is clearly shown in the log. You would have certainly got a message which you had to acknowledge that such installation was successful. Do you not believe it? Please, next time do take note of what is actually stated in the messages you see. The way Lockheed Martin have constructed things, "Prepar3D" paths refer to version 1. All the Registry and User Data and Flights folders have the v2 added. I think they did this so you could have v1 and v2 both installed and operational with different data files. Your having all three sims apparently installed (and in the same folder!) is strange and will continue to confuse you if you are not careful. Pete Link to comment Share on other sites More sharing options...
Andy Blair Posted September 12, 2014 Author Report Share Posted September 12, 2014 Hello Peter. First of all, thank you sincerely for responding to my request for support - I am glad that FSUIPC has been installed correctly for Prepar3Dv2 and appreciate your reassurance that all is well in that respect. I can't argue with anything you've said, only I would like to add in my defence that this, my latest install of Prepar3Dv2 and FSUIPC, was carried out on a brand new SSD and after the un-install procedure I outlined earlier - including the use of C-Cleaner, which I trusted to clear the registry of any lingering traces of FSX and my previous install of Prepar3Dv2. Regardless of this, the presence of old FSX files does not come as much of a surprise to me as does the presence of Prepar3D (version 1) files. I swear I have never owned or installed a version of this - I went straight from FSX to Prepar3Dv2.2 - so I really have no idea how this has come about. I did use a well known "fiddle" migration tool to install FSX add-ons into Prepar3Dv2.2 back in May, so perhaps this is the culprit. I seem to recall the way it worked was to create a 'virtual' FSX installation and point add-on installers to it - I'm sure you know more about how these things work than I do. Not sure even that would explain the presence of Prepar3D (version 1) though. I do recall back in May trying to install a piece of Orbx scenery I was unaware had yet to be made Prepar3Dv2 compatible (it was only FSX and Prepar3D version 1 compatible at that time). Not sure if this would have added any files. Having previously installed FSUIPC for FSX and then for Prepar3Dv2.2 - both times without any issues - I know how easy and straightforward it is to install when things go smoothly. That is why, when faced with such a sequence of error messages and warnings, it was not immediately obvious to me that the installation had been successful. I would not ignore error messages during the install of any other piece of software so I thought it reasonable to ask you for support. I acknowledge that the issue is not with FSUIPC but with my lack of understanding of what the error messages meant and my confusion as to why I was seeing them in the first place. Unfortunately, some of us are still trying to learn. Regards, Andy Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 12, 2014 Report Share Posted September 12, 2014 I can't argue with anything you've said, only I would like to add in my defence that this, my latest install of Prepar3Dv2 and FSUIPC, was carried out on a brand new SSD and after the un-install procedure I outlined earlier - including the use of C-Cleaner, which I trusted to clear the registry of any lingering traces of FSX and my previous install of Prepar3Dv2. Regardless of this, the presence of old FSX files does not come as much of a surprise to me as does the presence of Prepar3D (version 1) files. I swear I have never owned or installed a version of this - I went straight from FSX to Prepar3Dv2.2 - so I really have no idea how this has come about. I did use a well known "fiddle" migration tool to install FSX add-ons into Prepar3Dv2.2 back in May, so perhaps this is the culprit. I seem to recall the way it worked was to create a 'virtual' FSX installation and point add-on installers to it - I'm sure you know more about how these things work than I do. Not sure even that would explain the presence of Prepar3D (version 1) though. I do recall back in May trying to install a piece of Orbx scenery I was unaware had yet to be made Prepar3Dv2 compatible (it was only FSX and Prepar3D version 1 compatible at that time). Not sure if this would have added any files. Having previously installed FSUIPC for FSX and then for Prepar3Dv2.2 - both times without any issues - I know how easy and straightforward it is to install when things go smoothly. That is why, when faced with such a sequence of error messages and warnings, it was not immediately obvious to me that the installation had been successful. I would not ignore error messages during the install of any other piece of software so I thought it reasonable to ask you for support. I acknowledge that the issue is not with FSUIPC but with my lack of understanding of what the error messages meant and my confusion as to why I was seeing them in the first place. Unfortunately, some of us are still trying to learn. Yes, all understood. Considering all three Registry entries pointed directly at your P3Dv2 installation, I would agree that the unwanted two were placed there by the migration tool you used. Evidently, whoever wrote it, thought best that to install FSX and P3Dv1 add-ons into P3Dv2 they would be fooled by these entries. Unfortunate that it also fools FSUIPC's installer, which is well aware of all three programs, into wanting to install into all three. However, the outcome is not fatal, it is just confusing. Regards Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now