As much as I love FSDT's products I definitely hate when couatl gives me problems. I reformatted my computer in anticipation for the PMDG 777 a couple of weeks ago and for some reason when I went to deactivate/activate all my products I kept getting esellerate errors. I posted on the forum and I was told it was my computer and I should disable a whole bunch of things even though other people I know where having the same exact issue.

 

 

I had to reinstall GSX also because the latest update un-registered GSX.

Ditto

 

 

As much as I love FSDT's products I definitely hate when couatl gives me problems. I reformatted my computer in anticipation for the PMDG 777 a couple of weeks ago and for some reason when I went to deactivate/activate all my products I kept getting esellerate errors

I did exactly the very same. And, moreover, where I had all 7 of my FSDT airport add-ons plus GSX working perfectly, all of a sudden when the option after installing into FSX comes up to activate, and where it previously did this seamlessly including saving the registry entries, this time I was taken to a screen where I had to email them my activation/order code, and they in turn sent me the same digits to be inserted into the activation boxes. Back to square one! Not really helpful or seamless.

Umberto is one of the best and most patient devs out there when it comes to trouble shooting problems that crop up from time to time.

 

He is responsive, but sometimes I don't think he always understands the issues with the Add-On Manager being reported to him.  There is definitely a "problem" with the Add-On Manager and/or the updates themselves but Umberto keeps insisting there is "no problem", so I was not really getting anywhere with him ... he gets a little defensive when I'm really only trying to help him.

 

The last two "updates" have caused problems with all my other products under the COUATL (add-on manager) umbrella ... I'm at the point where I select "Ignore Updates" whenever I'm prompted.

 

I think part of the problem is indeed OS security context, the COUATL.EXE is lunched by FSX, so it's under the security context of FSX.  Yes it's a separate process/application, but it's still bound to the security context of the application that initiated the instance (aka FSX).  So if the Add-On manager tries to write to directories it's not supposed to under the FSX security context, it will fail.  And what might make this problem difficult to "debug" is that it maybe a recent Microsoft OS security update that is now preventing certain activity that was permitted before.  The sad part about MS OS is that the event log (Event Viewer - Windows Log - Security) doesn't seem to log file access attempts that the OS rejects because of the wrong security context even when I'm viewing as Admin.

 

I feel for Umberto, but I'm not actually sure he is listening to what many of us are reporting.

 

Rob

I often get messages to update the addon manager on start-up, don't you?

 

 

The last two "updates" have caused problems with all my other products under the COUATL (add-on manager) umbrella ... I'm at the point where I select "Ignore Updates" whenever I'm prompted.

After having issues with the last Update whereby I had to completely uninstall/re-install GSX, this time I went back to one that was before the last 2 Updates. Not only could I hear the cabin crew welcoming pax aboard which the last 2 Updates for some reason deleted, but an issue related in another thread----namely as soon as the push-truck disconnected, the GSU and chocks did not suddenly kick in----so I feel in a mind to do exactly as you. Ignore those Updates.

GSX, nearly ready to uninstall it for all of the above reasons, I would like to know if anybody else hears the continuous pushback truck engine noise all the way to taxing onto the runway.

Cheers Rod.

It would be really nice if the developer took notice of threads like this.  As is often the case, there's hardly one possitive comment about couatl among these posts, yet hardly anything changes.  It can't be ALL our machines that are at fault surely;-)

 

Of all my FSDT software, I have NOT ONE installed.  What a waste:-(

Perhaps he could take notice if these concerns were posted on the FSDT support forum here: http://www.fsdreamteam.com/forum/index.php

Perhaps he could take notice if these concerns were posted on the FSDT support forum here: http://www.fsdreamteam.com/forum/index.php

What's the purpose? As was pointed out by robains, Umberto takes no notice of errors highlighted. And more to the point,why is that piece of software that uses a built-in method(eSellerate) of validating purchases then requires one when re-installing a previously-purchased add-on scenery to go through the hoops of sending an email with the order code, then wait for the activation key, then waste time copy/pasting each of those activation key boxes?

Sadly, I've bought my last FSDT airport.  Its SUCH a shame as they're of such high quality.

 

 

And more to the point,why is that piece of software that uses a built-in method(eSellerate) of validating purchases then requires one when re-installing a previously-purchased add-on scenery to go through the hoops of sending an email with the order code, then wait for the activation key, then waste time copy/pasting each of those activation key boxes?

 

The down side off piracy protection i guess. Though i havent experinced any off issues with couatl engine mentioned above, i am sometimes experienceing partially missing terminal and airport buildings at the FSDT and FlightBeam airports.

What's the purpose? As was pointed out by robains, Umberto takes no notice of errors highlighted. And more to the point,why is that piece of software that uses a built-in method(eSellerate) of validating purchases then requires one when re-installing a previously-purchased add-on scenery to go through the hoops of sending an email with the order code, then wait for the activation key, then waste time copy/pasting each of those activation key boxes?

 

Unfortunately, I can't answer any of your questions, because I've never experienced any of those issues.  And I've done several reinstalls without having to dig up my activation keys (assuming I haven't reinstalled Windows...).

 

I've found Umberto to be, yes, terse, but ultimately responsive to concerns raised on his support forum. I'm sorry others believe otherwise.

It would be really nice if the developer took notice of threads like this. As is often the case, there's hardly one possitive comment about couatl among these posts, yet hardly anything changes

 

+1  ... I would like to see some real change also, clearly a problem does exist and it's going to take more than the developer just responding but actually doing something to identify and correct.

 

I'm guessing the person that produced the Add-On manager (Umberto) is NOT the same as the people producing the products under it's "control" so to speak.  So obviously there is some tension there and the need to say "everything is perfect" as I'm sure the FSDT developers don't want to see less sales because of a problematic Add-On manager.

 

As a developer of non-FSX products, I've gotten stuck in the very same process (finger point across development teams), and in all cases I sucked it up and took on the challenge that ultimately wasn't my problem, but the end result was a happy client once problem was identified and fixed.  The problem here, we're not getting anyone to attempt to "identify" the problem (aka duplicate it) - so we're stuck.  My options now are not buy FSDT products and go with other products, an option I'd rather not have to do because of a problematic Add-On manager.

 

Rob

I hate the addon manager's initial pause and stutters that it creates, but I love FSDT airports so I deal with it.

+1 ... I would like to see some real change also, clearly a problem does exist and it's going to take more than the developer just responding but actually doing something to identify and correct.

 

I'm guessing the person that produced the Add-On manager (Umberto) is NOT the same as the people producing the products under it's "control" so to speak. So obviously there is some tension there and the need to say "everything is perfect" as I'm sure the FSDT developers don't want to see less sales because of a problematic Add-On manager.

 

As a developer of non-FSX products, I've gotten stuck in the very same process (finger point across development teams), and in all cases I sucked it up and took on the challenge that ultimately wasn't my problem, but the end result was a happy client once problem was identified and fixed. The problem here, we're not getting anyone to attempt to "identify" the problem (aka duplicate it) - so we're stuck. My options now are not buy FSDT products and go with other products, an option I'd rather not have to do because of a problematic Add-On manager.

 

Rob

Although I've not had an issue recently, I too, have had problems with Add-on Manager. I totally agree with you that someone needs to stop abdicating responsibility and acknowledge that an issue exists. Perhaps if everyone takes the path your suggesting and profits start to diminish, someone will take action.

 

The FPS (finger pointing scenario) is all too common regardless of what line of business your in, and it's always the end user that suffers. What companies don't seem to comprehend is that, because of this issue, that would eat into their schedules, that they can fob off so easily, will, if left unresolved, lead to people making choices as per your post.