Jump to content
The simFlight Network Forums

FSUIPC 4.90 not loading in FSX, loading in P3D


Recommended Posts

I wonder if I might ask for a bit of help with a sticky problem.

 

I tried to run FSX today after not having used it for a couple of months, and found that (registered) FSUIPC is not being loaded. No fsuipc.log file is being generated, so it never even starts to load.

 

I have fsuipc 4.90, the DLLs are in s:\fsx\modules\ and s:\prepar3d\modules respectively. I've compared the DLL.xml files, and although I have different addons in P3D and FSX, I can confirm that the fsx version is properly formatted (I even tried copy-pasting the working p3d one into the fsx one, then removing all dlls other than fsuipc from the list). I even MD5 checksummed the dll's themselves to make sure the one in the fsx modules folder was identical to the one in the p3d modules folder, and it is.

 

All the other addons in the FSX dll.xml file load properly.

Reinstalling FSUIPC in desparation, here's an extract from the log:

 

Checking version of 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)

 

I also removed the section in dll.xml, so that the installer would recreate it, however it made no difference. Here's my complete dll.xml:

 

 

<?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>FSForce DLL</Name>
        <Disabled>false</Disabled>
        <ManualLoad>false</ManualLoad>
        <Path>S:\Program Files (x86)\FSForce 2\FSForce.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>FS Recorder</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>S:\Program Files (x86)\FS Recorder for FSX\FSRecorder_FSX.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>Reality XP GNS WAAS Hardware</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>Modules\rxpGnsDriver.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>A2A Feel</Name>
        <Disabled>False</Disabled>
        <Path>Modules\A2A_Feel.dll</Path>
        <DllStartName>module_init</DllStartName>
        <DllStopName>module_deinit</DllStopName>
    </Launch.Addon>
  <Launch.Addon>
        <Name>AccuFeelMenu</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>Modules\AccuFeelMenu.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>SquawkBox Transponder</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>S:\Program Files (x86)\Squawkbox\sbtrans10.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>SquawkBox AI Control</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>S:\Program Files (x86)\Squawkbox\sbaicontrol10.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>SquawkBox Internal Version</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>S:\Program Files (x86)\Squawkbox\sbmod10.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>IvAp</Name>
        <Disabled>False</Disabled>
        <Path>S:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll</Path>
        <Commandline></Commandline>
    </Launch.Addon>
  <Launch.Addon>
        <Name>FSUIPC 4</Name>
        <Disabled>False</Disabled>
        <Path>Modules\FSUIPC4.dll</Path>
    </Launch.Addon>
</SimBase.Document>
 

 

As I said above, I also did try removing everything from this apart from the fsuipc section, but that made no difference.

 

I've also created a simconnect.ini to prompt generation of a simconnect log file, I won't post the whole thing here (for brevity), but the relevant section is:

 

0.00000 SimConnect version 10.0.61259.0

