Just wondering, since Im not the only person this has happened too because it also happened Spencer from Touch and Go Films.
It happen to many other people as well but, of course, we always fixed it in the end.
What has the forum of Fsdt done to fix the problem.
Fixing all those that asked for help here, which what we always do, as can clearly seen from all the forum posts.
but wouldn't you know the answer by now.
No, because what you are seeing it's just a diagnostic message from FSX that it can't load our module FOR ANY REASON. It doesn't mean the module is at fault, it simply mean it wasn't able to load it, for some reason.
But the *reasons* might be several, from the antivirus (most common one) to a conflict with another module, from a problem in the Windows trust system, to a problem with some Windows sytem libraries.
All those reasons happened, all of them has been fixed, but ALL of them started with that message, and they were all fixed using entirely different methods, depening on what the cause was in that single case.
So, you shouldn't do the mistake of confusing the diagnostic message with the cause, becuase the causes can be many and, unless we follow a way to troubleshoot it, there's no an "universal" solution to it.
Note that, in ALL cases when the problem was eventually fixed, it was ALWAYS something system related, antivirus-related, or other modules in conflict-related.
It was NEVER fixed by "fixing" or replacing our module, becaue there wasn't nothing wrong with it to begin with: it was just a matter of finding WHAT is causing it to fail on THAT specific system and, as I've said, the causes are many.
It is unfair that Im being asked to find the culprit when everything else on my system works well with each other.
It might be in YOUR case nothing is conflicting, then we'll proceed with other troubleshooting methods, and your issue will be fixed, as it was fixed to anyone that went here asking from help.
The only program that is conflicting is Fsdt.
A program doesn't "conflicts" on its own. If there's is a conflict, it's with something else, otherwise it should fail on each and every system. Since it obviously doesn't, it's clear the conflict is something else, and it needs to be identified what is in your case, on your system.
So what are you guys doing to correct this problem.
As as I've said, fixing the problem to everyone that asked for help here, as clearly demonstrated by following all posts, to their eventual conclusion, which alwasy was the problem was solved in the end, but with different methods because the causes can be several.
QW uses the same bglmanx.dll and it won't work either.
That's normal. Since the file it's the same, if something on your system is causing it to fail, it won't change if it's installed with QW or with FSDT, it will still suffer from that "something else" on your system that is preventing to work.
Seriously, my system is fine but Fsdt should have used something other then Coautle to run their program
Now I don't understand: you are saying the error is coming from bglmanx.dll, now you are saying is coming from Couatl.exe ? Please, clarify better: do you see the error on bglmanx.dll only, on Couatl.exe only, or both ?
I won't hesitate for a second to post on my Youtube page this problem with Fsdt.
By posting all over the world about your problem, you will only show that your system had a problem, nothing more than that.
Since we have a Trial version of all our products, everyone can freely download them on his own system and 99.99% of the cases, he'll find they works just fine, and when they don't, he can come here and have the problem fixed.
Please choose your words carefully when you reply because it's been over 2 months and you havent given me an answer just pot luck solutions that don't work.
Your last message was on Sept. 4th, to that I replied in about 1 hour, asking to try something.
You are now replying 20 days later than what you have been asked to (trying to exclude any other modules to check for a problem) is "not fair".
It might be there's no conflct with another module, but before being sure of it, we need to test it so, please, do what you have been asked to because, if you have tried all the other usual solutions, like checking the antivirus and the trust system haven't worked, there might a chance there's another module in conflict.
Sometimes, it might be enough to change the module's loading *order*, and it migth do away but first, it needs to be identified if there is a conflict indeed, otherwise we don't have any way to know with *which* module we should exchange the loading order with.
So, we are now back to my last message, please try this:
- Open you DLL.XML file with a text editor (eg. Notepad is fine), the file is located at %APPDATA%\Microsoft\FSX
- Look for all the <Disabled> tags, and change them to <Disabled>True</Disabled>
- Do this for ALL the <Launch.Addon> sections, EXCEPT for the Addon Manager one (bglmanx.dll) and the main section at the top of the file (which would disable the whole XML file so, you shouldn't change it)
- Save the file and exit.
- Do the same for the EXE.XML file, located in the same folder, disable all modules EXCEPT for Couatl (fsdreamteam\couatl.exe)
- Save the file and exit
- Launch FSX and see if it works. If it does, re-enable every module, one by one, check if FSX works, enable another module, and so on, until you find the conflicting one.