5.123 not installing

[rusblag]

Hi Pete,

Never ever had a problem updating before.  Had  ver. 5.122a and updated to ver.5.123   The install log says it installed OK...but no FSUIPC in the addon menu, but the log file and ini file  stayed the same showing ver. 5.122.  I deleted the log file and re-ran the installer. That put a 5.123 installer log in the modules folder, but still left the ini file showing ver.5.122, but still no FSUIPC in the addons menu, so it appears to be not actually installing.

/Russell

Installer for FSUIPC5.DLL version 5.123

Looking in registry for Prepar3D v4 install path:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4
     Parameter"AppPath"
... >>>  OK! FOUND Prepar3D v4!  <<< ...
     AppPath=D:\Lockheed Martin\Prepar3D v4\
===========================================================

INSTALLATION FOR Prepar3D v4:
AppPath="D:\Lockheed Martin\Prepar3D v4\"
Checking version of the Prepar3D v4 EXE:
... Version 4.1.7.22841  (Need at least 4.1.0.0)
Checking if there's already a version of FSUIPC5 installed as:
       D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL
... Version 5.123 found.
D:\Lockheed Martin\Prepar3D v4\Modules folder already exists.
Okay -- installed FSUIPC5 into "D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Rus\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\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Rus\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Rus\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 ...
... There is a SimConnect.XML, checking for "local" section.
... "local" section already exists, file not modified.
"Modules\FSUIPC Documents" folder already exists.
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 "FSUIPC4 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 CHECK
Checking FSUIPC registration ...
Registration check for FSUIPC5 was successful! (result code 00)

*************** End of Install Log ***************

 

[Pete Dowson]

16 minutes ago, rusblag said:

Never ever had a problem updating before.  Had  ver. 5.122a and updated to ver.5.123   The install log says it installed OK...but no FSUIPC in the addon menu, but the log file and ini file  stayed the same showing ver. 5.122.  I deleted the log file and re-ran the installer. That put a 5.123 installer log in the modules folder, but still left the ini file showing ver.5.122, but still no FSUIPC in the addons menu, so it appears to be not actually installing.

It is installing, just not being loaded by SimConnect. That is odd. I'd need to check your DLL.X ML file, from the Appdata\Roaming L-M folder for P3D4, i.e. in
C:\Users\Rus\AppData\Roaming\Lockheed Martin\Prepar3D v4

BTW if you downloaded 5.123 very soon after I uploaded it you will probably need to download it again, as I uploaded a corrected version. The original had an odd SimConnect incompatibility with P3D 4.1.7. It wouldn't result in it not being run, only in it failing, with a log entry, when running.

Pete

 

[rusblag]

<?xml version="1.0" encoding="WINDOWS-1252"?>

<SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>SSWF-104S</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-F104S-ASA\modules\zipper.dll</Path> <DllStartName>f104s_cvars_init</DllStartName> <DllStopName>f104s_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW_NASARR21G</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-F104S-ASA\modules\nasarR21G.dll</Path> <DllStartName>nasar21_init</DllStartName> <DllStopName>nasar21_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>vACMI</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>.\vACMI.dll</Path> <DllStartName>vacmi_cvars_init</DllStartName> <DllStopName>vacmi_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>D:\Lockheed Martin\Prepar3D v4 SDK 4.1.7.22841\World\Traffic\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>D:\Lockheed Martin\Prepar3D v4 SDK 4.1.7.22841\Modeling\Special Effects\Visual FX Tool\visualfxtool.dll</Path> </Launch.Addon> <Launch.Addon> <Name>SSW-F84F</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-F84F\modules\thunder.dll</Path> <DllStartName>f84_cvars_init</DllStartName> <DllStopName>f84_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>WebSimClient</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimSkunkWorks\WebSimConnect\modules\WSC_Client.dll</Path> <DllStartName>wsc_cvars_init</DllStartName> <DllStopName>wsc_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW-PA200</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-TORNADO\modules\panavia.dll</Path> <DllStartName>pa200_cvars_init</DllStartName> <DllStopName>pa200_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW_PA200_RADAR</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-TORNADO\modules\pa200radar.dll</Path> <DllStartName>radar_init</DllStartName> <DllStopName>radar_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW_NASARR15</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-FRF-104G\modules\nasarr15.dll</Path> <DllStartName>nasarr15_init</DllStartName> <DllStopName>nasarr15_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW-FRF104G</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-FRF-104G\modules\zipper_g.dll</Path> <DllStartName>frf104g_cvars_init</DllStartName> <DllStopName>frf104g_cvars_init</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW.MIRAGEF1</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-MIRAGE-F1\modules\ssw_miragef1.dll</Path> <DllStartName>f1_cvars_init</DllStartName> <DllStopName>f1_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>MIRAGE_RWR</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-MIRAGE-F1\modules\F1rwr.dll</Path> <DllStartName>f1_rwr_init</DllStartName> <DllStopName>f1_rwr_init</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW-AV8IIB</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-AV8B-HARRIER-IIB\modules\harrier.dll</Path> <DllStartName>av8_cvars_init</DllStartName> <DllStopName>av8_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW-RBVSTOL</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-AV8B-HARRIER-IIB\modules\rbvstol.x64.dll</Path> <DllStartName>cvars_init</DllStartName> <DllStopName>cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 5</Name> <Disabled>False</Disabled> <Path>D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.dll</Path> </Launch.Addon>