0.02451 Server: Scope=local, Protocol=Auto, Address=::1, Port=51773, MaxClients=64
0.03219 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64
0.05451 Server: Scope=local, Protocol=IPv6, Address=::1, Port=51774, MaxClients=64
0.07887 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=51775, MaxClients=64

 
0.18377 Exe Launched:  Path="S:\Program Files (x86)\FSForce 2\FSForce.exe"  CommandLine="/FS"  Version="2.6.0.4"
0.21591 Exe Launched:  Path="C:\Program Files (x86)\EZCA\EZCA.exe"  CommandLine=""  Version="1.1.7.2"
0.23196 Exe Launched:  Path="s:\Program Files (x86)\SPAD\Spad.exe"  CommandLine=""  Version="0.5.0.1"
0.37469 Exe Launched:  Path="S:\Prepar3D\\Flight One Software\Ultimate Traffic 2\UT2Services.exe"  CommandLine=""  Version="2.1.0.0"
0.38057 Panels data export found and set to 20B319D8
0.38334 DLL Loaded:  Path="S:\Program Files (x86)\FSForce 2\FSForce.dll"  Version="2.6.0.4"
0.40081 Panels data export found and set to 20B319D8
0.44778 DLL Loaded:  Path="S:\Program Files (x86)\FS Recorder for FSX\FSRecorder_FSX.dll"  Version="2.1.0.0"
0.45456 Panels data export found and set to 20B319D8
0.45457 DLL Loaded:  Path="Modules\rxpGnsDriver.dll"  Version="1.6.0.1"
0.47013 Panels data export found and set to 20B319D8
0.53138 DLL Loaded:  Path="Modules\A2A_Feel.dll"  Version="<Unknown>"
0.54039 Panels data export found and set to 20B319D8
0.54256 DLL Loaded:  Path="Modules\AccuFeelMenu.dll"  Version="0.1.0.0"
0.55612 DLL Loaded:  Path="S:\Program Files (x86)\Squawkbox\sbtrans10.dll"  Version="<Unknown>"
0.56515 DLL Loaded:  Path="S:\Program Files (x86)\Squawkbox\sbaicontrol10.dll"  Version="<Unknown>"
0.59975 DLL Loaded:  Path="S:\Program Files (x86)\Squawkbox\sbmod10.dll"  Version="<Unknown>"
0.61786 DLL Loaded:  Path="S:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll"  Version="2.0.2.2773"
> 14.12127 [191, 1]Open: Version=0x00000004  Name="TrackIR SimConnect Interface"
> 14.12194 [64, 1]Open: Version=0x00000004  Name="FSForce DLL"
> 14.12196 [64, 2]SubscribeToSystemEvent:EventID=0, SystemEventName="SimStart"
> 14.12196 [65, 1]Open: Version=0x00000004  Name="FS Force"
> 14.12198 [65, 2]RequestSystemState:RequestID=0, szState="Sim"
> 14.12199 [65, 3]SubscribeToSystemEvent:EventID=0, SystemEventName="SimStart"
> 14.12200 [190, 1]Open: Version=0x00000002  Name="FS Recorder"
> 14.12213 [66, 1]Open: Version=0x00000004  Name="A2A Feel"

 

Which doesn't seem to give any clues as to why fsuipc4.dll is not being loaded.

 

I normally start fsx through a batch file, but to eliminate that as an issue I've been starting it directly from s:\fsx\fsx.exe for testing. I have double checked it's set to run as administrator, not that it should make any difference.

 

