Problems with FSUIPC 4.948g

[misterADIdas11]

Hey,

I've done some updates to the FSDT Addon Manager and FSUIPC and since then nothing is working anymore.

I can only get access to the Flightsim if I disable FSUIPC or the bglmanx.dll.

And even when I disable FSUIPC I get the famous message if I really really want to run FSUIPC.

In combination with bglmanx.dll it brings FSX to crash.

 

Anything you can do here?

 

Greets,

Adrian

[Pete Dowson]

I sometimes got trouble with BGLMANX.DLL. I think you might try changing the order of loading in the DLL.XML. I've had it clash with other DLL modules too, not just FSUIPC. You could also try re-running the AddOn manager after removing BGLMANX from the DLL.XML file.

 

I think it's something to do with the problem SimConnect has always had loading modules. I think you'll find that FSUIPC itself is not even getting to run, so there's no code I can change to help at all.

 

Pete

[misterADIdas11]

So what should I do?

 

This is my 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>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>D:\Flight X\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.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>LHBP_objectPlacer.dll</Name>
    <Disabled>False</Disabled>
    <Path>Modules\LHBP_objectPlacer.dll</Path>
    <Commandline />
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow_EDCG.dll</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Flight X\ORBX\FTX_GLOBAL\FTX_AA_EDCG\Scenery\ObjectFlow_EDCG.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Objectflow_EDBH.dll</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Flight X\ORBX\FTX_GLOBAL\FTX_AA_EDBH\Scenery\Objectflow_EDBH.dll</Path>
  </Launch.Addon>
  <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>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>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>
    <ManualLoad>False</ManualLoad>
    <Path>.\RAASPRO\RAASPRO.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </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>VistaMare Core</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Flight X\VistaMare\ViMaCoreX.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG Options</Name>
    <Disabled>False</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>IvAp</Name>
    <Disabled>False</Disabled>
    <Path>C:\IVAO\ivap_fsx_bootstrap.dll</Path>
    <Commandline />
  </Launch.Addon>
  <Launch.Addon>
    <Name>FS Recorder</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>C:\Program Files (x86)\FSrecorder\FSRecorder_FSX.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>VAInterface</Name>
    <Disabled>False</Disabled>
    <Path>Modules\VAInterface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>SODE DLL</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Flight X\SODE\SimObjectAnimationModule.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4_Loader.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>as_connect</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp.dll</Path>
  </Launch.Addon>
</SimBase.Document>
 

[misterADIdas11]

I'm getting a StackHash_0a9e, by the way.

Edited December 18, 2015 by misterADIdas11

[Pete Dowson]

So what should I do?

 

This is my dll.xml:

 

Try moving the BGLMANX.DLL entry to the end. i.e.this:

 

 <Launch.Addon>

    <Name>Addon Manager</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>bglmanx.dll</Path>

  </Launch.Addon>

 

to just before this:

 

</SimBase.Document>

 

I see you have PMDG Options loading too. That often gave me grief too, but I don't use any PMDG add-ons now.

 

BTW I don't think any of these problems can occur in P3D, because they removed that awful buggy trust checking system which FSX uses and which all happens BEFORE the FSUIPC module is even loaded!

 

Pete

[Pete Dowson]

I'm getting a StackHash_0a9e, by the way.

 

Yes, that's what I get. That just means a memory corruption affecting the stack of the process. What module is identified?

 

Pete

[misterADIdas11]

No module is actually identififed.

The eventviewer just states "StackHash_0a9e"

 

Fehlerbucket , Typ 0
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: fsx.exe
P2: 10.0.61472.0
P3: 475e17d3
P4: StackHash_0a9e
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: ffb80156
P9:
P10:
 

[misterADIdas11]

Now I am getting following message:

 

The procedure entry point SimConnect_Text could not be located in the dynamic link library Simconnect.dll

[Pete Dowson]

Now I am getting following message:

 

The procedure entry point SimConnect_Text could not be located in the dynamic link library Simconnect.dll

 