</SimBase.Document>

[rusblag]

Forgot to say...I downloaded it at 10.42pm today.

/Russell

[Pete Dowson]

27 minutes ago, rusblag said:

Forgot to say...I downloaded it at 10.42pm today.

The XML.DLL you posted is almost impossible for me to check, as it is missing all of its natural formatting. Could you please instead ZIP it and attach it?

Pete

 

[rusblag]

Sorry about that Pete.

DLL.zip

[Pete Dowson]

Wow! I've never seen so many Add-In DLLs. I'm wondering if this is breaking some P3D4 limit (a bug with too many scenery add-on XMLs which is being investigated now).

As well as FSUIPC and two P3D SDK DLLs, there are 13 DLLs, mostly for add-on aircraft by the look of it.

Just to check it isn't specifically FSUIPC, could you try renaming your current DLL.XML, say to DLL.XMLx, then re-run the FSUIPC Installer see if that works okay. If it doesn't, see below. If it does, delete the new DLL.XML and rename your normal one back.

Then, in either case, enable SimConnect logging (see the FAQ thread for details) and re-run P3D. Then find the Simconnect log file and show me that, please. It should show why it isn't being loaded.

Pete

 

[rusblag]

Hi Pete,

I created the simconnect.ini and placed it in the Prepar3D files in My Documents, then ran the sim.  It shows nothing.   This is the simconnect.ini   Have I done it right ?

/Russell

       

simconnect.ini

[rusblag]

Oh damn...I was looking in the wrong place.    Here it is.  Sorry about that.

/Russell

SimConnect0.Log

[Pete Dowson]

56 minutes ago, rusblag said:

Here it is. 

Hmm. That shows that a previous session of P3D4 crashed on exit, and that Windows blamed FSUIPC, so prevents it loading by a Registry entry.

FSUIPC often gets the blame for the crash just because it usually has threads still running at the end (for Lua, WideFS, and other activities which take longer to close down). Are you using LINDA by any chance? That also uses some drivers which can exhibit the same problem on an exit crash.

The FSUIPC5 Installer should be clearing that indication in the Registry. are you sure you are running the Installer "as administrator" (a right-click option)? Because it seems that it isn't able to fx the entry itself.

The next P3D4 update is also supposed to fix this problem.

Pete

 

[rusblag]

Hi Pete,

              That's strange, as I was unaware that P3d had ever closed with a crash, it's always appeared to close normally.  I always run the installer as administrator.  5.123 is the first one that's given me a problem.   Would it be a good idea to delete  the 5.123 and install  5.122a again, which worked perfectly ?     No, I don't use Linda.    Thanks for your help anyway...much appreciated.   I've deleted 5.123,  installed 5.122 then updated to 5.122a.  Everything is now back and working.   Doesn't that point to a fault with 5.123 ?

/Russell

[Pete Dowson]

26 minutes ago, rusblag said:

That's strange, as I was unaware that P3d had ever closed with a crash, it's always appeared to close normally.

There seems to be quite a few types of P3D crash which don't provoke any error message, it just disappears as you'd expect it to do. Note for instance that the P3D windows disappear quite a few seconds before it is all actually closed, so if you, say, shutdown the PC too quickly afterwards that might force it to close, which is the same as a crash.

28 minutes ago, rusblag said:

Would it be a good idea to delete  the 5.123 and install  5.122a again, which worked perfectly ? 

The installation process hasn't changed. but do try 5.123b which is a fixed version of 5.123 and replaced it recently.

Pete

 

[rusblag]

OK,  5.123b  installed perfectly.    No two ways about it, your support is second to none.   I believe you are around one year younger than me, and it amazes me that your brain is still active and sharp enough to deal with, and cure, the constant stream of cries for help from all over the globe.   It really is appreciated Pete.

/Russell.

[Pete Dowson]

49 minutes ago, rusblag said:

OK,  5.123b  installed perfectly. 

Good. I was getting a bit worried as after tomorrow I'm off on holiday for two weeks, and needed to get this release out and working well beforehand because, knowing L-M, they'll release the next P3D4 update whilst i'm away. ;-)

Pete