I also tried removing fsuipc.ini from the modules folder, in-case something was wrong with it causing fsuipc not to start (although I'd expect an fsuipc.log to be created if that were the case) - in any event, it didn't help.

 

I remember having a problem with prepar3d hanging on startup with certain nvidia drivers some time back, which seemed to be related to a problem that the nvidia drivers caused in the loading sequence for fsuipc. Accordingly, I've tried rolling right back to 301.42 which also made no difference.

 

In the spirit of flailing about aimlessly, changing anything to see if it would help, I also disabled my antivirus and firewall - no dice.

 

I'm completely stumped here, so if anyone can help point me in the right direction about what to try next, I'd be very grateful.

Link to comment
Share on other sites

To follow up, I went back through a backup and found the fsuipc 4.86 dll file, so I tried that instead, and now FSX loads it OK and I get an fsuipc.log which I've pasted below. Everything seems to work OK - all I did was roll back the dll, without changing anything else.

 

It may be worth mentioning also, that in my post above I neglected to say that when trying to fix 4.90 I had tried using the fsuipc4_loader.dll file (and changing the dll.xml reference accordingly) without success.

 

Has anything changed between 4.86 and 4.90 in the loading code that could have caused the problem?

For now, I'll just continue to use 4.86, but it would be nice to get it sorted so I don't miss out on future improvements and updates. I'm happy to troubleshoot and post/email logs etc. as necessary.

 

 

********* FSUIPC4, Version 4.86 by Pete Dowson *********
Running inside FSX on Windows 7
Module base=54C00000
User Name=REMOVED
User Addr=REMOVED
FSUIPC4 Key is provided
WideFS7 Key is provided
    10671 System time = 03/07/2013 18:41:07
    10671 FLT UNC path = "R:\Users\Paul\My Documents\Flight Simulator X Files\"
    10718 Trying to connect to SimConnect Acc/SP2 Oct07 ...
    10733 FS UNC path = "S:\FSX\"
    11108 LogOptions=00000000 00000001
    11108 SIM1 Frictions access gained
    11108 Wind smoothing fix is fully installed
    11108 G3D.DLL fix attempt installed ok
    11108 SimConnect_Open succeeded: waiting to check version okay
    11108 Trying to use SimConnect Acc/SP2 Oct07
    11139 VRI port 1 "com4" opened
    16708 VRI FMER ("MCP Combi") detected on port com4
    24695 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
    24695 Initialising SimConnect data requests now
    24695 FSUIPC Menu entry added
    24758 R:\users\paul\My Documents\Flight Simulator X Files\Duke at Bournemouth.FLT
    24758 S:\FSX\SimObjects\Airplanes\RealAir Duke B60\RealAir_Duke.AIR
    28018 System time = 03/07/2013 18:41:25, Simulator time = 18:41:21 (17:41Z)
    28205 Aircraft="RealAir Beech Duke N1873K Winglets Ventral"
   102212 Starting everything now ...
   102243 LUA.0: beginning "S:\FSX\Modules\ipcReady.lua"
   102243 LUA.0: ended "S:\FSX\Modules\ipcReady.lua"
   102243 LUA.1:


   102243 LUA.1: [iNIT]LINDA:: Loading...
   102337 LUA.1: LINDA:: Aircraft: RealAir Beech Duke N1873K Winglets
   102337 LUA.1: LINDA:: Aircraft module detected: FSX Default
   102399 LUA.0: LINDA:: AivlaSoft library loaded...
   102399 LUA.0: LINDA:: FSX standard library loaded...
   102415 LUA.0: LINDA:: IAO library loaded...
   102415 LUA.0: LINDA:: RealityXP library loaded...
   102431 LUA.0: LINDA:: A2A MAP library loaded...
   104069 LUA.0: LINDA:: Module: FSX Default Started...
   104069 LUA.0: LINDA:: Ready to go, Captain!
   104069 LUA.0: LINDA::
   105800 Advanced Weather Interface Enabled
 

Link to comment
Share on other sites

To follow up, I went back through a backup and found the fsuipc 4.86 dll file, so I tried that instead, and now FSX loads it OK and I get an fsuipc.log which I've pasted below. Everything seems to work OK - all I did was roll back the dll, without changing anything else.

 

The only possible cause I can think of is that somehow you got SimConnect classifying 4.90 as untrusted, so not to load it.  Try deleting the entries in the [Trusted] section of the FSX.CFG, or maybe just put the latest version from Download Links into the Modules folder instead of the 4.90 main release so that it will ask again.

 

Regards

Pete

Link to comment
Share on other sites

Thanks for the reply Pete.

 

I did try deleting the trust line in fsx.cfg, and with stock (main release) 4.90 I got no request to trust the module.

 

I also tried 4.907 from the latest download link, and again, after removing the trusted line from the fsx.cfg there is no request to trust the module when fsx starts and there is no fsuipc.log generated.

 

I've rolled back again to 4.86, so I'm up and running for the time being.

 

I'm pretty sure this must have something to do with the newer .dlls being unsigned, but what could be happening such that simconnect logs nothing at all about it, I'm not sure.

 

How does 4.86 and earlier actually perform the signature check - is it all internal to the driver or does it use the windows PKI? I'm at a bit of a loss as to why 4.86 is still working if the signature has been revoked, so I'm concerned that at some point it may stop working and I won't be able to update to 4.90 and later. I looked in the certificate snap-in in the MMC and the Simflight (and GlobalSign CA) certificates show no sign of having been revoked in there, so maybe my machine hasn't downloaded the CRL (yet?)???

 

I note in your post about the globalsign CA compromise that you mention the CRL being updated via windows update, but I have no pending updates that could be relevant. Are you aware whether the update revoking the certificate has been pushed out via windows update yet?

Link to comment
Share on other sites

I did try deleting the trust line in fsx.cfg, and with stock (main release) 4.90 I got no request to trust the module.

I also tried 4.907 from the latest download link, and again, after removing the trusted line from the fsx.cfg there is no request to trust the module when fsx starts and there is no fsuipc.log generated.

 

 

If there's no message asking if it is okay to load it, then SimConnect must already have read something which tells them not to. In the days when FSUIPC4 was signed this would have been by the Publisher (SimFlight) being already listed as "untrusted" in the Registry, as seen in Internet Explorer. But with an unsigned module it doesn't know the publisher, so that can't happen. It can only really happen due to a reference in its FSX.CFG.

 

So your experiences are absolutely puzzling.

 

Does the SimConnect log show any reason why it won't load it? (See the FAQ subforum for a thread  about enabling the SimConnect log).

 

I've rolled back again to 4.86, so I'm up and running for the time being.

 

Well, being signed that won't generate the prompt as to whether you want to load it or not, but it is subject to the publisher being trusted -- and the signature being valid. One day GlobalSign will maybe catch up and get the revocation actioned.

 

I can't support older versions in any case.

 

I'm pretty sure this must have something to do with the newer .dlls being unsigned, but what could be happening such that simconnect logs nothing at all about it, I'm not sure.

 

The signature omission should make things simpler, less error prone, not more so. Very few add-ons are signed, so FSUIPC now just joins the rest. And do I understand you've already tried a SimConnect log and it doesn't even mention FSUIPC4? That's as if it isn't in the DLL.XML and therefore is simply not even looked for.

 

How does 4.86 and earlier actually perform the signature check - is it all internal to the driver or does it use the windows PKI? I'm at a bit of a loss as to why 4.86 is still working if the signature has been revoked

 

 

Me too. GlobalSign, the signature authority, said the revocation would take place within hours. It happens through Microsoft updates, so maybe it takes longer. Someone also said the publisher updates only occur once a week. However, I've been accepting all windows updates on my test PC ever since and the revocation still hasn't occurred. Makes me feel like a fraud, so I'm not happy about it!

 

However, the only reason we went this way is that somehow the signature was being used by rogues to sign virus laden installers, giving SimFlight a bad name. That's supposed to be prevented by the revocation. If SimFlight feel strongly enough about it I'm sure they'll chase GlobalSign about it -- that would happen if there were more accusations about malware.

 

 

, so I'm concerned that at some point it may stop working

 

...as of course it should have done weeks ago!

 

 

Regards

Pete

Link to comment
Share on other sites

I'm going to assume that this is a preferred thread to post in....

 

Clean install of FSX and Acceleration. Once FSUIPC 4.0 is installed, it all breaks down.

 

I have used the loader that is mentioned in other threads.

 

Here is all the information I can provide....

 

FSX, starts (spinner with the ultralight), hangs a few seconds later.

 

This was a "clean" install precipitated by the dreaded trust issue (precipitated by the installation of 4.90) that just would not go away no matter how many times I tried per Peter's instruction.  All previous FSX and addons were uninstalled with their uninstallers and the registry cleaned with CCleaner.

 

My paid registration can be confirmed by association with my forum account email.

 

 

 

The important line from the fsx.cfg... and this is the first and only change made, fresh cfg.

[Trusted]
E:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4_Loader.dll.klqaahzckecbzzcoubnihncklowttzqzqaizhkhb=1

********* FSUIPC4, Version 4.90 by Pete Dowson *********
Running inside FSX on Windows 7
Module base=54200000
User Name="<private information>"
User Addr="<private information>"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
      827 System time = 06/07/2013 11:27:34
      827 FLT path = "C:\Users\Paul\Documents\Flight Simulator X Files\"
      858 Trying to connect to SimConnect Acc/SP2 Oct07 ...
      873 FS path = "E:\Microsoft Games\Microsoft Flight Simulator X\"
Installer for FSUIPC4.DLL version 4.90

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
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"
Not there, so looking in:
     HKEY_CURRENT_USER\Prepar3D
     Parameter"AppPath"
... NOT found! ...
===========================================================

INSTALLATION FOR FSX:
SetupPath="E:\Microsoft Games\Microsoft Flight Simulator X\"
Checking version of 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:
       E:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL
... No previous valid version found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "E:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Paul\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\Paul\AppData\Roaming"
Found FSX.CFG in "C:\Users\Paul\AppData\Roaming\Microsoft\FSX\FSX.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
No previous FSUIPC4 entry found, so adding it now ...
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
"Modules\FSUIPC Documents" folder created 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 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 ***************

<?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>Object Placement Tool</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Traffic Toolbox</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\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>..\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_Loader.dll</Path>
  </Launch.Addon>
</SimBase.Document>

Log Name:      Application
Source:        Application Hang
Date:          7/6/2013 11:28:42 AM
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Paul-PC
Description:
The program fsx.exe version 10.0.61637.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: 179c
 Start Time: 01ce7a65a2588d36
 Termination Time: 24
 Application Path: E:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
 Report Id: 14d5d37a-e659-11e2-af61-50e5495458bd

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Hang" />
    <EventID Qualifiers="0">1002</EventID>
    <Level>2</Level>
    <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-07-06T16:28:42.000000000Z" />
    <EventRecordID>28776</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Paul-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61637.0</Data>
    <Data>179c</Data>
    <Data>01ce7a65a2588d36</Data>
    <Data>24</Data>
    <Data>E:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>
    <Data>14d5d37a-e659-11e2-af61-50e5495458bd</Data>
    <Binary>55006E006B006E006F0077006E0000000000</Binary>
  </EventData>
</Event>
Edited by lawndartleo
Link to comment
Share on other sites

 

I'm going to assume that this is a preferred thread to post in....

 

Well not really, because the thread title doesn't actually cover your subject. Why not start your own thread with a more appropriate title?

 

Clean install of FSX and Acceleration. Once FSUIPC 4.0 is installed, it all breaks down.

I have used the loader that is mentioned in other threads.

 

 

The "loader" is actually "mentioned" in the Installation document included in the ZIP. It is almost never useful. It was only ever provided as an "in case" provision, to avoid loading conflicts with other DLLs.  Did you try without the loader? Were the symptoms the same? If FSUIPC actually gets loaded (as can be checked by the existence of a new LOG file) then the loading has already been done so the loader would be irrelevant.

 

827 System time = 06/07/2013 11:27:34

827 FLT path = "C:\Users\Paul\Documents\Flight Simulator X Files\"

858 Trying to connect to SimConnect Acc/SP2 Oct07 ...

873 FS path = "E:\Microsoft Games\Microsoft Flight Simulator X\"

 

The only recent problems with a log which stopped there were due to a bad device installation, one for a "Razer Nostromo Keypad". The problem, an erroneous Registry entry, caused FSUIPC's joystick scan (only performed for registered users) to go into a loop. This was corrected in version 4.902.

 

Generally if you have a problem with FSUIPC (and it is actually running, as seen from a Log file), it is a good idea to see if there is an update. So, please go to the Download Links subforum and get the current interim update, 4.907, and see if that helps.

 

Oh, first, I'd try removing the Loader from the modules folder and re-running the 4.90 Installer so it fixes the DLL.XML file. THEN put the version 4.907 into the Modules folder.

 

Regards

Pete

Link to comment
Share on other sites

Hello,

 

Not long after posting, I ran across the 907 version.... I always get my "up to date" files from http://www.schiratti.com/dowson.html but just learned that page is not necessarily up to date.  My first inclination was to look for updates in the link at the top of this page (http://forum.simflight.com/files/) but 907 is not there so it was unknown to me.  A little more forum cruising and I found http://forum.simflight.com/topic/66139-updated-modules/ which was what I needed all along. 907 did the trick.

 

Odd that the Nostromo was causing problem as it works just fine.

 

Thanks!

Link to comment
Share on other sites

Not long after posting, I ran across the 907 version.... I always get my "up to date" files from http://www.schiratti.com/dowson.html but just learned that page is not necessarily up to date.  My first inclination was to look for updates in the link at the top of this page (http://forum.simflight.com/files/) but 907 is not there so it was unknown to me.  A little more forum cruising and I found http://forum.simflight.com/topic/66139-updated-modules/ which was what I needed all along. 907 did the trick.

 

The Schiratti page always provides a link to the current latest Install version. Between every complete re-issue (documentation etc etc) there are always many interim updates and those are ALWAYS hosted here, in the Download Links subforum, along with lots of other stuff.

 

Your second link above is direct to the relevant thread in the Download Links subforum, that's all. it would be a good idea for you to explore this Forum a little -- you never know, you might find other useful things.

 

Odd that the Nostromo was causing problem as it works just fine.

 

Yes. it's only its entries in the Registry which are non-standard and cause FSUIPC problems which I had to work around.

 

Pete

Link to comment
Share on other sites

Hello Pete,

 

I did generate a simconnect log, and it doesn't give any indication why it won't load fsuipc.dll, here is the relevant part of the log where you can see the other modules getting loaded, but no mention of fsuipc:

 

0.00000 SimConnect version 10.0.61259.0

0.02451 Server: Scope=local, Protocol=Auto, Address=::1, Port=51773, MaxClients=64
0.03219 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64
0.05451 Server: Scope=local, Protocol=IPv6, Address=::1, Port=51774, MaxClients=64
0.07887 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=51775, MaxClients=64

 
0.18377 Exe Launched:  Path="S:\Program Files (x86)\FSForce 2\FSForce.exe"  CommandLine="/FS"  Version="2.6.0.4"
0.21591 Exe Launched:  Path="C:\Program Files (x86)\EZCA\EZCA.exe"  CommandLine=""  Version="1.1.7.2"
0.23196 Exe Launched:  Path="s:\Program Files (x86)\SPAD\Spad.exe"  CommandLine=""  Version="0.5.0.1"
0.37469 Exe Launched:  Path="S:\Prepar3D\\Flight One Software\Ultimate Traffic 2\UT2Services.exe"  CommandLine=""  Version="2.1.0.0"
0.38057 Panels data export found and set to 20B319D8
0.38334 DLL Loaded:  Path="S:\Program Files (x86)\FSForce 2\FSForce.dll"  Version="2.6.0.4"
0.40081 Panels data export found and set to 20B319D8
0.44778 DLL Loaded:  Path="S:\Program Files (x86)\FS Recorder for FSX\FSRecorder_FSX.dll"  Version="2.1.0.0"
0.45456 Panels data export found and set to 20B319D8
0.45457 DLL Loaded:  Path="Modules\rxpGnsDriver.dll"  Version="1.6.0.1"
0.47013 Panels data export found and set to 20B319D8
0.53138 DLL Loaded:  Path="Modules\A2A_Feel.dll"  Version="<Unknown>"
0.54039 Panels data export found and set to 20B319D8
0.54256 DLL Loaded:  Path="Modules\AccuFeelMenu.dll"  Version="0.1.0.0"
0.55612 DLL Loaded:  Path="S:\Program Files (x86)\Squawkbox\sbtrans10.dll"  Version="<Unknown>"
0.56515 DLL Loaded:  Path="S:\Program Files (x86)\Squawkbox\sbaicontrol10.dll"  Version="<Unknown>"
0.59975 DLL Loaded:  Path="S:\Program Files (x86)\Squawkbox\sbmod10.dll"  Version="<Unknown>"
0.61786 DLL Loaded:  Path="S:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll"  Version="2.0.2.2773"
> 14.12127 [191, 1]Open: Version=0x00000004  Name="TrackIR SimConnect Interface"
> 14.12194 [64, 1]Open: Version=0x00000004  Name="FSForce DLL"
> 14.12196 [64, 2]SubscribeToSystemEvent:EventID=0, SystemEventName="SimStart"
> 14.12196 [65, 1]Open: Version=0x00000004  Name="FS Force"
> 14.12198 [65, 2]RequestSystemState:RequestID=0, szState="Sim"
> 14.12199 [65, 3]SubscribeToSystemEvent:EventID=0, SystemEventName="SimStart"
> 14.12200 [190, 1]Open: Version=0x00000002  Name="FS Recorder"
> 14.12213 [66, 1]Open: Version=0x00000004  Name="A2A Feel"

 

 

Given that you can't support older versions, and that you are expecting (indeed hoping) for 4.86 and older to stop working in the near future, I really hope we can get to the bottom of this.

 

As you said, it's as if it's not even in DLL.XML and not looked for, however I can be 100% certain the dll.xml is correctly formatted, since if I just change the module to 4.86 (without making any changes to dll.xml or anything else) it loads, but change it back to 4.90 or 4.907 and it doesn't.

 

Is there any point in me sending you a complete simconnect log (not just the excerpt) in case I've missed something? I can do so via PM or email if you like, as it'd be rather long and I'd prefer not to clutter up the forum with it, unless that is what you'd prefer.

 

Alternatively, I wonder if it's worth trying (if it's convenient for you to build one) one of the following

 

