FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: FrozenMalibu on January 04, 2016, 08:42:49 pm
-
Hey there!
First of all I would like to thank you for activating my account here. I am interested in GSX for P3D V3.1 and downloaded it for testing at the free airports. Starting P3D after the installation shows me this error:
http://fs5.directupload.net/images/160104/foz3nja7.png (http://fs5.directupload.net/images/160104/foz3nja7.png)
After pressing OK P3D is closing. Installation and starting P3D was done with admin rights.
I started searching for errors like this in your forum and found a way to deal with that error but at FSX.
It was changing the order of launching addons in the dll.xml. Checking this showed me that the order is correct:
http://fs5.directupload.net/images/160104/y5gkzkm9.png (http://fs5.directupload.net/images/160104/y5gkzkm9.png)
At searching for the folder I found this two folders which seem to got installed by your installationsoftware. This caused amazement because I never had P3D v2 installed... ???
http://fs5.directupload.net/images/160104/fbun7k93.png (http://fs5.directupload.net/images/160104/fbun7k93.png)
A repair installation did not help. I hope that the amount of information is enough and can help you at finding a solution.
-
I started searching for errors like this in your forum and found a way to deal with that error but at FSX.
This thread refers to P3D:
http://www.fsdreamteam.com/forum/index.php/topic,10489.msg97548.html#msg97548
The cause it's the same: another addon that uses an outdated Simconnect library (one that was made for FSX RTM or FSX SP1), has forced the sim to load that outdated version instead of the correct one (FSX SP2), used by our modules and many others too.
-
Thanks for the answer!
-SP2 SimConnect is installed
-The dll.xml order is correct and
-the addons from the list I use are PMDG and FSUIPC which shouldn't cause the problem
What about Active Sky Next? Does this affect to SimConnect?
-
What about Active Sky Next? Does this affect to SimConnect?
No idea, since I don't have it so I couldn't test it in the thread I linked in the other post. However, one fact is clear:
SOMETHING is calling an outdated FSX Simconnect, and the sim is stuck with it, there's no question about it.
The SimConnect_text() API call is included ONLY in the FSX SP1 and SP2 versions, and it wasn't in the RTM version so, if it cannot be found, it can only happen because the sim has loaded an older version under request from another module that requires it.
Of course, another possible explanation is that the FSX SP2 version has been installed, but it has gone missing/corrupt, which sometimes happens. In this case, you might try to reinstall it this way:
- Boot Windows in Safe Mode
- Go into your Windows\WinSxS folder and delete the simconnect 10.0.61259.0 folder.
- Reboot Windows
- Reinstall the Simconnect client from here:
\Lockheed Martin\Prepar3D v2\redist\Interface\FSX-SP2-XPACK\retail\lib\Simconnect.MSI
-
I am having the same exact issue today, however I am running P3D 3.0 and my sim was running fine this morning for hours, but when I launched it again this evening those errors appeared.
Following the advice posted, I've booted into safe mode, removed the simconnect folder mentioned, reinstalled from the P3D redist folder and still having issues.
Now when I launch P3D, none of my addons (FSDT, EZdok, vPilot) are loading in the sim, I only see FSUIPC in the addons menu.
Please help.
-
Now when I launch P3D, none of my addons (FSDT, EZdok, vPilot) are loading in the sim, I only see FSUIPC in the addons menu.
That clearly indicates you have a problem with Simconnect that is not related in any way to FSDT, since other modules are also affected by it. FSUIPC loads whatever Simconnect version is available dynamically.
Since we require the FSX SP2 version, we rely on it being installed properly and, it seems the same problem affects your other addons too, which probably also require the FSX SP2 version of Simconnect.
Note that, the FSX SP2 version of Simconnect also has a dependency from the Visual Studio 2005 runtime library, so it's possible your issue might be fixed by uninstalling and reinstalling them, as explained here:
http://www.fsdreamteam.com/forum/index.php/topic,9908.msg78015.html#msg78015
-
Now when I launch P3D, none of my addons (FSDT, EZdok, vPilot) are loading in the sim, I only see FSUIPC in the addons menu.
That clearly indicates you have a problem with Simconnect that is not related in any way to FSDT, since other modules are also affected by it. FSUIPC loads whatever Simconnect version is available dynamically.
Since we require the FSX SP2 version, we rely on it being installed properly and, it seems the same problem affects your other addons too, which probably also require the FSX SP2 version of Simconnect.
Note that, the FSX SP2 version of Simconnect also has a dependency from the Visual Studio 2005 runtime library, so it's possible your issue might be fixed by uninstalling and reinstalling them, as explained here:
http://www.fsdreamteam.com/forum/index.php/topic,9908.msg78015.html#msg78015
Thanks for the reply. Just to clarify, I wasn't having issues with any other addons, only the FSDT related ones initially getting the Simconnect_Text error, only later did almost all of the addons get affected once I followed the instructions you gave about removing the installed SimConnect files and removing the directories under the \WinSxS folders within Safe Mode. Once I did that reinstalled the SimConnect files again per your instructions is when all hell broke lose with everything else being affected.
I am not getting the SimConnect_Text error anymore, but none of the addons are working and I get a popup stating: Couatl.exe - The application was unable to start correctly (0xc0150004). Click OK to close the application" when I start P3D.
-
Now when I launch P3D, none of my addons (FSDT, EZdok, vPilot) are loading in the sim, I only see FSUIPC in the addons menu.
That clearly indicates you have a problem with Simconnect that is not related in any way to FSDT, since other modules are also affected by it. FSUIPC loads whatever Simconnect version is available dynamically.
Since we require the FSX SP2 version, we rely on it being installed properly and, it seems the same problem affects your other addons too, which probably also require the FSX SP2 version of Simconnect.
Note that, the FSX SP2 version of Simconnect also has a dependency from the Visual Studio 2005 runtime library, so it's possible your issue might be fixed by uninstalling and reinstalling them, as explained here:
http://www.fsdreamteam.com/forum/index.php/topic,9908.msg78015.html#msg78015
Thanks for the reply. Just to clarify, I wasn't having issues with any other addons, only the FSDT related ones initially getting the Simconnect_Text error, only later did almost all of the addons get affected once I followed the instructions you gave about removing the installed SimConnect files and removing the directories under the \WinSxS folders within Safe Mode. Once I did that reinstalled the SimConnect files again per your instructions is when all hell broke lose with everything else being affected.
I am not getting the SimConnect_Text error anymore, but none of the addons are working and I get a popup stating: Couatl.exe - The application was unable to start correctly (0xc0150004). Click OK to close the application" when I start P3D.
At much more troubleshooting, I noticed that when installing the Simconnect files from under the P3D installation folder, the simconnect.dll files were not being placed under the WinSxS folder structure. I tried several different sources of the Simconnect installation files, but none of them would install under WinSxS. I finally resorted to pulling out my FSX installation DVDs and installed FSX. That did the trick to get the Simconnect files installed under WinSxS.
But now I am back to the error of bglmanx.dll with "the procedure entry point SimConnect_Text could not be located in the dynamic link library simconnect.dll".
Any suggestions now?
-
once I followed the instructions you gave about removing the installed SimConnect files and removing the directories under the \WinSxS folders within Safe Mode. Once I did that reinstalled the SimConnect files again per your instructions is when all hell broke lose with everything else being affected.
If you removed all Simconnect, you must reinstall ALL of them, not just the SP2 version!
-
once I followed the instructions you gave about removing the installed SimConnect files and removing the directories under the \WinSxS folders within Safe Mode. Once I did that reinstalled the SimConnect files again per your instructions is when all hell broke lose with everything else being affected.
If you removed all Simconnect, you must reinstall ALL of them, not just the SP2 version!
Which I DID. I was showing only the ESP version of Simconnect in the WinSxS folder, things still didn't work so I got that one out as well. Re-Installed P3Dv3, which put that one back. The others like I said had to be installed from sources other than the P3D folder, because those installers would never put the files into the WinSxS folders.
If I remove the bglmanx.dll loading section from the dll.xml file, P3D starts up just fine without errors, however none of the addons show up.
-
I found someone who fixed the problem with deleting the encoding="windows-1252"? from the dll.xml
The solution was that P3D was starting succesfully but AddonManager didn't show up in the Addon tab. Can someone confirm this? Is this because of the trial version or is the solution just bad?
-
I found someone who fixed the problem with deleting the encoding="windows-1252"? from the dll.xml
The solution was that P3D was starting succesfully but AddonManager didn't show up in the Addon tab. Can someone confirm this? Is this because of the trial version or is the solution just bad?
That does nothing to fix the error with the bglmanx.dll file loading with P3D unfortunately.
-
That does nothing to fix the error with the bglmanx.dll file loading with P3D unfortunately.
Of course it doesn't, because that problem with XML encoding (which was caused by an outdated version of Active Sky Next), would prevent the sim from even *attempting* loading the .DLL, so it will just not load, but with no error message.
Instead, your problem, is that the OLDER FSX Simconnect (the RTM version) is correctly installed, but the latest ones are not.
The Simconnect RTM version is the only one that doesn't contain the Simconnect_text API call. The SP1 and the SP2/Xpack version contains that function (which is REQUIRED by the Addon Manager) so, I can only repeat and confirm the reason for this error is that the FSX Simconnect SP2/Xpack version is not installed correctly in your system.
Also, re-read my previous replies about the VC++ 2005 SP1 runtimes missing. They are also required by the FSX Simconnect SP2 client.
-
That does nothing to fix the error with the bglmanx.dll file loading with P3D unfortunately.
Of course it doesn't, because that problem with XML encoding (which was caused by an outdated version of Active Sky Next), would prevent the sim from even *attempting* loading the .DLL, so it will just not load, but with no error message.
Instead, your problem, is that the OLDER FSX Simconnect (the RTM version) is correctly installed, but the latest ones are not.
The Simconnect RTM version is the only one that doesn't contain the Simconnect_text API call. The SP1 and the SP2/Xpack version contains that function (which is REQUIRED by the Addon Manager) so, I can only repeat and confirm the reason for this error is that the FSX Simconnect SP2/Xpack version is not installed correctly in your system.
Also, re-read my previous replies about the VC++ 2005 SP1 runtimes missing. They are also required by the FSX Simconnect SP2 client.
I have the VC++ runtimes installed, but for the sake of additional troubleshooting, I downloaded them all again and reinstalled this morning. Still no luck fixing the issues.
(https://i.gyazo.com/d2e842404531b87be6f5af7e85f1d655.png)
All 4 (including the ESP version) of Simconnect were installed, in the add/remove programs control panel only 2 show up, however under WinSxS, they are all showing there.
(https://i.gyazo.com/f2f5d58fea08b8fd66a9eb049af92b9f.png)
(https://i.gyazo.com/40b59e017538a5bb2213ce1ebcfbb1a9.png)
Is there any kind of SimConnect installation validator tool to verify that everything is in place that is needed?
-
I have the VC++ runtimes installed, but for the sake of additional troubleshooting, I downloaded them all again and reinstalled this morning. Still no luck fixing the issues.
From your screenshot, it looks like you haven't installed all the VC++ 2005 runtimes, because you have several versions of the x64 runtimes (which are NOT used by FSX or P3D, since they are 32 bit apps), and only ONE version of the 32 bit version and, if that one is not the SP1 (VC++ 2005 SP1, not FSX SP1...), Simconnect won't work, because it requires the VC++ 2005 SP1 version.
Download and install the VC++ 2005 SP1 redistributable, the x86 version. Yes, even if your OS is 64 bit, for 32 bit apps to be working, you need to download the 32 bit (called x86) version of the runtimes.
-
I have read and re-read all the above and links within threads and more links within those threads. Still have this issue also, and have not changed anything in my P3D v3.1 accept I updated PMDG 777, any other suggestions? And yes GSX was working after the updated 777
-
This thread indicates all the possible causes, which in fact can only be two:
1) Your Simconect SP2/Xpack installation has a problem and has gone corrupted/missing, and the thread here indicates several possible solutions.
OR
2) Another library that is *required* by Simconnect SP2/Xpack has gone corrupted/missing. It's most likely the VC++ 2005 SP1 redistributable runtime, which must be installed correctly too. This thread also discussed about the VC++ runtimes, in the previous post.
-
I have the VC++ runtimes installed, but for the sake of additional troubleshooting, I downloaded them all again and reinstalled this morning. Still no luck fixing the issues.
From your screenshot, it looks like you haven't installed all the VC++ 2005 runtimes, because you have several versions of the x64 runtimes (which are NOT used by FSX or P3D, since they are 32 bit apps), and only ONE version of the 32 bit version and, if that one is not the SP1 (VC++ 2005 SP1, not FSX SP1...), Simconnect won't work, because it requires the VC++ 2005 SP1 version.
Download and install the VC++ 2005 SP1 redistributable, the x86 version. Yes, even if your OS is 64 bit, for 32 bit apps to be working, you need to download the 32 bit (called x86) version of the runtimes.
Did as you suggested, re-downloaded VC++ 2005 runtimes and the SP1 redistributable x86 and still having the error.
(https://i.gyazo.com/fab4bde02764aeffdec51d2e519bfed7.png)
-
Did as you suggested, re-downloaded VC++ 2005 runtimes and the SP1 redistributable x86 and still having the error.
Try to install BOTH x86 and x64 versions. Your screenshot shows you only reinstalled the x86 versions. You might try to use the Depends utility over fsdreamteam\bglmanx.dll
http://www.dependencywalker.com/
Use the x86 version and open bglmanx.dll. It will likely tell you which system libraries are missing/corrupted on your system. This won't FIX your problem automatically, but you should at least know WHAT's causing it.
-
Okay, I fixed the issue for me, hope it helps....
1 - Uninstalled all simconnect versions
2 - removed all simconnect.dll listed entries from the registry
3 - reboot
4 - Install again (lol) simconnect all flavors
Hope this helps, it was removing the registry entries that did it for me
-
Did as you suggested, re-downloaded VC++ 2005 runtimes and the SP1 redistributable x86 and still having the error.
Try to install BOTH x86 and x64 versions. Your screenshot shows you only reinstalled the x86 versions. You might try to use the Depends utility over fsdreamteam\bglmanx.dll
http://www.dependencywalker.com/
Use the x86 version and open bglmanx.dll. It will likely tell you which system libraries are missing/corrupted on your system. This won't FIX your problem automatically, but you should at least know WHAT's causing it.
Installed any missing Visual C++ 2005 runtimes (x86 and x64).
(https://i.gyazo.com/e260ae7889afaf548e0304cf903b5118.png)
Downloaded and ran Dependency Walker, opened d:\Prepar3d v3\bglmanx.dll, which resulted in the following modules showing as missing:
(https://i.gyazo.com/208e37af9193b6e5123c9a00d9b0bdc9.png)
-
Those error are not the problem, but check if you have other errors, and see the reply here:
http://www.fsdreamteam.com/forum/index.php/topic,12344.msg97781.html#msg97781
-
I am getting exact same errors posted by dizza.
Just updated p3d v3 to 3.1 & also pmdg 777.
nothing else has been altered.tried all the solution on this thread & other thread.
this is definitely an issue with addon manager.because if i remove the entry of bglmanx the entire quote.the simulator starts without problem but of course it means i can no longer use GSX(the only product installed on my system).
i am requesting to have a deep look into this because it seems a lot of people are now experiencing the problem.currently the only way to start p3d v3.1 is to disable fsdt addon manager/gsx completely.
before virtuali suggest me to install all those libraries once again.just to let you know i have done those.
-
Okay, I fixed the issue for me, hope it helps....
1 - Uninstalled all simconnect versions
2 - removed all simconnect.dll listed entries from the registry
3 - reboot
4 - Install again (lol) simconnect all flavors
Hope this helps, it was removing the registry entries that did it for me
can u explain what did you mean by "2 - removed all simconnect.dll listed entries from the registry"
-
can u explain what did you mean by "2 - removed all simconnect.dll listed entries from the registry"
What I did was search the registry with the keyword "simconnect" delete the folder entry and repeat using F3, reboot. Make sure you back up your registry before deleting anything.
-
this is definitely an issue with addon manager.
This is NOT an Addon Manager issue. The reason why, has been explained many times already in this thread.
because if i remove the entry of bglmanx the entire quote.the simulator starts without problem
That's because none of the other 3rd party modules you use (assume you use other 3rd party modules) requires the Simconnect_text() function call, which is only included in Simconnect SP1 and SP2 version.
The Simconnect_text() function call, instead, is NOT included in the original Simconnect RTM.
THAT'S the reason of the error message: the sim cannot load the Simconnect SP2 version (required by bglmanx.dll) for some reason, but IT IS loading the old RTM version and, since that one doesn't contain the Simconnect_text() function call, it gives you that message, because bglmanx.dll REQUIRES IS.
Of course, it's far from being the only 3rd party addon module that requires Simconnect_text() (it's the standard function that prints on the top green line), but if you don't have any of these installed, you are mislead thinking it's an "Addon Manager issue", because you don't see the error anymore, but the problem is NOT the Addon Manager.
The problem is your sim stuck with the outdated Simconnect RTM. That's the ONLY problem you have.
before virtuali suggest me to install all those libraries once again.just to let you know i have done those.
I will always suggest to reinstall the libraries, because that IS the problem and there's simply nothing we can do on our side to automatically fix your sim not being able to load the Simconnect SP2 version.
But as I've said, and as confirmed by other users that posted here, it's not ALWAYS possible to fix this by just reinstalling. In some cases you'll have to do remove all Simconnect libraries manually in SAFE MODE, then reinstall.
And, last user that posted and replied to you, said in his case he had to also clear the registry from the Simconnect entries, and then reinstall
-
i already said that i did all those simconnect libraries install.it didn't solve the problem.i will try to delete simconnect libraries in safe mode but i need to know how to delete registry for simconnect entries.
& i am very very disappointed at FSDT. people who are having these issues have common addons e.g. ASN,PMDG777,REX4.before saying a product is fully compatible with release,i think developer should test it more thoroughly before final release.
& i am sorry i can't agree with you.even what u r saying regarding the simconnect behavior.there should have been a release note regarding this issue in the first place with the latest gsx release.
because honestly the fact is users are unable to even start the simulator just because of a simple addon conflict is a catastrophic failure.
& i am sorry everyone for being angry.but,at this point i am very angry with FSDT.Simply because we have works to do other than solving some stupid libraries conflict which wasn't suppose to happen & it was the job of developer to make sure smooth experience as user end.
ban me or whatever u like to do.but,as a paid user i do have right to ask proper product support that i paid in the first place.
-
i already said that i did all those simconnect libraries install.it didn't solve the problem.
And I already said that this doesn't ALWAYS fix the problem.
i will try to delete simconnect libraries in safe mode but i need to know how to delete registry for simconnect entries.
The other user that replied to you, which I also pointed it out, already explained how he did it. I'll copy it here, again:
What I did was search the registry with the keyword "simconnect" delete the folder entry and repeat using F3, reboot. Make sure you back up your registry before deleting anything.
i am very very disappointed at FSDT. people who are having these issues have common addons e.g. ASN,PMDG777,REX4.before saying a product is fully compatible with release,i think developer should test it more thoroughly before final release.
GSX is 100% Fully compatible with P3D 3.1, and it has obviously tested with it ( I don't have any other P3D version installed ), but you cannot expect it would FIX your SIMCONNECT PROBLEM that doesn't have anything to do with it.
i am sorry i can't agree with you.even what u r saying regarding the simconnect behavior.there should have been a release note regarding this issue in the first place with the latest gsx release.
There's shouldn't be any release note, because a failure to load Simconnect SP2 is NOT something that is supposed to happen, and it's not obviously caused by our software, which is instead a VICTIM of it, but that we are supporting anyway, even if it's not caused by any of our software or installers.
because honestly the fact is users are unable to even start the simulator just because of a simple addon conflict is a catastrophic failure.
The error message you see, is NOT coming from the Addon Manager. It's coming from Windows itself, because Simconnect SP2 is not loading, so P3D doesn't start because of this. Under FSX, if Simconnect fails to load, the affected addons will just disappear but sim will continue to load. This seems to be a different behavior in P3D, which is of course outside our control.
i am sorry everyone for being angry.but,at this point i am very angry with FSDT.Simply because we have works to do other than solving some stupid libraries conflict which wasn't suppose to happen & it was the job of developer to make sure smooth experience as user end.
Your problem is that Simconnect SP2 is not loading. There's nothing we can do to fix this, other then tell you different ways to fix it, which is exactly what we did.
The real problem is the official Simconnect installer doesn't seem able to restore every issue, and sometimes you must act manually, as already suggested by the other user.
I hope you are not suggesting OUR installer should try to replace the Microsoft one and trying to hack your registry and fix things!!
ban me or whatever u like to do.but,as a paid user i do have right to ask proper product support that i paid in the first place.
I'm AM supporting you. And you have been given several different solutions so, what's the "ban" it's about ?
-
i already said that i did all those simconnect libraries install.it didn't solve the problem.i will try to delete simconnect libraries in safe mode but i need to know how to delete registry for simconnect entries.
Please report back after you try these two solutions, and we'll proceed from there.
-
OK so i found a solution myself.
No thanks to virtuali
& just FYI i tried uninstalling & deleting the simconnect folder located in winsxs folder.for some reason even on safe mode i was unable to delete those folders/files.
so,anyway somewhere i found a solution & it goes like this:
copy the following from : C:\Users\Your Name\AppData\Roaming\Lockheed Martin\Prepar3D v3 "dll.xml" file to C:\ProgramData\Lockheed Martin\Prepar3D v3 "dll.xml"
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
-
so,again virtuali this is not an simconnect issue.it's an issue that messed up by recent addon manager.
IT IS a Simconnect issue, and it's likely caused by another addon, and it WAS already discussed here, when one of the problems reported was the loading ORDER of the modules.
ANOTHER module, using the old Simconnect, version (the one that didn't had the Simconnect_text() ) was forcing P3D to use the old version.
It was suggested in this forum that changing the loading order of the modules in the XML file it would prevent the sim to be stuck with the old Simconnect because of the *other* module using it, see this post for the explanation and the solution:
http://www.fsdreamteam.com/forum/index.php/topic,12418.msg94305.html#msg94305
P3D now reads ALSO the DLL.XML in C:\ProgramData although it works with BOTH location: it merges them in a single list so, as if it was a single XML file, but it loads the modules listed in the XML file under C:\ProgramData FIRST.
By copying bglmanx.dll in the other XML in C:\ProgramData, you simply altered the loading order, which prevented the OTHER offending module ( the one using the outdated Simconnect version ), which was one of the solutions discussed here: loading bglmanx.dll FIRST.
So, your report further confirm the problem was caused by another module using the old Simconnect RTM and the sim being stuck with it, not loading the SP2 version required by bglmanx.dll, and you fixed it by forcing the sim to load modules in a different order.
-
OP here,
RVxSpeeds solution worked for me. Thank you for this and thanks to all the others trying to fix this issue especially virtuali. I tested it and I'm pretty sure I will buy GSX. This thread can be marked as SOLVED :)!
-
Confirm.. RVxSpeed solution also work for me.. P3D V3. Thanks..
-
Hello
i can confirm the solution and i have found the Problem:
The bglmanx.dll must be the first entry in DLL.XML, BUT the GSX Installer set the entry in the DLL.xml on ....AppData\Roaming\Lockheed Martin\Prepar3D v3
Some Addon manufacturer eg. PMDG an RAAS use the DLL.xml on C:\ProgramData\Lockheed Martin\Prepar3D v3.
When you Set the enry on the dll.xml in AppData\Roaming\Lockheed Martin\Prepar3D v3 is not the first entry in P3D.
To set in C:\ProgramData\Lockheed Martin\Prepar3D v3 is the correct Solution.
@virtuali
Is it possible to change the installer in the next version that is used the correct dll.xml?
Best regards
Jan
-
i can confirm the solution and i have found the Problem
C:\ProgramData\Lockheed Martin\Prepar3D v3 is the correct Solution.
@virtuali
Is it possible to change the installer in the next version that is used the correct dll.xml?
Maybe you haven't followed the thread entirely but, forcing bglmanx.dll to be loaded first, it's a WORKAROUND, not a solution! Normally, the loading order of modules shouldn't matter.
Windows Side-by-Side, when it works, is designed to allow multiple in-process modules using different versions of SxS libraries (Simconnect, in this case) to run *together* in the same address space.
If you are getting that error, it's because something in the SxS system is not working correctly and, BECAUSE another module is using an OUTDATED Simconnect (the one from FSX RTM, which is the only one that doesn't contain the Simconnect_text() API call), the sim is "stuck" with the RTM version, even if other modules are *requiring* the FSX SP1 or SP2 version of the Simconnect.
So yes, we could probably change the installer to use C:\ProgramData, which is loaded first, but this would be an issues ONLY if your SxS system is not working correctly AND you use 3rd party modules compiled with the obsolete FSX Simconnect RTM.
The REAL solution would be:
- Fixing your issue with SxS, so both Simconnect versions can be loaded at the same time, which is how the system was designed to work in the first place.
- Asking other developers to stop using outdated Simconnect versions, and use the most current one, the FSX SP2 one.
This will SAVE MEMORY too because, if you have one module using the RTM version, another module using the SP1 version and another one using the SP2 version, being all in-process .DLLs, ALL THREE will be loaded in RAM!! So, even when the SxS system works, it's best not to use it, from a performance point of view.
Instead, if all developers did the right thing, and only used the same Simconnect version ( the FSX SP2 version, the one we and others like PMDG use ), only THAT one will be loaded in RAM, which would result in some memory savings.
-
I understand your arguments. I read the article several times and searched a long time for this error.
The all manufacturers use the same version in the future will probably never arrive.
I have all SimConnect clients are installed and I have all the c ++ runtimes.
in the "dll.xml" I have under the "Addon Manager" the following entries:
<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>
<Manual Load> False </ Manual Load>
<Path>. \ RAASPRO \ RAASPRO.dll </ Path>
<DllStartName> module_init </ DllStartName>
<DllStopName> module_deinit </ DllStopName>
</Launch.Addon>
When i set the bglmanx.dll after RAASPRO i have this error. After PMDG works.
does this mean the RAAS use an old version of SimConnect?
best regards
Jan
-
When i set the bglmanx.dll after RAASPRO i have this error. After PMDG works. does this mean the RAAS use an old version of SimConnect?
Surely RAASPRO seem to be connected to this problem:
http://www.avsim.com/topic/475355-problem-with-raas-update-in-p3dv2-both-install-and-uninstall-woes/
http://www.fsdreamteam.com/forum/index.php/topic,13066.msg97871.html#msg97871
And yes, last time I checked it, it was using FSX RTM:
http://www.fsdreamteam.com/forum/index.php/topic,12418.msg94357.html#msg94357
But I checked the version that comes with the Aerosoft Airbus, the version that comes with the PMDG 777 loads Simconnect dynamically (I checked their code by disassembling it) and, for some reason, it triggers the sim to load the RTM version, and for some reason the SxS system doesn't work.
-
I have this same error and have found absolutely none of the Workarounds to be working for me.
I've been trying around and discovered that somehow the PMDG 737/777 and GSX seem to be conflicting. I can install one of them and it'll work fine. If I install them both together I get said bglmax.dll error. My dll.xml only contains one entry, and that is the one of Addon Manager.
I've also tried just installing the SP2 SimConnect, leaving the other SimConnects uninstalled. Same error when I install GSX and the PMDG aircrafts together, both on their own seem to work fine.
Then I tried reinstalling everything, no avail either.
I have read most of the topic about this issue, and even though im a beginner to P3D, I kinda understand that the issue should be version incompatbility, as in that one addon loads a version of Simconnect that is too old. But as far as I can tell, and have read, PMDG uses a new enough Version. So I'm absolutely clueless what the issue could be.
-
I've been trying around and discovered that somehow the PMDG 737/777 and GSX seem to be conflicting.
There's no conflict and no conflict it's possible, between PMDG and our software. This because PMDG USE and REQUIRE Simconnect SP2.
But the error you are getting ( the Simconnect_text() not found ), it's because YOUR SIM is NOT using Simconnect SP2, but Simconnect RTM, which is MISSING that function!
From the latest reports, this SEEM to be related in some way to the RAAS Pro program which COMES with the PMDG, which uses a different method to load Simconnect, which seems to cause a conflict.
Please read again this thread, because severa affected user fixed this by moving the bglmanx.dll lines to the DLL.XML in C:\ProgramData
-
First off, thank you for taking time to listen to my issues, virtuali.
I do understand that the PMDG and GSX both use SP2, which is what irritates me about my problem. I do also realize that loading RTM first is causing the issue, as bglmanx.dll is trying to load a method that isn't present in that version of SimConnect. I wasn't however aware, that RAAS Pro ist causing this.
Now for the dll.xml, I don't have one in my Main Directory, the only one I have is the one in %Appdata%/Lockheed Martin/P3D v3/ and that file only has two entries, bglmanx.dll as first entry, and some sort of Orbx DLL as second entry. bglmanx.dll should therefore be loading first. I've also tried copying the dll.xml to the Main Directory - no avail either. Now bglmanx.dll is the first dll to load in both dll.xml files, but the error persists.
Would you happen to have any more suggestions for workarounds, or maybe an idea how or why RAAS Pro manages to load in first, without having an Entry in the dll.xml.
EDIT: Creating an entry for RAASPro in the dll.xml file, obviously at the bottom of the file, made no change either.
-
I wasn't however aware, that RAAS Pro ist causing this.
It was something which was discussed in this very thread.
Now for the dll.xml, I don't have one in my Main Directory
You are not supposed to have one.
I've also tried copying the dll.xml to the Main Directory - no avail either. Now bglmanx.dll is the first dll to load in both dll.xml files, but the error persists.
That's because the "Main Directory" is NOT the place to put a DLL.XML, and nobody suggested that either. As I've said, and as also several users that had this problem also confirmed, you should trying placing the DLL.XML in the C:\ProgramData folder, which is NOT the "Main Directory"!!
C:\ProgramData is an alternative place for files that are supposed to be into %APPDATA%, just that %PROGRAMDATA% is for all users, and %APPDATA% is by-user.
The whole path, of course, would be C:\ProgramData\Lockheed Martin\Prepar3D v3
Which of course was ALSO discussed here, a couple of post before:
i can confirm the solution and i have found the Problem C:\ProgramData\Lockheed Martin\Prepar3D v3 is the correct Solution.
Try to read all messages of the thread, they DO contain useful informations!
-
You're right. My bad. Sorry for making you so mad.
-
Does this mean if i put my Dll.xml in the ProgramData folder, i wont need it in AppData?
-
Does this mean if i put my Dll.xml in the ProgramData folder, i wont need it in AppData?
No. If the OTHER addon which is CAUSING the problem ( remember, the problem is NOT bglmanx.dll, the problem is ANOTHER addon using an outdated Simconnect!! ), is being moved with it, the problem will be just the same: the sim might be stuck loading the outdated Simconnect, which doesn't contain the Simconnect_text() function, which is the reason of the error message.
Moving JUST the lines belonging to bglmanx over from the the DLL.XML in %APPDATA% to the one in %PROGRAMDATA%, it's just a trick to bypass the problem caused by that other addon, because the XML under %PROGRAMDATA% will be loaded BEFORE the one under %APPDATA% so, once the sim has loaded the correct Simconnect, because bglmanx.dll (as the first loaded module) has requested it, it won't try to load the outdated version when the other offending module is asking for it, since if it stays in the other XML under %APPDATA%, it's surely loaded *after* it.
Yes, I know it sounds complex and if other offending addons would start install themselves under %PROGRAMDATA%, the problem will happen AGAIN so, it's just a temporary fix.
The REAL solution, is that other developers would STOP using OUTDATED Simconnect versions (Simconnect_text() is available starting from FSX SP1, so they are still using the old RTM version for some reason) and fix their modules as soon as possible to support the current Simconnect API.
-
OK so i found a solution myself.
No thanks to virtuali
& just FYI i tried uninstalling & deleting the simconnect folder located in winsxs folder.for some reason even on safe mode i was unable to delete those folders/files.
so,anyway somewhere i found a solution & it goes like this:
copy the following from : C:\Users\Your Name\AppData\Roaming\Lockheed Martin\Prepar3D v3 "dll.xml" file to C:\ProgramData\Lockheed Martin\Prepar3D v3 "dll.xml"
Excellent, been pulling m,y hair out over this for hours, all I had to do was what you stated here ... BINGO !
-
Hi guys,
I'm in a bit of a pickle here.
It started off with the SimConnect_Text error and I tried fixing it using the suggest steps on page 1 by also deleting the SimConnect folder from the Winsxs folder.
However, when I'm trying to reinstall SimConnect, the deleted folder is not created in the Winsxs folder.
P3D now gives me 2 errors (it's translated from Dutch, so I don't know the exact error in English):
-Cannot start simobjectdisplayengine.exe
-Cannot start couatl.exe
So either the winsxs folder is corrupted somehow or it's a permission issue.
Any help is welcome :)
-
However, when I'm trying to reinstall SimConnect, the deleted folder is not created in the Winsxs folder.
It should. Do you have errors from the Simconnect installer ? Try running it in admin mode, immediately after a Windows restart.
-
Hi Umberto, thanks for your quick reply!
Frankly, I'm not able to select 'Run as administrator' through the right-click menu.
When selecting properties the option 'Run as administrator' is ticked but greyed out, so I'm not sure which mode the installer uses (my user account is admin by default btw).
No errors are being displayed when installing SimConnect. I do see the manifests being created in the winsxs folder, but nothing else.
Additional info: I'm using Windows 10.
-
I was able to restore the winsxs folder by using a Windows restore point, couldn't manage otherwiste but now it seems to be working.