Static Objects missing in some Orbx airports after GSX install

General Category > General Discussion

<< < (3/3)

virtuali:

--- Quote from: LFigueiredo on February 21, 2016, 01:54:19 am ---I have the same files at both places( Users/MyName/App data/Roaming/Lockheed Martin/P3d V2 and Program Data(x86)/Lockheed Martin/P3dV2).
--- End quote ---

That's not right. Not sure it will create issues, but it might, and it's best (and less confusing), if you don't have any duplicates. And, if the problem IS caused by another 3rd party module that is causing OrbX modules to fail, because of the loading order, by copying the SAME file in both places, you simply duplicated the error in the fist file.

As I've said, the only reason to have bglmanx.dll (or any other module that loads the CORRECT Simconnect, which is the one we use) in the DLL.XML under %PROGRAMDATA%, is a way to be sure that no OTHER module will force the sim to load an OUTDATED version, by loading first.

So, as I've said, you must have ONLY the bglmanx.dll lines in the file under %PROGRAMDATA%, and everything else in the file under %APPDATA%

If I understand you current situation, it should be enough to remove all the other modules sections from the DLL.XML in %PROGRAMDATA% (leaving JUST the bglmanx.dll section), and remove the bglmanx.dll section from the DLL.XML in %APPDATA%

With "section", I mean the lines belonging to a specific module, starting from <Launch.Addon> to the next </Launch.Addon>

Don't remove the file header, of course...

LFigueiredo:
Ok, let me see if I got it right:

1. I left a complete dll.xml file in the APPDATA. It was sent to me by Mr. Dave Cooper, from Orbx.
2. I deleted bglmanx.dll from APPData. It is located only in ProgramData now.

What i don´t understand is why bglmanx.dll looks to be a new version, since it is shown as of 2016/02/13, the day i installed GSX. I could not open it, and when i try to attach it to you i am not allowed as well. Could you send me a bglmanx.dll file for me to test? I may have a problem in this file...

LFigueiredo:

This is how my dll.xml file looks now. It is located in APPDATA/MyName/Roaming/LockheedMartin/P3DV2 folder:

<?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>ObjectFlow_YWOL_P3D</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ORBX\FTX_AU\FTXAA_YWOL\scenery\ObjectFlow_YWOL_P3D.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>ObjectFlow_YMML_P3D</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ORBX\FTX_AU\FTXAA_YMML\Scenery\ObjectFlow_YMML_P3D.dll</Path>
</Launch.Addon>
<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_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_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>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.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>
<Launch.Addon>
<Name>Flight Recorder</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
</Launch.Addon>
</SimBase.Document>

virtuali:

--- Quote from: LFigueiredo on February 21, 2016, 01:07:55 pm ---1. I left a complete dll.xml file in the APPDATA. It was sent to me by Mr. Dave Cooper, from Orbx.
--- End quote ---

Ok

--- Quote ---2. I deleted bglmanx.dll from APPData. It is located only in ProgramData now.
--- End quote ---

Yes, if you mean "delete the section in the DLL.XML under %APPDATA% which references bglmanx.dll, and leave it as the ONLY module in the DLL.XML located under %PROGRAMDATA%"

--- Quote ---What i don´t understand is why bglmanx.dll looks to be a new version, since it is shown as of 2016/02/13, the day i installed GSX.
--- End quote ---

There hasn't been a new version in a while. That file date you are looking at, is misleading, since it's the date you installed in your system, not the date we created it.

The bglmanx.dll file ITSLEF, is NOT a problem. Don't waste your time looking at it. The problem is ANOTHER addon using an OUTDATED Simconnect, which is likely affecting both OrbX and PMDG. Which is why, I explained a possible solution.

Loading bglmanx.dll first will be a "fixer" solution for a problem caused by other modules, which never happened, if other developers stopped compiling their modules using outdated Simconnect, especially under P3D, where they are guaranteed all the features of the latest one for FSX are available so, there's no "backward compatibility for FSX RTM and SP1 users" explanation.

LFigueiredo:
Thanks for the explanation. What i have learned from this situation is the following:

1. Having to deal with installation issues/compatibility issues in Fligh Simulation in general is something that makes me very concerned about installing something new from now on. I never know if a new airplane/scenery/tool will affect the sim itself and the other addons already installed. This leads me to the second conclusion:
2. I don´t intend to buy many addons from diferent sources anymore. I will keep my P3D with as few as possible changes in the future.
3. I will buy V3.1 from LM and have it side by side with my existing V2.5. I will install the addons first(Rex, GSX, VFX, etc), then the airplanes and finally my scenery. I will think twice before buying another addon, because it is very boring, frustating and time-intensive to be solving issues instead of flying and enjoying our hobby.
4. Lockheed Martin should think seriously about having a more complete plattform that could include the most popular addons available. I would rather buy a P3.1 for 1,000 dollars instead of having to buy and install all those products again. Time is money, and mine is very valuable.

Cheers,

Luiz

Navigation

[0] Message Index

[*] Previous page

Go to full version