You were wrong all along
It wasn't caused by a "problem" in our software. That what I was saying all along. You said you were sure it was a problem with our coding, which wasn't the case.
It was never the other add-ons as you kept insisting.
The Orbx issue was just one of the possible causes I indicated.
I added a 2nd one, the outdated Addon Manager, and since this wasn't either, the only possible explanation left, was that sim itself reporting a standard documented variable in the wrong way. Since I was *sure* there was no bug in our software (because it WAS fixed in the June 15th update!!), the only possible explanation left, was a bug in the sim.
And in fact, that's exactly what is happening.
That said, I'm curious about something now. In your own words, you said that you can guarantee that FSDT products work fine with a fresh install of FSX and P3D. Well, now that you know the real cause of this issue, do you still stand behind those words or do you now blame P3D for being the cause?
Sure. By default, the Avatar mode is Enabled, so on a default installation, you should never come across with that specific P3D bug and, of course, we assumed that, since one of KMEM most prominent features was the support for it, users would have it enabled it, which is the default setting.
Anyway, congratulations again on solving this mystery and I guess this matter is now closed.
I thank you for your insistence too, which lead me to research into the "impossible" ( a P3D bug ), since we seemed to have exhausted all the "possible" options.
I also reported the issue in the LM support forum:
http://www.prepar3d.com/forum/viewtopic.php?f=6310&t=122196So, hopefully, if they fix it, it would never happen again, that a customer using KMEM with the Avatar disabled, won't mistakenly assume there's a problem with it, when in fact it's a P3D bug.
And yes, just in case LM won't fix it, we already have an alternative solution ready, which is hacking into the sim to check if the Avatar is disabled, but I rather not using it, both because it's a potentially messy solution that would require updating the Addon Manager for each new build of the sim, and in general I would rather stay away from using undocumented features and direct memory access. This because the sim doesn't tell us (using documented methods) if the Avatar is disabled, so we cannot know for certain if we can rely on the value of the official variable.
So, the best solution would be that LM would fix it on their side, also because OTHER addons might also need to rely on that value to be correct, so something else out there might have issues if it's relying on the sim to provide the correct information about the avatar status.