a. A 4.86 dll, exactly as I have working now, but unsigned, to see if that loads.

 

b. A 4.86 dll with the only change being that the signature checking is commented out or removed before compiling, to see if that specific change is what's causing it, or whether it could be something else.

 

Thanks

Link to comment
Share on other sites

I did generate a simconnect log, and it doesn't give any indication why it won't load fsuipc.dll, here is the relevant part of the log where you can see the other modules getting loaded, but no mention of fsuipc:

 

Well, there just MUST be something wrong with that DLL.XML which I cannot see. And if that were the case itcouldn't load 4.86 either, so it makes no sense at all.

 

I suppose you could, as an experiment try renaming the DLL.XML and re-running the FSUIPC 4.90 installer, so it makes a fresh DLL.XML with just FSUIPC4.DLL present, but because of the 4.86 loading I can't see that being different.

 

When you said "I did try deleting the trust line in fsx.cfg,", did you delete ALL of the [Trust] section or only one line? At least delete all of the lines mentioning FSUIPC4.

 

The only other thing I can think is that the DLL is being 'guarded' by some virus checker somewhere, somehow. You are SURE that the DLL does actually get properly installed into the right Modules folder?

 

Regards

Pete

Link to comment
Share on other sites

Well this is utterly bizarre.

 

Your comment about removing the whole trusted section from fsx.cfg was what led me to a solution, but I'm as mystified now as to what is going on as I ever was before.

 