From what? i.e. what program, exactly, gives such a message, and when? There's no such message in FSUIPC for sure, and FSUIPC is not dependent upon that function -- it uses it if it can, but doesn't really care if it isn't there.

 

However, "SimConnect_Text" is a standard part of SimConnect, so if your SimConnect.DLL installation has it missing then it seems your FS installation is corrupted. Maybe this is why you are getting problems? Maybe you need to re-install. First I expect you could try installing just the SimConnect's (at least the SP1 and SP2 versions would be needed by most add-ons).

 

Pete

[misterADIdas11]

It comes when the Sim is asking me to activate the bglmanx.dll.

On Thursdays everything was working fine...

[Pete Dowson]

It comes when the Sim is asking me to activate the bglmanx.dll.

On Thursdays everything was working fine...

 

So, is it from BGLMANX.DLL? Maybe you need to check with Virtuali support?

 

Another thing comes to mind. Many reports of "stackhash" errors seem to identify overclocking or other hardware problems as a typical cause. Maybe something in the hardware is starting to fail. Certainly memory corruption is the cause of "stackhash" errors and could certainly also result in very strange errors like your missing Simconnect function one. 

 

Whether memory corruption is caused by software going wrong or by hardware is a difficult one to determine, but certainly something to investigate.

 

Pete

[misterADIdas11]

But from one on the other day?

That's weird...

On Thursday everything was working fine, then I saw that FSUIPC and the Addon Manager needs an Update, applied those and BAM.

Everything crashed.

 

I don't want to reinstall the FSX over Christmas :cry:

[misterADIdas11]

Two new things I discovered:

 

When I deactivate the bglmanx.dll and active the FSUIPC only beside my other addons: FSX is running.

When I deactivate the FSUIPC.dll and activate the bglmanx.dll only beside my other addons: FSX is running.

When both are activated:

 

1. The procedure entry point SimConnect _Text could not be located in Dynamic Link Library SimConnect.dll after I activate the bglmanx.dll

or

2. FSUIPC causes FSX to crash.

or

3. bglmanx.dll causes FSX to crash.

 

[Pete Dowson]

But from one on the other day?

That's weird...

On Thursday everything was working fine, then I saw that FSUIPC and the Addon Manager needs an Update, applied those and BAM.

Everything crashed.

 

I don't want to reinstall the FSX over Christmas :cry:

 

Well, the fact that things have changed ON THEIR OWN as well is certainly starting to point to corruption and possibly hardware problems. Sorry, but there it is, and I've really given you all the advice I can.

 

Check with Virtuali support about BGLMANX errors reporting SimConnect. I've never heard of that one. ALL SimConnect.DLL modules contain the export "SimConnect_Text" so I definitely think that's a corruption in your system, and changed since before this latest report of yours.

 

Pete

[virtuali]

Check with Virtuali support about BGLMANX errors reporting SimConnect. I've never heard of that one. ALL SimConnect.DLL modules contain the export "SimConnect_Text" so I definitely think that's a corruption in your system, and changed since before this latest report of yours.

 

Pete

 

Hi Pete,

 

Simconnect_text() has been added to Simconnect only starting with version 61242 ( SP1 ), it's not included in 60905 (RTM) so, the two most likely causes of these issues are:

 

- Both the SP1 and the SP2 versions are not properly installed or are gone corrupted for some reason.

 

OR

 

- The Side-by-side loading system has got a problem and, instead of allowing two processes to load two different .DLLs in the same memory space (which is what it's supposed to do WHEN IT WORKS), has loaded the FSX RTM Simconnect because another module requested it, and is stuck with it.

 

Bglmanx.dll, of course, is just the victim of this, since it NEEDS SImconnect_text() so, it cannot proceed without it. In fact, the error message about the missing entry point is not even coming from it, but from Windows itself.

[Pete Dowson]

Hi Pete,

 

Simconnect_text() has been added to Simconnect only starting with version 61242 ( SP1 ), it's not included in 60905 (RTM) 

 

Ah, my bad, didn't realise that. Thanks Umberto!

 

Pete