von

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.

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.

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, 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?

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?

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.

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 ***************

FSUIPC 5.121a (P3Dv4) ok here.

Same here .. I continued the post in the P3D forum: http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=126680

Also noticed my P3Dv4 startup screen changed (FSUIPC v512) to this (screenshot) until I mouse right click the aircraft then the display returns to a normal windowed display: Changing back to FSUIPC dll 5.113 fixed it. https://imgur.com/a/TzZD3 Note: I have Win7-64 with KB4038788 installed Edit: Just for info .. I also use Ezdok which uses the middle mouse button (depressed) to pan the VC .. it is working ok.

" Did you update FSUIPC to 5.103, the version for the HOTFIX? " Yes, and same errors using the default P3D jet.

Just for info: Lorby-SI AddonOrganizer The ZIP title is v99 but the exe's file version is still v95. All working ok in P3Dv3 and v4 as far as I can tell inspecting the output cfg file.

Just for info: FSUIPC 4.959m ok (P3Dv3.4 HF2, FSX Accel. / Win7-64) here (as was 4.959 prior).

It was just example to show top portion. With every software install or update I check the exe and dll xml. I move FSUIPC back to the top protion above my addon aircraft e.g.,.. for years now FSX and P3D. Years ago I had a problem with it at or near the bottom ... never (so far) have I had any problems with it higher up. Here are mine files for FSX and P3D today ***************************************** FSX *** <?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>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>F:\FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll</Path> </Launch.Addon> <Launch.Addon> <Name>AFXModule</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>F:\AFX-v108\AFXModuleFSX.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Object Placement Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>VRS_TacPack</Name> <Disabled>False</Disabled> <ManualLoad>True</ManualLoad> <Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Flight Recorder</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Flight1SoundStream</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Flight One Software\Flight1 SoundStream\Flight1SoundStreamFSX.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG HUD interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>VistaMare Core</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>VistaMare\ViMaCoreX.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Level-D Simulations</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\LVLD.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Fly the Maddog</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>F:\FSX\Modules\LeonardoSH.dll</Path> </Launch.Addon> <Launch.Addon> <Name>CMeteoXml</Name> <Disabled>False</Disabled> <Path>.\CMeteoXml.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Carenavigraph</Name> <Disabled>False</Disabled> <Path>.\Carenavigraph.dll</Path> </Launch.Addon> <Launch.Addon> <Name>XMLTools</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>XMLTools.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>as_connect</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp.dll</Path> </Launch.Addon> </SimBase.Document> P3D: **** <?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>Traffic Toolbox</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3 SDK 3.4.18.19475\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG HUD interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_P3D</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Carenavigraph</Name> <Disabled>False</Disabled> <Path>.\Carenavigraph.dll</Path> </Launch.Addon> <Launch.Addon> <Name>XMLTools3D</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>XMLTools3D.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>as_connect</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp.dll</Path> </Launch.Addon> <Launch.Addon> <Name>VRS_TacPack</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path> </Launch.Addon> </SimBase.Document>

Just for Info: 5/Jan/2017 13:15 All ok here with FSUIPC 4.959 / Win7-64 / P3D 3.4.18.19.475 ** FSUIPC loaded near / first (top/ I always move it/put it there) in DLL.xml: C:\Users\Vaughan\AppData\Roaming\Lockheed Martin\Prepar3D v3 example: <?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>Traffic Toolbox</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3 SDK 3.4.18.19475\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG HUD interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> ** FSUIPC not present: C:\ProgramData\Lockheed Martin\Prepar3D v3 ** I do not use Linda

"It will be included in the next Installer Update. I'm just waiting for some feedback on the new PMDG 737NGX CDU offsets I've added." Right, I seen you were testing in another post version Q .. Thanks for the fix. Have a good day.

