gvmd

I did read your suggestions and thanks for your help. I did go to regedit and looked for HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\\ but did not find it. I then looked in HKEY_LOCAL_CURRRENT_USER\SOFTWARE\Lockheed Martin and found the V2 and V3 in this location and deleted V3. I then started Prepair3d and it crashed. So I went back into the Regedit and Looked back a HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\ the Lockheed Martin folder was not here. So I looked in folder Wow6432Node and found the Lockheed Martin folder and I removed V3 as well. Still P3d would not load. I went back and regedit and remove all the Lockheed Martin folders and reloaded the P3d. I was then able to reload FSUIPC with no problems. A big thanks for pointing me in the right direction.

Do you have any ideas on how to fix this issue?

Hi Pete I originally loaded V3 but found out V3 was not compatible with VRS superbug. I uninstalled it and installed V2. Everything ran fine and had no issues until I wanted to load widefs and that’s when the troubles started.

Hi Pete, thanks for the quick response. Below is my install log. Installer for FSUIPC4.DLL version 4.955c Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"AppPath" ... >>> OK! FOUND FSX! <<< ... AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ 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" ... NOT found! ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... SetupPath=C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ Looking in registry for Prepar3D v3 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v3! <<< ... SetupPath=C:\Program Files (x86)\Lockheed Martin\Prepar3D v2 ************ BUT this is the same path as for Prepar3D v2! Will only install for Prepar3D v3 ************ =========================================================== INSTALLATION FOR FSX: SetupPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\" 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: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL ... Version 4.955c found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\rick office\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\girls\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Guest\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\PCPitstopSVC\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\rick office\AppData\Roaming" Found FSX.CFG in "C:\Users\rick office\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 ... ... There is a SimConnect.XML, checking for "local" section. ... "local" section already exists, file not modified. Looking in "C:\Users\rick%20office\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 v3: SetupPath="C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\" Checking version of the Prepar3D v3 EXE: ... Version 2.5.12946.0 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Checking if there's already a version of FSUIPC4 installed in: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL ... Version 4.955c found. Prepar3D v3 Modules folder already exists. Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\rick office\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\girls\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Guest\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\PCPitstopSVC\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\rick office\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\rick%20office\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 "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 "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 'not now' selected *************** End of Install Log *************** What do you mean by "any more"? Are you saying you had installed it and had it working before? You just said this was all fresh "yesterday"? Of course, if FSUIPC is not being loaded then it cannot add itself to the menu system. Find the Install log and paste its contents into a message here. I'm out all day but I'll get to it when I return later this evening. I have built a F18 replica cockpit and have used FSUIPC to control all the devices on my Sim. After reloading Prepare 3d I started and stopped the program. I then reloaded FSUIPC i did get the message as stated above. I hit OK and then it asked me if i would like to load FSUIPC and i selected both FSUIPC and WideFS. in put in the pass codes and the program finished. I then started Prepare3d and looked for FSUIPC on the ADD-ON drop down tab the FSUIPC tab that is there is missing. Yes I agree that FSUIPC did not load properly. Best Rick

I have prepare 3d v2 academic which was running well. I yesterday I purchased WIDEFS7 and loaded FSUIPC4 V 4.955C. I received an error “problem! Cannot edit the Prepar3d V3 DLL.xml file to activate FSUIPC”. After the attempted to load FSUIPC I tried to run Prepare 3d and it would crash. I uninstalled and reinstalled Prepare 3d and reinstalled FSUIPC V4.955C and am still getting the same message. I am able to run PrePare3d now but FSUIPC is not on the dropdown menu anymore. I am running windows 7 VRS superbug. Rick

Hi Pete, I discovered I had multiple entries in the file for the switches I had problems with. I went thru them all and removed double entries and I am back to normal. Thanks! Rick

I have issue with trying to reassign some of my switches that were previously assign FSUIPC. When I go to reassign some previously assign switch In FSUIPC in the Button & Switches tab. The Clear button, Select FX box and Control Sent when Button Pressed is grayed out. I am unable to make any changes to this switch assignment. I am not sure how to correct this issue.