wizzards Posted February 5, 2014 Report Posted February 5, 2014 i have been using FSUIPC (correct version) with P3d 1.4 and P3d v2 with no issues,I recently installed some add ons using the EMT they seem to run perfectly, but strangely FSUIPC is now showing as being registered only in P3d v1.4 and not reg in P3d v2 ,it was working ok in P3d v2 before, i have deleted and reinstalled FSUIPC approx 4 time but it still shows reg in P3d v1.4 but un reg in P3d v2,the instaler shows that it has been installed in both P3d 1.4 and v2 ,any help greatfully recieved peter
Pete Dowson Posted February 6, 2014 Report Posted February 6, 2014 i have been using FSUIPC (correct version) with P3d 1.4 and P3d v2 with no issues,I recently installed some add ons using the EMT they seem to run perfectly, but strangely FSUIPC is now showing as being registered only in P3d v1.4 and not reg in P3d v2 ,it was working ok in P3d v2 before, i have deleted and reinstalled FSUIPC approx 4 time but it still shows reg in P3d v1.4 but un reg in P3d v2,the instaler shows that it has been installed in both P3d 1.4 and v2 ,any help greatfully recieved Does this "EMT" thing, whatever it is, rename the Prepar3.EXE file by any chance, or change its version number? Please show me the log file from a session in P3Dv2 (FSUIPC4.LOG, from the Modules folder). You can paste its contents into a message here. Please close P3D first. Pete
wizzards Posted February 6, 2014 Author Report Posted February 6, 2014 hello, the fightsim estonia migration tool places a dummy FSX CFG in the same folders as the P3d v1.4 CFG or P3d v2 CFG I have tried deleting the Fsx CFG entry and then reinstalling FSUIPC ,it made no difference enclosed the FSUIPC install file you requested (hope it is the correct file) thanks for your help peter Installer for FSUIPC4.DLL version 4.928Looking 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\FSX Parameter"AppPath"... NOT found! ...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 Prepar3D:SetupPath="E:\Prepar3d\"Checking version of the Prepar3D EXE:... Version 1.4.4747.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\Modules\FSUIPC4.DLL... Version 4.928 found.Prepar3D Modules folder already exists.Okay -- installed FSUIPC4 into "E:\Prepar3d\Modules\FSUIPC4.DLL"Looking for the current user's Application Data path:... found as "C:\Users\peter1\AppData\Roaming"Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this oneLooking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG thereLooking in "C:\Users\Default\AppData\Roaming" ... No Prepar3D.CFG thereLooking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG thereLooking in "C:\Users\peter1\AppData\Roaming"Found Prepar3D.CFG in "C:\Users\peter1\AppData\Roaming\Lockheed Martin\Prepar3D\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 okayNow 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\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 "SimConnectP3D.dll" okayNow 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 "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay===========================================================INSTALLATION FOR Prepar3D v2:SetupPath="E:\Prepar3dV2\"Checking version of the Prepar3D v2 EXE:... Version 2.0.9448.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:\Prepar3dV2\Modules\FSUIPC4.DLL... Version 4.928 found.Prepar3D v2 Modules folder already exists.Okay -- installed FSUIPC4 into "E:\Prepar3dV2\Modules\FSUIPC4.DLL"Looking for the current user's Application Data path:... found as "C:\Users\peter1\AppData\Roaming"Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this oneLooking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG thereLooking in "C:\Users\Default\AppData\Roaming" ... No Prepar3D.CFG thereLooking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG thereLooking in "C:\Users\peter1\AppData\Roaming"Found Prepar3D.CFG in "C:\Users\peter1\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 okayNow checking for a SimConnect.XML file ...... No SimConnect.XML file found. This is okay.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" okayNow 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 "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay===========================================================All installer tasks completed.Registration for FSUIPC4 was successful! (result code 00)*************** End of Install Log ***************
Pete Dowson Posted February 6, 2014 Report Posted February 6, 2014 hello, the fightsim estonia migration tool places a dummy FSX CFG in the same folders as the P3d v1.4 CFG or P3d v2 CFG I have tried deleting the Fsx CFG entry and then reinstalling FSUIPC ,it made no difference That will make absolutely no difference at all. The only reason the Installer looks for the CFG file is to make sure it puts or updates the DLL.XML file in the correct place. If your FSUIPC is getting loaded, as it must be if it appears (whether registered or not), then there is no problem with that folder. Do NOT delete and CFG files -- they are completely irrelevant. enclosed the FSUIPC install file you requested (hope it is the correct file) I did not ask for any install file. The Install log shows everything installed okay, but I had assumed that from what you said. The answer might be in the FSUIPC4 run time log, which is what I asked for -- it is called FSUIPC4.LOG (no "Install" in the name at all) as I already said. Pete
wizzards Posted February 9, 2014 Author Report Posted February 9, 2014 hello sorry had folders hidden hope this is correct peter h********* FSUIPC4, Version 4.928 by Pete Dowson *********Running inside Prepar3D v2 on Windows 7... Prepar3D has been renamed as "Prepar3Dv2"Module base=5E9A0000User Name=""User Addr=""FSUIPC4 not user registeredWIDEFS7 not user registered, or expired 31 System time = 09/02/2014 17:04:09 31 FLT path = "C:\Users\peter1\Documents\Prepar3D v2 Files\" 31 Trying E:\Prepar3Dv2\Modules\SimConnectP3D2.dll 124 Found it: trying to connect 124 FS path = "E:\Prepar3Dv2\" 421 LogOptions=00000000 00000001 421 SIM1 Frictions access gained 421 Wind smoothing fix is fully installed 421 SimConnect_Open succeeded: waiting to check version okay 421 Trying to use SimConnect Prepar3D 421 Running in "Lockheed Martin® Prepar3D® v2", Version: 2.0.9448.0 (SimConnect: 2.0.0.0) 421 Initialising SimConnect data requests now 421 FSUIPC Menu entry added 436 E:\Prepar3Dv2\FLIGHTS\OTHER\Prepar3D.FXML 436 E:\Prepar3Dv2\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.AIR 61916 System time = 09/02/2014 17:05:10, Simulator time = 06:20:01 (10:20Z) 66940 Starting everything now ... 68125 Advanced Weather Interface Enabled 125549 Sim stopped: average frame rate for last 34 secs = 23.4 fps 144722 System time = 09/02/2014 17:06:33, Simulator time = 06:20:22 (10:20Z) 144722 *** FSUIPC log file being closedAverage frame rate for running time of 52 secs = 23.7 fpsMemory managed: 26 Allocs, 26 Freed********* FSUIPC Log file closed ***********
Pete Dowson Posted February 9, 2014 Report Posted February 9, 2014 ********* FSUIPC4, Version 4.928 by Pete Dowson ********* Running inside Prepar3D v2 on Windows 7 ... Prepar3D has been renamed as "Prepar3Dv2" That's your problem. Why have you renamed Prepar3D.exe to Prepar3Dv2.exe? Unless you fix that, all of your FSUIPC related data files will probably be renamed to suit. What was the actual name of this log, for instance? Something like "FSUIPC4.Prepar3Dv2.log" perhaps? Whatever, both your INI file (if you transferred on from another FS installation), and, crucially for the registration check, your KEY file will need renaming too. Pete
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