Static Objects missing in some Orbx airports after GSX install

General Category > General Discussion

<< < (2/3) > >>

virtuali:

--- Quote from: LFigueiredo on February 19, 2016, 02:14:04 pm ---I remember that, during my GSX installation, the installer informed me that it would change the location of dll.xml to User/MyName/APPdata/Roaming/LockheedMartin/P3DV2. Could i move it back, just like below?
--- End quote ---

No, the installer won't try to change the location, nor it would warned you it will do that.

It probably informed you that it was going to create a new (correct and blank) DLL.XML in THAT location, but it didn't said anything about "changing THE location". It surely changed the file itself, but it would never try to change its default location.

All our installers always use the %APPDATA% folder (and this is in compliance of Microsoft recommendations that small configuration files should be by-user and placed into that folder), and will not, by default, use any other location or change it.

Prepar3D now supports BOTH locations: %APPDATA% and %PROGRAMDATA%.

BOTH files will be read (with the one under %PROGRAMDATA% read first) and the modules referenced there will all internally "merged" into a single list, so all modules will be called, regardless from which file they came from.

The suggestion to move the bglmanx.dll lines from the DLL.XML in %APPDATA% to the one into %PROGRAMDATA%, is just a TRICK to ensure that bglmanx.dll is read BEFORE most of the other 3rd party modules.

And the reason to have it loaded first, is to prevent other 3rd party modules that uses older Simconnect version, to "lock" the sim to that one, preventing other modules loaded after them to use the newest, which is required by our modules and many others, like PMDG.

LFigueiredo:
Hi Umberto

You are correct, there is a dll.xml file that was saved before GSX installation. I replaced the current dll.xml file to the "old" one, not only in the APPDATA directory but also in the ProgramData direcory (Both at the P3D V2 folders). Anyway, the Orbx airports are the same, even when I try to reinstall them. I would like to try the trick you mentioned:

" The suggestion to move the bglmanx.dll lines from the DLL.XML in %APPDATA% to the one into %PROGRAMDATA%, is just a TRICK to ensure that bglmanx.dll is read BEFORE most of the other 3rd party modules."

How do I do that? I am not so confortable about changing/editing files, so please try to make it very easy, like Step 1 .do this, Step 2. do that and so on...

LFigueiredo:
Anyway, this is how my dll.xml files look now:

<?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>
</SimBase.Document>

And this is how they looked before a recente new airplane addon, a Twin Other:

<?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>iFly 747-400 Menu</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\iFly744.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>ObjectFlow_EGPB_P3D</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ORBX\FTX_EU\FTX_AA_EGPB\scenery\ObjectFlow_EGPB_P3D.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>ObjectFlow_05S_P3D</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_AA_05S\scenery\ObjectFlow_05S_P3D.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>ObjectFlow_11S_P3D</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_AA_11S\scenery\ObjectFlow_11S_P3D.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>ObjectFlow_KMRY_P3D</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_AA_KMRY\scenery\ObjectFlow_KMRY_P3D.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>ObjectFlow_CYSE_P3D</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\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>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
</Launch.Addon>

<Launch.Addon>
<Name>CMeteoXml</Name>
<Disabled>False</Disabled>
<Path>.\CMeteoXml.dll</Path>
</Launch.Addon>

<Launch.Addon>
<Name>Carenavigraph</Name>
<Disabled>False</Disabled>
<Path>.\Carenavigraph.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>
</SimBase.Document>

Luiz

virtuali:
If I understood your message correct, you just posted how the file looks like NOW (empty) and how it looked like *before* installing a new airplane. However, you don't say which one is (%PROGRAMDATA% or %APPDATA%), and/or if you have another one in the other location, and its content.

Your first DLL.XML file is EMPTY (no <Launch.Addon> sections, just the header), so it's normal that NOTHING will be loaded from *that* file.

The other version looks normal. If the other modules loaded from there are working, and just Orbx don't, that doesn't seem to be a problem related to those modules which I'm afraid I cannot help much with.

I'm not even exactly sure of your current situation:

- Have you been able to have GSX working, by having the bglmanx.dll lines in the DLL.XML located under %PROGRAMDATA%, and nothing else in that file ?

If yes then you can be reasonably sure the correct Simconnect is being used, and what happens with other modules is something you must sort it out between them.

LFigueiredo:
Hi Umberto,

I have the same files at both places( Users/MyName/App data/Roaming/Lockheed Martin/P3d V2 and Program Data(x86)/Lockheed Martin/P3dV2). I tried to change my dll.xml files to different configurations, and i suppose now that my problem does not have anything to do with it. My P3D is working just the same, regardless how different my dll.xml files are. This is why i am curious about other files that may be the cause of the issue. Regarding the bglmanx.dll file, it is also located in both places, but i didn´t touch it yet.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version