Does anyone understand the continued use of the "Addon Manager" that Cloud9 uses? A constant pain in the "you know what" every time someone wants to install an aircraft (F4, MB339, F-104 specifically).
"Virtuali" explains (he's the originator of the program) that it's required to update the aircraft with the latest gauge and file information. What is it updating. . .the aircraft have been out for years, development is no longer being done on those airplanes. . .what in the world could it be updating? Is there some little gremlin over at Cloud9 that periodically changes a bitmap in the gau file? Does he move coding around just to maintain his job security? Somebody please explain to me why aircraft that are 3 or four years old need to be updated everytime you reinstall them?
Why haven't the gau files, the bglman.dll and related module files and whatever else this antiquated mgr updates been made part of the installer and be done with the Addon Manager?
You might have surmised by now that I recently reinstalled the F4 Phantom, spurred on by the discussion about the Alphasim Phantoms. Here's the real kicker. . .I also had the MB339 installed and flying perfectly. After installing the Phantom, all the livery updates and the service pack update I had to run the addon Manager (it's required to download all those updates, don't ya know). . . .well now, not only does the F4 cause a CTD but so does the MB339. Yep gotta love the engenuity of the concept.
"Virtuali" explains (he's the originator of the program) that it's required to update the aircraft with the latest gauge and file information. What is it updating. . .the aircraft have been out for years, development is no longer being done on those airplanes. . .what in the world could it be updating? Is there some little gremlin over at Cloud9 that periodically changes a bitmap in the gau file? Does he move coding around just to maintain his job security? Somebody please explain to me why aircraft that are 3 or four years old need to be updated everytime you reinstall them?
Why haven't the gau files, the bglman.dll and related module files and whatever else this antiquated mgr updates been made part of the installer and be done with the Addon Manager?
You might have surmised by now that I recently reinstalled the F4 Phantom, spurred on by the discussion about the Alphasim Phantoms. Here's the real kicker. . .I also had the MB339 installed and flying perfectly. After installing the Phantom, all the livery updates and the service pack update I had to run the addon Manager (it's required to download all those updates, don't ya know). . . .well now, not only does the F4 cause a CTD but so does the MB339. Yep gotta love the engenuity of the concept.