After removing the whole trusted section, and running fsx, I got asked about absolutely nothing, despite having lots of stuff in my dll.xml as you can see above. So I looked in fsx.cfg, and found that a number of modules had been added to the [trusted] section.

 

Among them, FSUIPC, in the line:

 

S:\fsx\Modules\FSUIPC4.dll.rooctoroqihwhtikitinolctiqihrnaqeqkbqcor=-1

 

Now I'd never really thought before about what the numbers at the end of these lines mean, as of course fsx just adds them and you never need to edit them.

 

But I figured -1 might indicate untrusted and a bit of googling seemed to confirm this, so I changed it to =1, saved the file and restarted fsx, and now fsuipc loads correctly.

 

A fair bit of googling doesn't seem to reveal any documentation on the meaning of these numbers. After deleting the whole trusted section and letting fsx recreate it, I have entries with both -2 and -1 at the end (but none with 1 or 2). So it seems that when fsx sees a module it hasn't seen before, it's automatically marking it as untrusted. Of course I can now easily work around this by just changing the sign of the entry whenever I need to add a new module.

 

Can anyone enlighten me on what -1/-2/1/2 mean at the end of the lines (ie. where should a 2 rather than a 1 be used).

 

Also, perhaps someone can point me in the right direction as to why my fsx is automatically adding everything as untrusted without asking me. Perhaps I have a rare and ridiculous setting that's causing this.

 

