FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: edwardpat on September 07, 2015, 03:50:17 am
-
Hi, Umberto:
Some weeks ago we exchange ideas on this forum regarding the interferences of the EMT with the bglmanx.dll module. I still get P3Dv2.5 hangs-up during P3D startup sequence even with the EMT disabled (and bglmanx.dll in the main P3D directory, as it should). Do you think that changing the order the respective modules are loaded inside the DLL.xml could help resolve the interference?. Here is my DLL.xml file:
<?xml version="1.0"?>
<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>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>
I have not tried changing the order (like loading the EMT *after* loading the FSDT Addon Manager), and before doing it, would like to know your opinion.
King regards,
Edward
-
Do you think that changing the order the respective modules are loaded inside the DLL.xml could help resolve the interference?.
It has fixed a lot of issues for many users here:
http://www.fsdreamteam.com/forum/index.php/topic,12418.msg94305.html#msg94305