MazGan Posted February 21, 2017 Report Posted February 21, 2017 So as the title says FSUIPC4.ini file dosen't create its self and FSUIPC dosen't show in addons in game using P3D.
Pete Dowson Posted February 21, 2017 Report Posted February 21, 2017 19 minutes ago, MazGan said: So as the title says FSUIPC4.ini file dosen't create its self and FSUIPC dosen't show in addons in game using P3D. Did you actually install FSUIPC? Did the install succeed okay? Where's the Install log? What version of P3D? What version of FSUIPC? It really is a waste of time posting questions like this with zero information! Pete
MazGan Posted February 21, 2017 Author Report Posted February 21, 2017 sorry for not posting it in the first time I did install FSUIPC version of P3D is 3.4 version of FSUIPC 4.962 Installer for FSUIPC4.DLL version 4.962 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" ... NOT found! ... 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" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v3 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v3! <<< ... SetupPath=D:\Prepar3D\ =========================================================== INSTALLATION FOR Prepar3D v3: SetupPath="D:\Prepar3D\" Checking version of the Prepar3D v3 EXE: ... Version 3.4.22.19868 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Checking if there's already a version of FSUIPC4 installed in: D:\Prepar3D\Modules\FSUIPC4.DLL ... Version 4.962 found. Prepar3D v3 Modules folder already exists. Okay -- installed FSUIPC4 into "D:\Prepar3D\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\riis1\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\Default.migrated\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\riis1\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\riis1\AppData\Roaming\Lockheed Martin\Prepar3D v3\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 ... ... There is a SimConnect.XML, checking for "local" section. ... "local" section already exists, file not modified. Looking in "C:\Users\TEMP\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 "SimConnectP3D3.dll" okay Now installing additional files into the "Modules\FSUIPC Documents" folder: Failed to install "FSUIPC4 User Guide.pdf" Error 32 reported ("The process cannot access the file because it is being used by another process. ") Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.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 "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 exit: selected FSUIPC REGISTER Providing FSUIPC registration dialogue ... Registration for FSUIPC4 was successful! (result code 00) *************** End of Install Log ***************
Pete Dowson Posted February 21, 2017 Report Posted February 21, 2017 Okay. So either the DLL.XML file is corrupted -- the one in C:\Users\riis1\AppData\Roaming\Lockheed Martin\Prepar3D v3\ or it is crashing on load. Show me the DLL.XML file, and see if there is an FSUIPC4.LOG file produced in the Modules folder -- if so, post it here. And check in Windows Event Viewer for an Application Log error showing a crash in Prepar3D.exe. If so, grab the details and post here. You might also try replacing the DLL with the latest interim update available in the Download Links subforum. Version 4.963 is due to be released tomorrow, and the day after. Keep an eye out for that in the Download Links subforum. Pete
MazGan Posted February 21, 2017 Author Report Posted February 21, 2017 So there is no FSUIPC4.LOG in Modules folder but I will post here the DLL.xml and I think it's messing active sky aswell becuase active sky is not working as well. seems that I have more then one error. שם יישום שחלות בו תקלות: couatl.exe, גירסה: 3.1.0.3625, חותמת זמן: 0x58921765 שם מודול שחלות בו תקלות: KERNELBASE.dll, גירסה: 10.0.14393.479, חותמת זמן: 0x58256d37 קוד חריגה: 0xc0000409 היסט תקלה: 0x000da832 מזהה תהליך שחלות בו תקלות: 0x4e4 שעת ההפעלה של היישום שחלות בו תקלות: 0x01d28c6a46b1f30e נתיב היישום שחלות בו תקלות: D:\Prepar3D\fsdreamteam\couatl\couatl.exe נתיב המודול שחלות בו תקלות: C:\WINDOWS\System32\KERNELBASE.dll מזהה דוח: 779bd3e2-e110-4961-bbc8-9a4f785f2c76 שם מלא של החבילה שחלות בה תקלות: מזהה יישום יחסי לחבילה שחלות בה תקלות: ------------------------------------------------------------------- מוצר: Microsoft Flight Simulator SimConnect Client v10.0.60905.0 -- שגיאה 1316. The specified account already exists. ------------------------------------------------------------------ שם יישום שחלות בו תקלות: Prepar3D.exe, גירסה: 3.4.22.19868, חותמת זמן: 0x588f7cbf שם מודול שחלות בו תקלות: ntdll.dll, גירסה: 10.0.14393.479, חותמת זמן: 0x58256ca0 קוד חריגה: 0xc0000005 היסט תקלה: 0x0004d3c7 מזהה תהליך שחלות בו תקלות: 0x284c שעת ההפעלה של היישום שחלות בו תקלות: 0x01d28c5fa29d8e78 נתיב היישום שחלות בו תקלות: D:\Prepar3D\Prepar3D.exe נתיב המודול שחלות בו תקלות: C:\WINDOWS\SYSTEM32\ntdll.dll מזהה דוח: 4199c760-f134-4695-a1cd-a7ae728fe4d0 שם מלא של החבילה שחלות בה תקלות: מזהה יישום יחסי לחבילה שחלות בה תקלות: ------------------------------------------------------------------------------------ <?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>Migration Tool Plugin</Name> <Path>MigTool.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>D:\Prepar3D\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_Interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>RAASPRO</Name> <Disabled>False</Disabled> <Path>.\RAASPRO\RAASPRO.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </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>PMDG Options</Name> <Disabled>Flase</Disabled> <Path>PMDG\DLLs\PMDGOptions.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Events</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGEvents.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Sounds</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGSounds.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>as_connect</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp.dll</Path> </Launch.Addon> </SimBase.Document>
Pete Dowson Posted February 21, 2017 Report Posted February 21, 2017 3 hours ago, MazGan said: So there is no FSUIPC4.LOG in Modules folder but I will post here the DLL.xml and I think it's messing active sky aswell becuase active sky is not working as well. seems that I have more then one error. Well, yes -- COATL is crashing by the look of it. You need to go get the latest DreamTeam / Virtuali Add-On Manager. It will install updates for both COUATL and BGLMANX. Neither of the crashes into Windows are related to FSUIPC. And the DLL.XML looks like it came from FSX, not P3D -- Vistamare.DLL is certainly not compatible with P3D, for example. That's the DLL supporting Aerosoft's AES which isn't P3D compatible (nor FSX-SE in fact). It isn't an FSUIPC problem in any case.
MazGan Posted February 22, 2017 Author Report Posted February 22, 2017 Alright so I completely deleted GSX with COATL and addon manger launched up the game and FSUIPC is still not showing and in the DLL.XML file the Vistamare.dll is there maybe because I haev mirgation tool?
Pete Dowson Posted February 22, 2017 Report Posted February 22, 2017 1 hour ago, MazGan said: Alright so I completely deleted GSX with COATL and addon manger launched up the game and FSUIPC is still not showing and in the DLL.XML file the Vistamare.dll is there maybe because I haev mirgation tool? Vistamare crashes here with P3D. Why haven't you deleted that? Migration tools are a menace. Why are you using one? Pete
MazGan Posted February 22, 2017 Author Report Posted February 22, 2017 Just now, Pete Dowson said: Vistamare crashes here with P3D. Why haven't you deleted that? Migration tools are a menace. Why are you using one? Pete Used it to use md-11 in p3d and some sceneries.
MazGan Posted February 22, 2017 Author Report Posted February 22, 2017 Anything that I can do to fix it?
Pete Dowson Posted February 22, 2017 Report Posted February 22, 2017 18 minutes ago, MazGan said: Anything that I can do to fix it? Why haven't you deleted the Vistamare entry? Try deleting or renaming the DLL.XML file completely, then re-running the FSUIPC installer. Pete
MazGan Posted February 22, 2017 Author Report Posted February 22, 2017 7 minutes ago, Pete Dowson said: Why haven't you deleted the Vistamare entry? Try deleting or renaming the DLL.XML file completely, then re-running the FSUIPC installer. Pete Deleted and rerun but still nothing works and if I check Modules folder there is no FSUIPC.ini file.
MazGan Posted February 22, 2017 Author Report Posted February 22, 2017 And when I delete DLL.XML its not building its self again so there is no dll file after i delete it and re run the sim so this may be the problem
Pete Dowson Posted February 22, 2017 Report Posted February 22, 2017 Okay. In that case it seems that SimConnect is not loading it. Please look in the FAQ subforum for a thread which tells you how to make a SimConnect log file. Do what that says, then try again, and show me the SimConnect log it produces. Pete
Pete Dowson Posted February 22, 2017 Report Posted February 22, 2017 1 minute ago, MazGan said: And when I delete DLL.XML its not building its self again so there is no dll file after i delete it and re run the sim so this may be the problem Ah, that's different. So the installer is not making one? Either you forgot to rerun the FSUIPC Installer as I told you, or you are looking in the wrong folder. Look at the FSUIPC install log. Pete
MazGan Posted February 22, 2017 Author Report Posted February 22, 2017 I did rerun FSUIPC and i'm looking in appdata/roaming Installer for FSUIPC4.DLL version 4.962 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" ... NOT found! ... 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" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v3 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v3! <<< ... SetupPath=D:\Prepar3D\ =========================================================== INSTALLATION FOR Prepar3D v3: SetupPath="D:\Prepar3D\" Checking version of the Prepar3D v3 EXE: ... Version 3.4.22.19868 (Need at least 1.0.677.0) Checking compatibility with installed SimConnect: Checking if there's already a version of FSUIPC4 installed in: D:\Prepar3D\Modules\FSUIPC4.DLL ... No previous valid version found. Prepar3D v3 Modules folder already exists. Okay -- installed FSUIPC4 into "D:\Prepar3D\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\riis1\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\Default.migrated\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\riis1\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\riis1\AppData\Roaming\Lockheed Martin\Prepar3D v3\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 ... ... There is a SimConnect.XML, checking for "local" section. ... "local" section already exists, file not modified. Looking in "C:\Users\TEMP\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 "SimConnectP3D3.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 "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 "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 exit: selected FSUIPC REGISTER Providing FSUIPC registration dialogue ... Registration for FSUIPC4 was successful! (result code 00) *************** End of Install Log ***************
MazGan Posted February 22, 2017 Author Report Posted February 22, 2017 I think I got it working I don't know what I did but I can see FSUIPC in game now
MazGan Posted February 22, 2017 Author Report Posted February 22, 2017 The dll file did create itself but there is only fsuipc there
MazGan Posted February 22, 2017 Author Report Posted February 22, 2017 I tried switcing the new dll with the old one and its stopped working again so there is something in the file that is making fsuipc not to work
Pete Dowson Posted February 22, 2017 Report Posted February 22, 2017 37 minutes ago, MazGan said: I did rerun FSUIPC and i'm looking in appdata/roaming Well, you did something wrong because the file was not only written BUT THERE WAS ONE BEFORE -- even though you say you deleted it!!! See: Found Prepar3D.CFG in "C:\Users\riis1\AppData\Roaming\Lockheed Martin\Prepar3D v3\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 The full folder name is C:\Users\riis1\AppData\Roaming\Lockheed Martin\Prepar3D v3\ 37 minutes ago, MazGan said: I got it working I don't know what I did but I can see FSUIPC in game now Okay. 37 minutes ago, MazGan said: The dll file did create itself but there is only fsuipc there FSUIPC4.DLL, FSUIPC4.INI and FSUIPC4.LOG, and the FSUIPC Documents subfolder, are all absolutely guaranteed to be there, if it appears in game. So now I'm sure you are not looking correctly. This confirms you are really in a mess when it comes to dealing with files and folders: 38 minutes ago, MazGan said: I tried switcing the new dll with the old one and its stopped working again so there is something in the file that is making fsuipc not to work Exactly HOW did you do this "switching"? Pete
MazGan Posted February 22, 2017 Author Report Posted February 22, 2017 I saved the old dll file on desktop and just paste it in the folder and changed the name to DLL.xml because i changed it so it dosent do anything with the new one Am I doing something wrong and I dont see it?
Pete Dowson Posted February 22, 2017 Report Posted February 22, 2017 15 minutes ago, MazGan said: I saved the old dll file on desktop and just paste it in the folder and changed the name to DLL.xml because i changed it so it dosent do anything with the new one Ah, you mean the DLL.XML file, not FSUIPC4.DLL which is a DLL file!!! All you proved is that something is wrong with that DLL.XML file, or it is loading something bad! Just start with the one made fresh by FSUIPC, and add the items you need one by one and test each time. Do NOT include Vistamare! You've also proved you do NOT have a problem with FSUIPC, but with something else you've added. Pete
MazGan Posted February 22, 2017 Author Report Posted February 22, 2017 Alirght Added all items to the DLL.xml file without Vistamare and all seems to work perfect. Thanks for the help!
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