It may be worth mentioning that I also have Prepar3d installed - I don't think it can have anything to do with it, but it does occur to me that there is no [trusted] section in prepar3d.cfg and prepar3d seems to just trust everything by default, so is it possible that prepar3d has overwriten some dll or something so that the normal fsx behaviour of asking whether to trust modules or not has been disabled???

Link to comment
Share on other sites

Follow up, leaving the above intact for documentation - a bit more googling and I found the problem.

 

http://forum.avsim.net/topic/321790-trusted-section-weirdness/ refers to someone who had the exact same problem - fsx not asking whether to trust modules or not, and automatically marking them as untrusted.

 

http://lkalamaras.blogspot.com/2007/06/was-this-for-our-own-good.html has the solution, which is to change the value of HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\State back to it's default value of 0x23c00 (something??? had set it to 0x63c00 which changes some kind of trust policy in Windows, causing the problem).

 

Maybe this will help someone else out some time - I feel rather fortunate I found the solution this quickly, as I suspect this is one of those problems that could have someone tearing their hair out for weeks.

Link to comment
Share on other sites

Follow up, leaving the above intact for documentation - a bit more googling and I found the problem.

 

http://forum.avsim.net/topic/321790-trusted-section-weirdness/ refers to someone who had the exact same problem - fsx not asking whether to trust modules or not, and automatically marking them as untrusted.

 

http://lkalamaras.blogspot.com/2007/06/was-this-for-our-own-good.html has the solution, which is to change the value of HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\State back to it's default value of 0x23c00 (something??? had set it to 0x63c00 which changes some kind of trust policy in Windows, causing the problem).

 

Maybe this will help someone else out some time - I feel rather fortunate I found the solution this quickly, as I suspect this is one of those problems that could have someone tearing their hair out for weeks.

 

 

That's certainly something I didn't know about! And it should definitely be kept as reference for others. Could I ask you to please create a suitable thread with the problem and solution in the FAQ subforum for me? I think it is best coming drectly from the discoverer. When it is posted I will lock it so it stays among the top help threads.

 

Thank you!

 

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.