Gaffiero Posted January 27, 2015 Report Share Posted January 27, 2015 Hi, I have both FSX:SE and P3D v2.4, when I install FSUIPC it installs correctly for FSX but I am getting an error when it tries to install on P3D. Here is the part of the install log concerning P3D INSTALLATION FOR Prepar3D v2: SetupPath="D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\" Checking version of the Prepar3D v2 EXE: ... Version 2.4.11570.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Checking if there's already a version of FSUIPC4 installed in: D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL ... Version 4.938f found. Prepar3D v2 Modules folder already exists. Okay -- installed FSUIPC4 into "D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\James\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\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\James\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\James\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\MSSQL$SQLEXPRESS\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\MSSQL$SQLEXPRESS1\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\MSSQL$SQLEXPRESS2014\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there "Modules\FSUIPC Documents" folder created okay! 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 Installed "Profiles in Separate Files.pdf" okay =========================================================== All installer tasks completed. *************** End of Install Log *************** Thanks for the help!!!! P.s. Simmconnect is installed because I have REX installed and before I had installed Simmconnect REX would not inject weather and after installing it weather injection was fine. Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 28, 2015 Report Share Posted January 28, 2015 I have both FSX:SE and P3D v2.4, when I install FSUIPC it installs correctly for FSX but I am getting an error when it tries to install on P3D. Here is the part of the install log concerning P3D What error do you think you are getting? The log shows it all went perfectly! Pete Link to comment Share on other sites More sharing options...
Gaffiero Posted January 28, 2015 Author Report Share Posted January 28, 2015 I do not rember the exact wording as I am currently at work but the error said something that it could not edit the DLL.XML file of Prepar3d. If this is not enough information I will post a screenshot later today. Thanks Link to comment Share on other sites More sharing options...
Gaffiero Posted January 28, 2015 Author Report Share Posted January 28, 2015 I don't know if I am reading the log file correctly but it seems to me that it isn't finding the Prepar3d.cfg file. Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 28, 2015 Report Share Posted January 28, 2015 I don't know if I am reading the log file correctly but it seems to me that it isn't finding the Prepar3d.cfg file. 1. Why are you looking in the Log in the first place? What is prompting you to do so? What is not working? 2. It actually states very clearly that is DOES find the CFG file, here: Looking in "C:\Users\James\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\James\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.CFG" So, I repeat, WHAT is the problem? Why aren't you going flying instead? Pete Link to comment Share on other sites More sharing options...
Gaffiero Posted January 28, 2015 Author Report Share Posted January 28, 2015 Because during the install process I get an error which as I said before says that dll.xml could not be changed. Also when I run P3d it crashes every time untill I delete all files in the module folder of P3d. I will post a screen shot of the error soon. Thanks Link to comment Share on other sites More sharing options...
Gaffiero Posted January 28, 2015 Author Report Share Posted January 28, 2015 Ok here is the error I am getting during the install. An yes I did run P3D before installing FSUIPC Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 28, 2015 Report Share Posted January 28, 2015 Because during the install process I get an error which as I said before says that dll.xml could not be changed. This must be in a part of the Log you didn't bother showing, then, because obviously all is well with P3D install in the part you showed: 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 If you only show me part of things, how do you expect me to help? Also when I run P3d it crashes every time untill I delete all files in the module folder of P3d. I will post a screen shot of the error soon. Well that is certainly not an installation error! Do NOT post screenshots please! Just tell me what the error says, and show me the FSUIPC4.LOG file from after the crash. It could be one of a number of things, but I can't tell without information. Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 28, 2015 Report Share Posted January 28, 2015 Ok here is the error I am getting during the install. The reason for this will be in the part of the Install log you didn't bother to show me! Next time you paste files in, please paste the whole file!!!! The message probably relates to an install attempt for another installation altogether. Maybe your Registry also has pointers to P3Dv1. I seen that happen before, especially with folks who updated to v2 but never actually managed to completely uninstall v1 and then used the same folder for V2. Pete Link to comment Share on other sites More sharing options...
Gaffiero Posted January 28, 2015 Author Report Share Posted January 28, 2015 I just tried to post only the relevent parts and not post the whole log file, Surly I did not do it intentionally if I expected help!!!!! Well I posted the screen shot before I read you message, so here is what is says "Problem! Cannot edit Prepar3D DLL.XML file to activate FSUIPC. Please make sure you run Prepared3d at least once before you install FSUIPC". And yes I did run it more than once. Here is the log Installer for FSUIPC4.DLL version 4.938f Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=E:\Program Files (x86)\Steam\steamapps\common\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" ... NOT found! ... Looking in registry for Prepar3D 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! <<< ... AppPath=D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... SetupPath=D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ =========================================================== INSTALLATION FOR FSX: SetupPath="E:\Program Files (x86)\Steam\steamapps\common\FSX" Checking version of the FSX EXE: ... Version 10.0.62608.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 62608 (Steam) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: E:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL ... Version 4.938f found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "E:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\James\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\James\AppData\Roaming" Found FSX.CFG in "C:\Users\James\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\MSSQL$SQLEXPRESS\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\MSSQL$SQLEXPRESS1\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\MSSQL$SQLEXPRESS2014\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\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 "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay =========================================================== INSTALLATION FOR Prepar3D: SetupPath="D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\" Checking version of the Prepar3D EXE: ... Version 2.4.11570.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL ... No previous valid version found. Prepar3D Modules folder already exists. Okay -- installed FSUIPC4 into "D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\James\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\James\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\MSSQL$SQLEXPRESS\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\MSSQL$SQLEXPRESS1\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\MSSQL$SQLEXPRESS2014\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="D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\" Checking version of the Prepar3D v2 EXE: ... Version 2.4.11570.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Checking if there's already a version of FSUIPC4 installed in: D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL ... Version 4.938f found. Prepar3D v2 Modules folder already exists. Okay -- installed FSUIPC4 into "D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\James\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\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\James\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\James\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\MSSQL$SQLEXPRESS\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\MSSQL$SQLEXPRESS1\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\MSSQL$SQLEXPRESS2014\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there "Modules\FSUIPC Documents" folder created okay! 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 Installed "Profiles in Separate Files.pdf" okay =========================================================== All installer tasks completed. *************** End of Install Log *************** Link to comment Share on other sites More sharing options...
Gaffiero Posted January 28, 2015 Author Report Share Posted January 28, 2015 Oh and I never had prepare3d V1. I only ever bought v2.4 Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 28, 2015 Report Share Posted January 28, 2015 Well I posted the screen shot before I read you message, so here is what is says "Problem! Cannot edit Prepar3D DLL.XML file to activate FSUIPC. Please make sure you run Prepared3d at least once before you install FSUIPC". Okay, that's better. And the error you get reported is clearly in there, if you had but searched: Cannot edit the DLL.XML file to activate FSUIPC. And the reason for this is also very clear. There's a section for FSX, which was okay, a section for Prepar3D (v1), which is where the error occurs, and finally one for Prepar3D v2. The error occurs because there will be no DLL.XML path for P3D v1. You have a registry mixup with an installation entry for V1 pointing to your V2 as well as a separate entry for V2. Look: Looking in registry for Prepar3D 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! <<< ... AppPath=D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ just after this you can see the proper V2 path being found: Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... SetupPath=D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ The result of this mess is that the Installer tries to install for P3D v1 and P3D v2, both in the same folders. This does not harm (copying the files in twice doesn't hurt), but you'll get the DLL.XML update error because the path to the V1 CFG files no longer exists. So, it does not harm. If you want to tidy it up (as it should have been tidied by the V1 uninstaller) then you'd need to delete the Registry section called HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 28, 2015 Report Share Posted January 28, 2015 Oh and I never had prepare3d V1. I only ever bought v2.4 Nevertheless, the entry is there. Maybe you used some migration tool or other addon which made that false entry. Pete Link to comment Share on other sites More sharing options...
Gaffiero Posted January 28, 2015 Author Report Share Posted January 28, 2015 ok will give it a try, Thanks Link to comment Share on other sites More sharing options...
Gaffiero Posted January 28, 2015 Author Report Share Posted January 28, 2015 I must have been an add-on which installed it, I never installed it knowingly. Well either way that seems to have been the problem. Thanks 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