General Category > General Discussion

Addon Manager **SOLVED**

<< < (9/14) > >>

Kevin:
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

allybear21:
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!

virtuali:
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.

allybear21:
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!

virtuali:

--- Quote from: allybear21 on January 25, 2010, 01:02:56 pm ---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.
--- End quote ---

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.


--- Quote ---Now, it does not work at all.  I have uninstalled FSCOPILOT and FSINN and it still will not open up FSX.  
--- End quote ---

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.


--- Quote ---Your solution of blaming everything on FSCOPILOT is unacceptable!
--- End quote ---

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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version