BGLMANX.DLL Module causes hangs-up of P3Dv2.5 during start-up

[edwardpat]

Hi, Umberto:

I installed the latest GSX version using the new installer. I think something should be wrong with the new version of the bglmanx.dll file, since after using the new GSX version, P3Dv2.5 constantly hangs during the start-up sequence. The only way to avoid it is to take out the bglmanx.dll file from the main P3D folder, and when I do that P3Dv2.5 starts completely normal 100% of the time.

I think I'm not the only one with this type of problem (I saw the post from Peter Downson and he found an issue with another module from UT2 which I don't have that was apparently conflicting with the bglmanx.dll module). I used to believe that the Estonian Migration Tool was causing the trouble, but I completely uninstalled it, and the hang-ups are still present.

I'm attaching my DLL.xml file to check with you if there is something wrong with it, but it seems not, because at least the addon manager is loading in first order (and as you can see there is no Migration Tool anymore) and do not have any indication to make me think there is something wrong with any other module except bglmanx.dll itself:

<?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_KSFF_P3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_AA_KSFF\Scenery\ObjectFlow_KSFF_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow_CYSE_P3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_AA_CYSE\scenery\ObjectFlow_CYSE_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v2\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
  </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>CMeteoXml</Name>
    <Disabled>False</Disabled>
    <Path>.\CMeteoXml.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>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>

Please help, because I feel something is not right here.

Best regards,

Edward

[edwardpat]

Hi, I'm also attaching, in case is helpful, my EXE.xml file:

<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>exe.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>Couatl</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>fsdreamteam\couatl\couatl.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>as_btstrp_config_manager</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp_config_manager.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>SODE</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v2\SODE\SimObjectDisplayEngine.exe</Path>
  </Launch.Addon>
</SimBase.Document>

Thanks for your help,

Edward

[Pete Dowson]

Hi, I'm also attaching, in case is helpful, my EXE.xml file:
...
  <Launch.Addon>
    <Name>as_btstrp_config_manager</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp_config_manager.exe</Path>
  </Launch.Addon>

I have this disabled -- always have. It isn't really needed to use ASN. Try changing Disabled to True.

 <Launch.Addon>
    <Name>SODE</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v2\SODE\SimObjectDisplayEngine.exe</Path>
  </Launch.Addon>
</SimBase.Document>

I have this loading okay, but you could try, as a test, disabling it too. But do it only with the ASN one first.

Maybe I should test with my ASN one re-enabled.

Regards
Pete

[edwardpat]

Hi, Pete:
Thanks for your suggestions.
The first one, concerning disabling the ASN part of the EXE.xml seems to work well for me!!!. I was succesful in trying to start P3D three times (with the bglmanx.dll file inside P3D, of course, as it should), and everything was OK. Will do more testing tomorrow/Sunday after restart of my PC, etc., and will report back.
AS A SIDE NOTE, and this should be addressed directly to FSDT (and probably you should check yours too), is that when I open the AddonManager window (new version downloaded and installed using the most recent GSX installer) inside the P3D main menu it says that I have San Francisco HD installed in TRIAL mode and is OUTDATED (?). That is quite strange, since I don't have anything related to San Francisco HD installed in any way (I think is still in development by FlightBeam, who also uses these things of couatl.exe and bglmanx.dll). So, in my opinion the new version of the bglmanx.dll is in some way buggy and should be revised by FSDT.
In conclusion so far, appart from the previous note about SF, the first test you mentioned with the ASN part seems to be in the right direction!. As I said before, I'll do some more testing tomorrow and on sunday. I have not touched anything related to the other module (SODE) yet, as you suggested.
Thanks again and best regards,
Edward

[edwardpat]

Hi, Pete:
As per your suggestion, after "deleting" (changing Disabled to True) the entry for the ASN module in the EXE.xml, and after several tests, I can now confirm that the conflict with bglmanx.dll is solved (on my system, too). FSDT also changed the data file that caused a misidentification of the upcoming (in hours I guess) KSFO HD scenery, so no more strange messages about this scenery within the simulator.
Thanks again for your help.
Edward