The problem is that this update(s) for some reason it(they) deactivated QUATL and I had to reinstall manually each time.
No, it didn't. I can't possibly know why it happened on your system, perhaps a problem with the antivirus or a bad download, but it surely doesn't deactivate anything. There might be another reason too, read further.
Indeed, I had done the 1.9 install and following this the next update (before 14th Dec.) required a standalone installer update. Thats what I did and then yesterday it asked again for standalone installer.
As I've said, the two last updates were spaced 15 days from each other, which is an unusually short time, because they are usually spaced months apart, but there there wasn't any other way to do the separate caches feature.
This is of course a feature that only concerns users with BOTH FSX and Prepar3D installed on the same system so, if you weren't in that situation, by reading the release notes, you could have decided to skip that update.
In my Windows7 Home 64 I am admin, so its not an issue related to this.
What this has anything to do with it ? I'm saying that everything you reported is NORMAL, except the fact that the "Stand-Alone disables Couatl", which is not the case, and if it happens on *your* system, it's entirely unrelated to the fact you are admin or not.
In each of the updates above FSX.cfg was updated because I had to approve on FSX boot the new file to run there where FSX asks you about new DLLs etc.
And why you think this might be a "problem", or an indication of it ? A Major update IS, by definition, an update which updates an executable, either a .DLL or an .EXE or a .GAU and when updated executables are launched for the first time, FSX WILL require you to trust them and WILL save your trust preference in the FSX.CFG. That's how FSX works, for every executable of every developer.
In addition to that, when you Uninstall and reply YES to the questions "Do you want to remove the Addon Manage ? " and Couatl, the Uninstaller will remove every line belonging to the Addon Manager and Couatl in your FSX.CFG, so it's entirely normal it would be changed in this case too.
Umberto I say this because I observe in many support posts a pattern of replies around this. The most usual reply is back up and delete your FSX.CFG and run FSX with a fresh one.
You might have observed the reply, but have you read the *question* too ? This reply is the one that is being given ONLY in these case:
- Objects that disappears when getting close, or objects that have parts of them invisible, or where you can see their sounds (so the objects are there) but not object.
- Other add-ons or the user) having wrongly removed the default SimObjectsPaths line for the default Misc folder, so none objects will be found, because they are installed there, in a folder and a line that must be normally present in every FSX installation.
This is the ONLY case where the reply about resetting the FSX.CFG is ever given.
Something does not register in these installations and QUATL/GSX asks for update and when updated it deactivates GSX and I have to do manual full GSX uninstall and full installer install from beginning. Thats what I did yesterday and it worked but its irritating to do this every time !
This doesn't have anything to do with the installer. It's instead possible that you have a problem with one version of the several VC++ 2005 runtimes that might be installed on a system. There might be many different versions of the VC++ 2005 runtimes installed, and some users have ONE version missing/corrupted and other users might have ANOTHER one.
Since we can't possibly anticipate which one might be missing/corrupted on any given user's system, we have two *slightly* different version of the Addon Manager, one that requires one build of the VC++ 2005 runtimes, another which requires another one. One is downloaded by the full installers, the other by the Stand-Alone Addon Manager installer, assuming that is *very* unlikely that an user would have BOTH of them missing/corrupted, it's expected that at least one of them would work.
In your case, it looks like you have a problem with the version of the VC++ 2005 library that is used by the Stand-Alone Addon Manager version, but the one used by the full installer is working. Other users might have the opposite problem. Most of them (which is the normal situation) don't have any problems with either, so they won't see any difference using one or the other.
So, you are mislead thinking the Stand-Alone Addon Manager "disables" something, when in fact it's only EXPOSING a problem with your system that you already had.
Yes, both the Stand-Alone Addon Mananger AND the full installer installs the CORRECT version of the VC++ 2005 library THEY need, and they do this by launching the official MS installer for those libraries, but sometimes the MS installer cannot fix all problems, so we are forced to use this solution, hoping that at least ONE of them will work.
In 1.9 I followed the instructions and actually did a full uninstall and full install with full installer, not just the standalone.
Then it should have worked. No reason why it would't, and if it happens again, please report it, so we can check why it didn't work on your specific case.
I really appreciate a working team responding so fast to user feedback and issuing updates. You are the only one I have seen work this way and congratulations but in my case the interim updates of standalone installer updates deactivate the product. The small updates that run within FSX by QUATL don't, these are OK.
Could it be related to what I document here ?
http://www.fsdreamteam.com/forum/index.php/topic,11228.0.html
Surely not. The AFCADs are just the airport definitions, and it doesn't make any difference to the program if you update them or not. If you don't edit AFCADs, always reply YES.
It does not mention which not installed product.
It will automatically look which FSDT sceneries you have, and download updated AFCAD JUST for those you have installed.
The only not installed product I have is the old JFK for FSX I had bought before buying v2 (and update to 2.1).
Could that be the cause of my standalone installer installation deactivating QUATL after installation ?
Obviously not. I already indicated a possible reason above.
