FSDreamTeam forum
General Category => General Discussion => Topic started by: Kevin on January 17, 2010, 02:39:32 am
-
I have had so many problems with your sceneries I don't even use them anymore. I did all the "fixes" which did help but then stopped working and I had the same problem. I can not have those 2 lines for the dll's in my trusted programs for my flight sim to load or I have to reinstall addon manager every time I boot FSX. I just gave up after a long time working on it. What gets me is mine used to work fine. After a recent reformat I have problems with the bglmanx and addon manager. Why can't you just use a normal installer like ever other fs company.
KB
-
I HAVE THE SAME EXACT PROBLEM!!
I just reformatted the other day to Vista x64, I own the KORD, KFLL, and cloud9 KMCO sceneries. They all workeded perfectly before I reformatted, I've looked into all the problems with the dll.xml, fsx.cfg, and all the problems between fscopilot and add on manager. I am quite disapointed now after all my hard work that I can't even be able to use the $90 worth of scenery I have purchased. I just sometimes wonder why fsdream team and cloud 9 don't just use a regular installer that everyone can use without problem, it can't be for security because people can find a way around anything, so just make it easyer for people that actualy bought your product.
-
Why can't you just use a normal installer like ever other fs company.
KB
Virtuali will not let statements like this go unanswered, but in the mean time, may I suggest you read the FAQ?
-
Please, for the last time, STOP keep saying "use a normal installer like ever other fs company", as if we haven't explained, many times already, everywhere in the site, and of course the FAQ, that the Addon Manager IS NOT used just for protection!!
Asking something like this, is like problems with FSUIPC and asking an airplane developer stop using it. We just can't, because the scenery needs it for too many other things beside protection. If it's not clear enough: we would use the Addon Manager even if we released a scenery without activation. Or even a freeware scenery.
The first usual suggestion, whenever this problem happens, is to install the Stand-Alone Addon Manager first:
http://www.virtualisoftware.com/binaries/setup_addonmanagerX.exe
This will surely update all your files because, if you reinstalled using old and new installers together, perhaps something old got mixed with something new, and this might also create problems.
-
Ok, I intalled the add-on manager as you said, my fsx still freezes at the splash screen like always, I do have fs copilot installed as I know that there is some conflict between the two, when I disable fscopilot in the dll.xml, my fsx will work, but I wont be able to connect to Vatsim, which is where I fly 99.99% of the time.
-
I noticed just now that the addon manger was at the bottom of the dll.xml, so I put it at the top of the list so it would be above fscopilot, but it still freezes
-
Ok, I intalled the add-on manager as you said, my fsx still freezes at the splash screen like always, I do have fs copilot installed as I know that there is some conflict between the two, when I disable fscopilot in the dll.xml, my fsx will work, but I wont be able to connect to Vatsim, which is where I fly 99.99% of the time.
The suggestion about exchanging the order of loading came from something that we noticed a while ago: if FS Copilot loaded before the Addon Manager, it prevented the creation of the Addon Manager menu, and any further communication between Addon Manager and Simconnect, as if FS Copilot blocked Simconnect communication of addons loaded after it.
I also had some email exchanges between the FS Copilot author about this, but he didn't had any clue. However, exchanging the order of the modules and having the Addon Manager loaded first, used to fix the problem.
There was a post about it on the old Cloud9 forum:
http://forum.fscloud9.it/viewtopic.php?t=4269&sid=3fe8c431967d53cd85c68ef4db4fa059
However, this was about 3 years ago, before FSX SP2 was published so, it might not be useful anymore. There might be some additional issues with Vista or Windows 7 as well.
The issue is, last time I've checked it, FS Copilot used to be compiled requiring the FSX SP1 Simconnect, meaning it should work with FSX SP1 or FSX SP2 because, on a correctly installed FSX, both versions will be available.
Instead, the Addon Manager is compiled to require the FSX SP2 Simconnect, and it can't be made in any other way, since it actually *uses* some SP2-only features.
Now, in THEORY, thanks to the Windows Side by Side loading mechanism, it should be possible for two modules to use both versions together at the same time meaning, if 2 modules are loaded in FSX, one ( FS Copilot ) requiring the SP1 Simconnect and another ( the Addon Manager ) requiring the SP2 Simconnect, BOTH .DLL will be loaded in memory at the same time which, as I've said, should work in theory, but it's a very complex mechanism, that might not be very reliable, or might have changed in Windows 7.
This might be a reason why the 2 programs can't work together and, if this is the case, I'm afraid it's FS Copilot that needs to be updated to support the current Simconnect version.
If they wanted to target more users and having the program work on FSX SP1 as well might be desiderable but, the correct way of doing this is NOT just compiling for the old version and hoping that Windows Side-by-Side would work. Instead, they should check the Flight Sim version and DYNAMICALLY load the most updated Simconnect that is being found, which is how FSUIPC does, for example. FSUIPC works with FSX SP1 and SP2, but doesn't create problems to the Addon Manager because, under FSX SP2 ( which is the only version that we run under so, it's the only case when the 2 are used together ), it's able to dynamically load the Simconnect SP2 version so, there's no chance for a conflict or a crash, becasue we use that one as well.
It has been quite some time since the last time I've checked FS Copilot so, I have no idea if they updated to use SP2 Simconnect but, this is really the only possible explanation I have for the two not working together.
At this time, the only solution to use our products and online networks, is to use Squawbox instead.
-
Well how come everything worked when I had vista, and now I reformatted to the same vista I had, but it doesn't work, what changed?
-
Well how come everything worked when I had vista, and now I reformatted to the same vista I had, but it doesn't work, what changed?
You mean that, on your old installation, the Addon Manager and FS Copilot worked together, now they don't ?
If this is the case, that might just be a confirmation of what I was saying: it's probably something related to Windows .DLL, a Side-by-side, most likely.
Maybe it's something else that you previously installed in Windows, that allowed to the Windows Side-by-Side mechanism to work, and it's now missing.
Now, a very simple question: how come that FS Copilot is the ONLY 3rd-party module we know of, that doesn't work with the Addon Manager ? Which includes also a very similar program, namely Squawbox.
We know for sure that none of the most commonly used ones, like FSUIPC, Pmdgoptions.dll, Aerosoft Vimacore.dll, several Wilco .dll, but many others as well. None of these addons are creating similar issues. Which obviously mean, all these modules, INCLUDING the Addon Manager, are working as expected which, if correctly made, is what it's supposed to happen. It's not that we explicitely did something to allow compatibility with those modules: they just work, and we only verify from time to time they do. The one and only program we ever got problem reports, starting from 3 years ago, it's FS Copilot.
So, I'm sorry, but there's nothing else to say, other than switching to Squawbox, until FS Copilot gets fixed.
-
I have the same problem as the other guy and I am using Windows 7 64bit. I installed all of my sceneries before I installed fscopilot and it worked fine to me. It just seems wierd to me that were both having the same problem right now after a reformat. When did addon manager last update. Thanks
KB
-
It just seems wierd to me that were both having the same problem right now after a reformat
As I've said already, maybe it's something else that you previously installed in Windows, that allowed to the Windows Side-by-Side mechanism to work, and it's now missing.
When did addon manager last update.
It's always being updated, at least every 15-20 days, that's why its installer always gets it online, to be sure everyone gets the latest version. But, I can't think of anything that would create a new conflict with only one module, that was known to have issues with it for about 3 years, as was said in that post on the old Cloud9 forum I've linked.
Yes, there's IS a small difference in the installer, about the handling of the DLL.XML file: right now, is not sorting the module's list anymore in order to always have the Addon Manager on top of the list, so it wouldn't be blocked by being loaded after FS Copilot, which was the original issue we found. That's why I've suggested trying reordering the modules to have FS Copilot loaded last which, according to one poster, didn't change anything so, I suspect this might be something else, perhaps related to Windows 7.
-
Ok thanks, I would change to squawkbox so that I could use these sceneries but there's just so many things I don't like about it so I'd rather keep with my fscopilot. I did get some sort of beta one this time and I think it may be a little different from the other one I had. I'll look into it, I just wish there was an easy fix.
Kevin
-
Is there a way I could get a older version of add on manager, maybe the one that came out after KFLL because I remember that I had both KFLL and FsCopilot working when KFLL came out.
-
Is there a way I could get a older version of add on manager, maybe the one that came out after KFLL because I remember that I had both KFLL and FsCopilot working when KFLL came out.
There's no reason why an older version, which is still very recent would work with FS Copilot and the present one not. And, that version wouldn't work anyway with anything we'll release in the future.
I'm sorry, but I can only repeat and confirm: there's no other solution right now, than to use Squawbox.
-
In my root Microsoft Flight Simulator Folder I noticed that there is a file named: bglmanx_fsdt.dat
What is this file because I know that bglmanx.dll has to do with addon manager, and fsdt has to do with fscopilot.
When I open this file I get random symols with notepad.
-
What is this file because I know that bglmanx.dll has to do with addon manager, and fsdt has to do with fscopilot.
All files with names starting with bglmanx are part of the Addon Manager, and it won't work without. It has always been like this before, nothing has changed.
As I've said, there aren't any reason why it wouldn't work with FS Copilot which, BTW, it's the ONLY 3rd party .DLL module we know of that doesn't work with the Addon Manager.
EDIT:
I see why you might be confused: the FS Copilot installs in a folder named FSFDT, which is of course different that bglmanx_FSDT, it's just similar, and might lead into thinking the two have something in common.
-
Yeah I read your edit and that is true.
But in other news I was able to start FSX with addon manager and fscopilot running together, but I cannot recreate this again, it was some sort of fluke.
All I did was I tried to delete the bglmanx.dll, and coatal lines out of the [trusted] part of the FSX.cfg to see what that would do, and FSX started fine without problem and I could run addon manager and fscopilot together fine.
But I then restarted fsx and my same issue occured, that it wouldn't start, so I tried to delete those lines out of the cfg again and nothing happened this time.
-
But in other news I was able to start FSX with addon manager and fscopilot running together, but I cannot recreate this again, it was some sort of fluke.
That's exactly what I've found to be happening. Installed FS Copilot to have a look at it, it crashed the first time it was trusted. But this is sometimes to be expected, happens to the Addon Manager sometimes.
On the next FSX launch, both FS Copilot and the Addon Manager started fine.
Then, I tried launching FSX for the 3rd time, and now it freezes at the "Create Flight" screen each time. Can't start them together anymore. So, it seems that, if FS Copilot runs once, it does something (or create some file) that will prevent it to run together with the Addon Manager.
However, FS Copilot clearly has some other issues, entirely not dependent from the Addon Manager because, with the Addon Manager DISABLED, I keep getting crashes on exit from FSX, if FS Copilot is installed.
All I did was I tried to delete the bglmanx.dll, and coatal lines out of the [trusted] part of the FSX.cfg to see what that would do, and FSX started fine without problem and I could run addon manager and fscopilot together fine.
This would have the effect of repeating the "Trusting" question.
But I then restarted fsx and my same issue occured, that it wouldn't start, so I tried to delete those lines out of the cfg again and nothing happened this time.
Why you keep acting on the assumption that it's the Addon Manager that needs to be "fixed" in some way ?
For example, in this case, you should also have removed the Trusting lines in FSX.CFG for FS Copilot as well. I assure you that, if you keep insisting trying to "fix" things by mingling with Addon Manager files only, you will not get very far.
-
I just installed Microsoft Visual C++ 2008 Redistributable Package (x64) and the first time I loaded FSX it worked but it freezes everytime after that.
-
I just read this other post on these forums where you told someone not to use the 2008 redistributable, so I installed the 2005 sp1 (x64), on my first start of FSX it crashed but on the second time it was fine, but when I loaded in a flight and hit FSInn Control Pannel in addons, FSX froze.
Now it's back to freezing at the splash screen.
Hopefully this information is helping.
-
All these applications (FSX, the Addon Manager and FS Copilot) are 32 bit apps so, if anything, you need to install the 32 bit versions of the VC++ Redistributables. The x64 version is only used by 64 bit applications.
However, at least with regard to the VC++ 2005 SP1, since we use it, we install it...
And, there are some Windows updates that only appear *after* you installed those runtimes so, it might be worthwile to do a Windows update after installing all the runtimes.
However, my machine has all the runtimes installed and patched, and FS Copilot+Addon Manager now freezes each time, after having started successfully only once, the first time FS Copilot ran successfully after the first crash that happens when you trust it.
I had a look at the FS Copilot binary file and, there are a couple of peculiar things about it:
1) The file doesn't have a dependency manifest embedded, which should help Windows sort it out Side-by-Side loading when used together with other .DLL modules in the same process. FSX modules usually have it for this very reason ( FSUIPC.DLL has it, BGLMANX.DLL has it, VIMACOREX.DLL has it, PMDGOPTIONS.DLL has it...)
2) The file is byte-for-byte IDENTICAL in FSX and FS9, which is unusual.
3) It's not digitally signed. This shouldn't be problem, but since the FSX Trusting mechanism is so unstable, you never know.
-
I also have another computer in my home that has addon manager, fscopilot, and vista 64 bit that runs everything perfect. And prior to reformatting my computer I ran addon manager and fscopilot fine also.
Could I take some files from the FSCopilot files on the other computer in my house and transfer them to my computer. If so what files should I try.
-
You should always use the proper installers that comes with each product. Just copying files manually, if you don't know exactly what you are doing, is usually a recipe for disaster. Of course, since this is not FS Copilot forum, we can't obviously help you with anything related to it.
I've simply used its installer, I don't have the slightest idea how it works and what it does.
-
Also when I reformatted this time I downloaded a more updatted driver than what I had on my system before the reformat, could this have messed something up, should I get the older driver I had.
-
I downloaded a more updatted driver
What driver ?
-
Video Card driver
Im trying to think whats different about my system after the reformat, since I had it working before I reformatted.
-
I don't see how a video card driver could affect FS Copilot or the Addon Manager, other than having the Video card driver installer changed something in the VC++ runtimes. But if this is the case, it should be fixable ( or not ) by updating all the runtimes.
Which, as I've said, it's already done by our installer, for the runtimes we need. Since FS Copilot doesn't come with a manifest, it's difficult to say which runtimes (if any) needs. And not just which, generic, runtimes. The manifest serve the purpose to indicate to Windows exactly which version the program needs becahse, the whole point of the Side-by-side mechanism, is to allow different versions of the SAME .DLL to run together at the same time.
If, by misfortune, FS Copilot required a *DIFFERENT* VC++ 2005 SP1 version than we need (yes, you can have multple versions of the VC++ 2005 SP1 installed at the same time) and, by pure chance, they called a library function that is not backward/forward compatible so, it would not run with our version, they'll crash together. If they included a manifest, Windows would have loaded their preferred version as well, thanks to side-by-side.
But, again, THIS IS NOT FS COPILOT FORUM so, anything I'm saying here, it's pure speculation: I don't know if they require runtimes at all, I'm just saying *what* could wrong, and this is explanation at least is compatible with the fact that it might work on a Windows installation, and might not on a different one, depending on what system libraries are installed.
-
Where is the fscopilot forum, I can't find the official site for fscopilot?
-
I think it has been closed for maintenance:
http://www.mcdu.com/
-
Dear Virtuali,
after installing your new PHNL scenery, all your other sceneries won´t show up anymore. I really don´t want to get on anyones nerves, but only your sceneries are difficult to handle. I love flying, but I hate having to maintain the sim more than absolutely necessary. I just can´t rely on your sceneries showing up after a long flight. Everything is much too complicated.
This evening I installed PHNL which lead to double entries in the FSX.cfg. I deleted the double entries (coutl.exe and bglmanx) in the trusted section and ran the stand alone addon manager installation again. Now none of your sceneries show up.
The visual quality of your sceneries is very good (that´s why I bought every single sceney until now), but the fact that with every new installation process new problems pop up is very annoying. I understand that your sick and tired of answering the same questions over and over again, but I don´t feel like having to go troubleshooting everytime I add a new scenery. Explanations like some other programm has corrupted this and that file really don´t help, because no other scenery is that "vulnerable" or easy to mess up.
I really don´t know what to try next and to be honest, I´m growing a bit tired of solving problems that could be prevented.
What can I do next without having to reinstall everything (something I really don´t have the time for)?
I use Vista 64-bit SP2.
Regards,
Ingo
-
Hi, it´s me again.
I calmed down a bit and did some more reading in this forum. For some reason I decided to de-, then to reinstall PHNL and guess what!? Everything is fine. I really don´t have a clue what went wrong during the first installation process.....
Flightsimming is more about computers and software than virtual flying. I spend about just as much time keeping the sim running as it should as I do in the air. :o
Hope you don´t hate me for turning nuts.
Ingo
-
This evening I installed PHNL which lead to double entries in the FSX.cfg. I deleted the double entries (coutl.exe and bglmanx) in the trusted section and ran the stand alone addon manager installation again. Now none of your sceneries show up.
Double entries in the Trusted section is NOT an error. It simply means that a new version of that module has been trusted so, FSX will not repeat the trusting question again for that specific version. But, as I've said, the fact you have several entries for the same module, it's not a problem, at all.
The suggestion of removing the entries is not because just having entries (single or double, it doesn't matter), it a problem. It's because the FSX trust system cleary has issues because, the SAME module that the 1st time is trusted is wrongly labeled as problematic, it always run, either by launching FSX again, or by rebooting Windows. Removing all the entries, it's just a way to force FSX to redo the trusting question, nothing more.
Explanations like some other programm has corrupted this and that file really don´t help, because no other scenery is that "vulnerable" or easy to mess up.
Explanation are correct. And no other scenery is "vulnerable", because doesn't use a dll module which, as been explained many times, does too much for the scenery and it wouldn't work without. But, it's absolutely not true that no modules are so "vulnerable", because if you simply look at other support forums, you'll see that everyone else that depends on .dll modules has similar issues, trusting issue, antivirus issues, etc.
This is the only major gripe we have on FSX: the requirement for all modules to be trusted, which is obviously bugged, and the dependency from the XML files to load modules. FS9 DOES NOT have all these issues, because modules don't need Trusting, and everything that is placed under the MODULES folder will just be loaded automatically.
What can I do next without having to reinstall everything (something I really don´t have the time for)?
The first and easiest solution, is always this:
- Uninstall PHNL. Reply YES to the question "Do you want to remove the Addon Manager?" and replying YES to the question "Do you want to remove the Couatl engine?"
- Reinstall PHNL. If you see the Trusting message, trust all modules.
- If you see the "3rd party module" error message, keep ignoring it and ALLOW the module to run. Do this a couple of times. If it doesn't go away, reboot Windows and try again. It WILL go away.
-
I did a reformat just 2 months ago with the same exact settings. So yes your answer will be there's no fix, it's fscopilot BUT, why would this problem happen right now. None of my settings are any different on my computer. Have all the same sceneries and version of fscopilot. I just wanted to say I have never had any sort of issues with your sceneries. The fscopilot version has not changed in a very long time. FSDT sceneries do....that's why my conclusion would obviously be your sceneries.
KB
-
The fscopilot version has not changed in a very long time. FSDT sceneries do...
The only thing that changed recently, it's the installer doesn't put our module before FS Copilot, as it used to do, in order not having blocked by it. This because we now use the standard MS XML parser to add section, which it's easier and more reliable, with strangely formatted XML files, but there's no way to exchange the order using that method.
That's why I've immediately said to try exchanging the loading order. However, if this doesn't change anything, I really have no clue. However, the undeniable fact is, as proven from the old post from 2007 on the Cloud9 forum, that FS Copilot was known to have issues with our module since 3 years already.
It shouldn't be strange that it doesn't work now: it should be strange that it did before. BTW, the FS9 version (which, as I've said, it's *exactly* the same .DLL that works in FSX as well), constantly crash on exit on my system, even if the FS9 WORKS with the FS9 version of our Addon Manager.
.that's why my conclusion would obviously be your sceneries.
No so fast. There are other things that keep changing, and it's the various Windows updates, which over time changes a lot of system .DLL so, it's surely possible that, one of these updates has made the problem (that always existed) between FS Copilot and our own module, to reappear.
-
I think you need to consider a solution because your answer to everyone that uses fscopilot and purchases your scenery can not be install squawkbox. Addon Manager is ridiculous and has always been a pain.
KB
-
I think you need to consider a solution because your answer to everyone that uses fscopilot and purchases your scenery can not be install squawkbox.
As a matter of fact, they have to. Don't you think that, if the problem could be fixed from our side, we would tried it already ? Have you followed the explanation ?
If the issue is caused by a conflict between something that FS Copilot use, which is most likely a system component, why should be fixed from our side, considering that our module is constantly kept updated, while FS Copilot hasn't been upgraded for a lot of time ?
There's not a support forum open anymore...how can we possible get a clue why their module create this issue ? Not that we didn't already, a while ago. The reply was they don't have any clue either.
Addon Manager is ridiculous and has always been a pain.
That's not the case. The fact is that FS Copilot that is the ONE AND ONLY 3rd party module that doesn't work together with the Addon Manager.
You might have had a point, if you were able to name *another* 3rd party module that doesn't work together with FS Copilot. None of the most commonly used ones has such issue. We have users with a DLL.XML file with *dozen* of modules installed, and NONE create this issue, only FS Copilot.
I repeat and confirm, you have to switch to Squawbox, which works without issues with the Addon Manager, like any other module out there we know of, except FS Copilot.
-
Kevin is 100% correct. Let me get one thing across first...I DONT HAVE FSCOPILOT EVEN INSTALLED. Ok...now, I recently reinstalled my ORD scenery that I purchased maybe a year ago. When doing so it updated my version of addon manager automatically. I run fsx and it asks me if I trust addon manager and if i want to run it...i click yes...load up and reactivate my scenery. Later in the day I go to open fsx and I dont even make it past the FSX splash screen. I unistall my fsdt sceneries and addon manager and my fsx runs fine. CLEARLY, the lastest addon manager is corrupt and needs to be fixed. What am i now, the 3rd person with the same issue? Iv had fdt sceneries for a longgg time and never had an issue till now and its the sameone kevin is having. Id like to see this fixed or I would like atleast half of my money back.
-
Kevin is 100% correct.
No, he's not, because he's having a problem only if FS Copilot is installed. If he removes FS Copilot, FSX runs fine.
I'm just saying that we'll NOT pursue THIS issue, because FS Copilot is the one and only module that doesn't work with the Addon Manager, it hasn't been updated for ages, and there's no even an official website/forum right now, that users might go asking for ideas.
Everything else related to the Addon Manger, we'll WILL hunt down and help everyone. Just not, in the one and only case, where FSX runs fine, and stop working with the Addon Manager ONLY because FS Copilot. This is the only case when there's just nothing we can do, because we don't have the slightest idea why FS Copilot does this.
Let me get one thing across first...I DONT HAVE FSCOPILOT EVEN INSTALLED.
Then you have a different issue.
What am i now, the 3rd person with the same issue? Iv had fdt sceneries for a longgg time and never had an issue till now and its the sameone kevin is having
No, you don't have the same issue as kevin because, if he removes FS Copilot, FSX runs correctly so, clearly, the Addon Manager works on his machine, without FS Copilot. So, your issue is different.
Now, let's try to see why it doens't work on YOUR machine:
Let's start again from scratch:
Please describe, exactly, how FSX stops.
Do you see any error ? Or it just quits ?
-
Ok I think you have convinced me to try squawkbox because I am missing your sceneries and the QW757. Just a quick question about it(I know this isn't their support but maybe you will know) How do you change one of their default aircraft modules to one of yours. Such as I want to change the default Delta B752 paint from theirs to my better looking module. This is why I did not want to switch because it's such a pain getting all that back in there and I don't know how. Thanks
KB
-
You can install new repaint ( lots of them ) with the QualityWings 757. In fact, we wrote the Livery Manager for them...however, I really don't know if it would be possible to merge it with a different model.
-
I just purchased the Ultimate Traffic 2 for FSX and there's and already made file for it so that it will display all the vatsim traffic with the modules from it which is really cool. Their great modules and I see in one of their JFK pictures it looks like your scenery. Thanks
KB
-
Is there anyway to get a download link for the old add on manager? This is really frustrating! My FSX worked great with FScopilot installed and all of your sceneries until Honolulu. Now it is broken and will not start unless I uninstall the add on manager. Of course my aircraft of choice is the QW757 of which I cannot get to load anymore either. This just sucks!
-
The Addon Manager hasn't been updated for PHNL release.
The version that was released with PHNL is exactly the same that was released with the QW757 so, if you had the QW757 working previously with the Addon Manager and FS Copilot, it means the reason why they don't work together now, doesn't have anything to do with PHNL release, but it should have been apparent with the QW757 release as well, IF it was really depending by the Addon Manager.
And no, there's no way to use a version of the Addon Manager *older* than the one that came with the QW757 because that one will not work with the QW757 either.
As I've said, there's no other solution right now, than to use Squawbox. The only thing I can say is that, when the FS Copilot support forum will eventually reappear, we'll try to get in touch with them again, it just doesn't make any sense trying to fixing something that is not even supported at this time.
-
All I know is that I have used theQW757 from the day it came out until the day I put PHNL on my system and it worked like gold. Now, it does not work at all. I have uninstalled FSCOPILOT and FSINN and it still will not open up FSX. Your solution of blaming everything on FSCOPILOT is unacceptable!
-
All I know is that I have used theQW757 from the day it came out until the day I put PHNL on my system and it worked like gold.
That's only confirms what I've said: since the Addon Manager that has been released with PHNL is the same that comes with the QW757, and it has NOT been updated for the PHNL release, it means that what created the problem between this FS Copilot, is something else, possibly a Windows Update because, if it WAS the Addon Manager, you should have seen this problem with the QW757 already because the .DLL it's the same as the one that came with PHNL. At least until late yesterday night, because we put another update online.
Just FYI, the Addon Manager that comes with the QW757 and with PHNL, it's version 2.7.0.16. The one we put up yesterday night it's 2.7.0.17 - It will be automatically downloaded whenever a scenery installer or the Stand-alone Addon Manager installer are launched.
Now, it does not work at all. I have uninstalled FSCOPILOT and FSINN and it still will not open up FSX.
Without FS Copilot, as confirmed by other posts here, the Addon Manager works. The FS Copilot issues manifests in this exact way: FSX loads, but it hangs on the "Create Flight" screen.
If you have another issue, please state exactly what's happening here.
And, try to reinstall the Stand-alone Addon Manager because there's already a new version onlilne (which doesn't have anything to do the with FS Copilot and it will not fix the FS Copilot issue), but it might be better to fix other errors, not related to FS Copilot, that might happen.
Your solution of blaming everything on FSCOPILOT is unacceptable!
Wrong. You don't seem to understand what I've said.
The facts are:
- FS Copilot is the only and one 3rd party module that is known to crash together with the Addon Manger. None of the other popular addon modules, from FSUIPC to Wilco, to PMDG, to Aerosoft have this issue.
- This DOES'T mean I'm "blaming everything on FS Copilot", which is obviously wrong. Since FS Copilot hasn't been updated in ages, it might just be a *victim* of something that has been updated in Windows, like a security fix or something similar.
And, as I've said, since there's nobody to support it and no discussion on their forum, which is not active at the moment, it's difficult to say what can be causing this because, obviously, we don't know what might affect FS Copilot, like with libraries it needs, etc.
-
I urge everyone using FS Copilot to launch the Stand-alone Addon Manager installer again, because we have another update that *might* fix the problem.
If it works, it only confirms what I was suspecting, that was a problem of system libraries conflict, because nothing has changed in the Addon Manager actual code, just a compiler settings to use system library in a slightly different way (which wasn't touched in ages so, it means it has been broken by a Windows Update).
Is still not very stable, because I still get a consistent crash when exiting from FSX, but only if FS Copilot is enabled. However, since it does exactly the same in FS9, which never had any problems together with the Addon Manager, it might be an entirely different issue.
-
Not sure what you did, but all is working again! I used the new addon manager and have no more problems with start up or with FSINN/FSCOPILOT. Thank you for fixing this issue so quickly. Ok, now back to my cockpit!
-
Hi Virtuali
I've got some little problems with these sceneries (LSGG/KJFK/KLAS/KORD/LSZH): no building appears now and I don't understand why. I've tried to reinstalled the sceneries and the new addon manager but nothing are working.
I can't explain why. I red all the forum lines about the problem which occurs many time but I didn't understood how to resolve it I'm sure its should be not a big problem but I need help.
Thank you for your extremely patienza (when reading the forum!) and also for taking time for me (if you can).
Got any solution?
Thanks by advance
Phil
-
just a compiler settings to use system library in a slightly different way (which wasn't touched in ages so, it means it has been broken by a Windows Update).
Umberto, care to share? I know this is unrelated, but I'm trying to help fix a bug in the Level-D 767 ground menu. It ocasionally shows a ntdll.dll CTD error when opening. I want to contact Wade (the developer) with some solid evidence of this being a 'possible' bug with the Level-D and since you mention compiler settings, Im guessing (like you said) Windows Update changed something along the way that could be the cause of CTD's.
My guess is:
ms vc++ 2005 redistributable and some define somewhere plus a security fix preventing/breaking compatibility, correct?
-
ms vc++ 2005 redistributable and some define somewhere plus a security fix preventing/breaking compatibility, correct?
No, I haven't changed anything in the program code, and not even in the actual c++ compiler: it was related to how the code is wrapped when signed, and how this interacts with installed system libraries.
That's might be a reason. There are several security hotfixes that updates files related to those runtimes, one of them might have broken compatibility between a standard library call that was used by both programs.
In fact, is more complex than that, because there's also the issue of the Windows Side-by-Side loading mechanism, which should in theory fix those problems, but it requires all the apps using those libraries to have an embedded manifest (which the Addon Manager has, the FS Copilot hasn't, that's why their eventual dependencies of different versions of the same library can't be solved with the Side-by-side system)
And, there's also the side-by-side policies mechanism, which is a file that automatically "upgrades" a program to use a newer version of a .DLL (if found), even if that program had a manifest that specified an older version. But, of course, nobody can be 100% sure that the newer version doesn't break compatibility with programs compiled for earlier version.
The main issue here is, as usual, security: there's a conflict between the simple Side-by-side, which allows programs written for different version of the same library to run together, each one loading its own version (which wasn't possible before side-by-side) and the policies, that upgrades those older programs to use the newer libraries, which are supposed to be more secure, but there's an added risk of breaking compatibility.
-
I've got some little problems with these sceneries (LSGG/KJFK/KLAS/KORD/LSZH): no building appears now and I don't understand why. I've tried to reinstalled the sceneries and the new addon manager but nothing are working.
It's obviously impossible to help you without any description of what's happening.
So, the usual question, which is of course has been repeated in countless of other threads:
- Do you see the Addon Manager menu ?
- Do you see the Couatl menu ?
- Have you seen the question about trusting the Addon Manager when you installed the new version ?
- Have you replied YES to that question ?
- Have you done the same for Couatl ?
- Have you turned OFF your antivirus when installing the scenery and/or the updated Addon Manager ?
- Have you configured your Antivirus to ignore the following files, before trying to run FSX again ?
\Your_FSX_folder\fsdreamteam\Couatl\couatl.exe
\Your_FSX_folder\bglmanx.dll
- Have you seen any error messages when installing the Addon Manager ?
-
Hi Virtualy
Thank you for your support!
Before answering to your questions here the following message I've got when trying to install a scenery :
(Antivirus is deactivated)
runtime error at 116:2188
error on line 0, position 0 the following tags haven't been closed : simbase document.
(when installing addon manager)
and this other one:
app.data/microsoft/fsx/exe.xml
error on line 0, position 0
the following tags haven't been closed : simbase document.
exe file has not been modified by the installer
(when installing LSGG FSX scenery)
Could you light my candle please?
thanks again
Phil
-
Download and install the current version of the Stand-Alone Addon Manager, after you installed the scenery, with the scenery installed.
No, it's not enough you just run the Addon Manager installer that you already have, you need to download it again, because its installer has just been updated yesterday, and will now propose to recreate a correct xml file for you, in case one with errors is found.
-
Thanks Umberto for your precious help
Everything is working fine now with the new installer addon manager
here the procedure which works fine:
1/install addon manager
2/install all utilities (fs copilot and so on)
3/reinstall addon manager
4/ don't forget to check fsx config because this file is modified (if you added some lines before)
I think its a question of hierarchy in the dll folder. Can we move the lines in this folder to attribute to each addon some priorities??
Thanks again for the quality of your support!
Its also why FSDT is number one of Fs products sceneries :)
Phil
-
I think its a question of hierarchy in the dll folder. Can we move the lines in this folder to attribute to each addon some priorities??
You can change the loading order by rearraning section but, it shouldn't be done normally, only in case one finds that the loading order matters to solve a possible conflict between modules.
-
Thanks Virtuali I will give it a shot!
KB
-
Well, I give up!!
I have been folowing this thread, as I have been plagued by the failure of FSX to load with the FSDT airports loaded. I do not have FSCopilot installed and have tried each remedy that has been suggested, all the no avail.
Today I noted the comment about an upgrade to the addon manager, so I have uninstalled everything, re-installed and then installed the stand alone addon manager, all separately and checked one at a time and still I get the failure to load due to FSX hanging after accepting the addon manager dll.
It is therefore with a heavy heart that I have finally decided to give up the struggle and remove all the FSDT products form my system.
Norman :(
-
You probably haven't tried all the remedies. So, let's start from scratch again, please follow every step:
- Go into Control Panel, remove the Addon Manager, if you have an entry for it.
- Go into the FSX folder, verify that ALL bglmanx.dll files AND all the bglmanx*.dat files have been really removed. If not, removed them manually.
- Reboot Windows. Yes, this IS important. Do it, please.
- Turn the Antvirus OFF. Yes, this IS important.
- Reinstall the Addon Manager using the stand-alone installer. Don't run FSX yet.
- Configure the antivirus to ignore the following files:
YourFSXFolder\bglmanx.dll
YourFSXFolder\fsdreamteam\Couatl\couatl.exe
- Open your FSX.CFG file, located at %APPDATA%\Microsoft\FSX, with Notepad.
- Look under the [Trusted] section, and remove ALL the lines that contains a reference to bglmanx.dll. The whole line. Save the file back, don't launch FSX yet.
- Launch FSX. At the request to Trust the Addon Manager, reply YES, to both question, the one by Windows and the one by FSX itself.
- If you get the error the 3rd party module can't be loaded, IGNORE IT, and ALLOW it to run, regardless of what it says. Don't worry if FSX crashes after having issued that message. It doens't matter.
- Keep trying and, allow 20-30 seconds between each tries. If after 3-4 times it's always the same, REBOOT Windows and try again. Yes, this IS important, do it please.
-
Well, there was almost no difference between what you have specified and what I have been doing. A couple of differences; firstly I have UAC permanently turned off and secondly I have an exemption for my Microsoft Flight Simulator X folder and all the folders and files it contains in my anti virus already.
However, I have now been through your procedure three times, with UAC turned on and off; with the virus exemptions you specified also added to my already general exemption and this time I deleted the file bglmanx_aerosoft, that I had not done before.
After about 20 to 25 restarts it still doesn't run!!
Norman
-
I have an exemption for my Microsoft Flight Simulator X folder and all the folders and files it contains in my anti virus already.
That's not enough. If you read my message carefully, this was just *one* of the two operations needed on the antivirus.
The other one was to turn it off entirely ( not just quit from its interface, you need to turn off the real-time protection options ) before reinstalling. This is important because, files are first copied to the Windows Temporary folder BEFORE they are copied in the FSX folder. So, just exempting the FSX folder from scanning it's not enough, because the antivirus might still interfere before the files get a chance to be copied there.
So please, be sure that you have any realtime protection option turned off in the antivirus, before reinstalling.
this time I deleted the file bglmanx_aerosoft, that I had not done before.
I'm sorry, but if you are saying this, there might be an issue. You shouldn't remove just 1 .dat file. In fact, the uninstaller will remove all of them: the bglmanx.dll and the 4 .dat files. You shouldn't had to remove just the bglmanx_aerosoft.dat file.
In fact, if you have mixed .dat files from different versions, you might get that error.
So, please, check again that you don't have ANY file named bglmanx* ( the 1 DLL and the 4 DAT ) in the FSX root folder, before reinstalling.
-
As an alternative, you can try to download the files manually, from the same location the installer use:
http://www.fsdreamteam.com/download/setup/bglmanx/bglmanx.dll
http://www.fsdreamteam.com/download/setup/bglmanx/bglmanx.dat
http://www.fsdreamteam.com/download/setup/bglmanx/bglmanx_fsdt.dat
http://www.fsdreamteam.com/download/setup/bglmanx/bglmanx_aerosoft.dat
http://www.fsdreamteam.com/download/setup/bglmanx/bglmanx_qwings.dat
Put them all in the main FSX folder, of course. If this works, then it's SURE it was the antivirus interfering.
-
Hi Virtuali,
The antivirus was completely disabled, I was only saying that I already have MSFS totally exempted. I don't know if it is relevant, but in past attempts to correct this problem, I have always seen that the aerosoft dat file did not uninstal, but thought nothing of it.
Anyway, many thaniks for those links, I will give them a try.
Norman
-
I don't know if it is relevant, but in past attempts to correct this problem, I have always seen that the aerosoft dat file did not uninstal, but thought nothing of it.
It's normal behavior for any installer that, during the default Uninstall process, only files that were installed by THAT installer, will be removed.
So, for example, if you installed Aerosoft FlorenceX (which installs the Addon Manager and the bglmanx_aerosoft.dat ) before an FSDT scenery, if you Uninstall the FSDT scenery, the bglmanx_aerosoft.dat file will not be removed, because it wasn't put there by the FSDT installer.
HOWEVER
This is the default Uninstall behavior if you don't do anything BUT, if you reply YES to the question "Do you want to remove the Addon Manager ?", ALL files relevant to it will be removed, regardless of what put them there, which is useful to clean up, and it's the reason why there's that question.
-
Sorry, Vituali, its still no go. I have downloaded the direct links and I still get the same result. I don't know for sure where the Aerosoft file came from, but I guess that it was their version of London City, which I uninstalled ages ago. Anyway, it isn't removed when you answer yes to the remove question in the uninstaller. The German Wings file is removed.
I think that I have had the same experience that most of the others have had. My first airport was Geneva and I had the problem with that product. Then I followed the advice given on this forum and all was fine for a while. I added further airports and everything was still fine. Then suddenly I began to get the dll warning message again and FSX shut down, but again after uninstalling and then re-installing Geneva the problem went away. Now it is some weeks ago that it has returned again, and I tried to repair by uninstalling JFK and then re-installing it, but to no avail. Since then I have simply answered no to the dll question and the sim runs well.
I accept that the cause is probably some other addon on my system, although the only dll files I have, apart from the default and FSDF files are for PMDG, LDS and FSUIPC. I do have aicarriers in the exe.dll file, but that also has been there for some time. I don't think that it is related to Win7 I beta tested the original betas and also the pre-release and I didn't have a problem then. It could be an update since, I don't know.
I do not want to waste any more of your time, and I thank you for the help you have given. I know from experience with UK2000 how difficult it can be to track down a problem on a users system via the forum. I will continue to monitor this thread in the hope that something else may show up.
Norman
-
I don't think that it is related to Win7
I don't think too, I always test each and every version of the Addon Manager before releasing, on two different machines, one with Vista x64, the other with Windows 7 x64, and there are no problems whatsoever with either, all using absolutely standard configs. Meaning, both DEP and UAC are turned on, as in default.
You can easily check if the problem is caused by an interaction with another module, by editing your
%APPDATA%\Microsoft\FSX\DLL.XML
file with Notepad, and put a
<Disabled>True</Disabled>
line ( it's normally set to false ), in each module's section, except of course the Addon Manager. This will allow you to momentarily load FSX with nothing except the Addon Manager, as a test.
-
Hi Virtuali,
Well, I think I have finally found a solution, though not the reason for the problem. I have changed the compatibility setting for FSX to Vista sp2 and I have not had the dll failure for 24 hours now. It soesn't work with any other compatibility setting.
It may, therefore, be a Win 7 problem after all, perhaps due to a upgrade, as was mentioned previously.
Norman
-
Strange because, if I set any of the Windows compatibility settings, I always get a crash on start. But, if it works for you, just leave it there.
-
I'll certainly leave it as it is, and thank you very much for your patience and help.
Norman