I only used the DLL from your zip in my modules folder ... P3Dv3.1 started OK now. 15 Trying F:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll 15 Found it: trying to connect 31 FS path = "F:\Lockheed Martin\Prepar3D v3\" 125 ---------------------- Joystick Device Scan ----------------------- 125 Product= CH PRO PEDALS USB 125 Manufacturer= CH PRODUCTS 125 Vendor=068E, Product=00F2 (Version 0.0) 125 Serial Number= 140 Product= Saitek X52 Flight Control System 140 Manufacturer= Saitek 140 Vendor=06A3, Product=075C (Version 1.16) 140 Serial Number= 140 Product= Saitek Pro Flight Yoke 140 Manufacturer= Saitek 140 Vendor=06A3, Product=0BAC (Version 3.3) 140 Serial Number= 140 Product= Saitek Pro Flight Quadrant 140 Manufacturer= Saitek 140 Vendor=06A3, Product=0C2D (Version 2.0) 140 Serial Number= 140 ------------------------------------------------------------------- 156 LogOptions=00000000 00000001 156 ------------------------------------------------------------------- 156 ------ Setting the hooks and direct calls into the simulator ------ 156 --- CONTROLS timer memory location obtained ok 156 --- SIM1 Frictions access gained 156 --- FS Controls Table located ok 156 --- Installed Mouse Macro hooks ok. 156 --- Wind smoothing fix is installed 156 --- All links okay (except older global weather setting method) 156 ------------------------------------------------------------------- 156 SimConnect_Open succeeded: waiting to check version okay 156 Trying to use SimConnect Prepar3D 32713 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.1.3.1 (SimConnect: 3.1.0.0) 32713 Initialising SimConnect data requests now 32713 FSUIPC Menu entry added 32713 C:\Users\Vaughan\Documents\Prepar3D v3 Files\MooneyBravo-P3D-default-startup-flight.fxml 32713 F:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\Mooney_Bravo\Mooney_Bravo.air 76362 System time = 25/04/2016 13:43:18, Simulator time = 13:42:34 (17:42Z) 76378 Aircraft="Mooney Bravo" 77392 Starting everything now ... 77392 Run: "C:\Program Files (x86)\EZCA\EZCA.exe" 77439 ASN active function link set 77439 Ready for ASN WX radar 141415 === NOTE: not calling SimConnect_Close ... 142413 System time = 25/04/2016 13:44:24, Simulator time = 13:42:38 (17:42Z) 142413 *** FSUIPC log file being closed

Before doing the test do I need to put the DLL back into my Modules folder? Just looked at the ZIP .. It will be the only dll in the modules folder for the test.

I will download your file and test it now.

"he SimConnectP3D2.DLL should have been deleted by the FSUIPC4 Installer." I would not know .. never pay attention to what is in there ... I moved both DLL's out of the P3Dv3.1 Modules folder and put them on my desktop for safe keeping. P3Dv3.1 started ok. What should I do next?

I just went to my P3Dv3.1 Modules folder and noticed there are two DLL files in there?? Edit: yes, I could do a test for you ....

Pete, Thanks for the quick follow up. "Since you also have FSX installed all you need to do is remove the SimConnectP3D3.DLL from the P3D Modules folder. FSUIPC will use the FSX SimConnect quite happily." Will do . "Any reason you aren't updating to 3.2? It is said to be much better." When all my addons are said to be ok with it I will uninstall all my aircraft and scenery from P3Dv3.1 .... a big job ... and the do a full Install of P3Dv3.2 .. or 3.3 if I wait long enough and all my addons and scenery .. another big job at least for me. Edit: "I'll see if I can find a version 3.0 of the SimConnect.lib file and re-compile my interface DLL with that. Do you think you could test it for me when I have? I cannot install 3.0 or 3.1 now." I just seen this comment .. thanks. Yes I could do the test now. I will stand by.

FSUIPC 4949P gives Simconnect error for P3Dv3-1 Working ok in FSX Acceleration

Just for info. I have not seen this problem on my setup (Win7-64/FSUIPC 4.949 /P3Dv3.1 (Client only upgrade)). I do not have SavePreviousFlight=no in the ini file (never prior either). I never use FSUIPC's autosave but I did here for a test without any problems to report. P3Dv3.1 closes in 4 seconds or less with PMDG737NGX (or any other aircraft) with any FSUIPC option(s) On or OFF. I also posted on P3D forum : http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=116508

"Thanks for the information." You are welcome ... thanks for your help also. "Hmm. Wonder why it has to be turned off for the hotkey to work correctly." I really do not know ... but if you discover the reason I sure would like to know.