Well apparently releasing the fixes to turning off the vehicles which effect performance and the stairs which should have worked in day one for those of us who have bought your software is not a priority. What’s the point of your updater if you can’t update the software.
You don't seem to understand. It's not a matter of priority, we simply CANNOT release anything right now, until we'll release the GSX update and the new ecommerce update. And I think ( I THOUGHT ) to have explained this quite clearly but, apparently, not.
It's just that these two major things, the GSX update, and the Esellerate closure, are all happening at the same time.
Hooray your working on new features for your costumers but fail to support those who are using the current versions. Six months sitting on a fix, really? I thought FSLabs was bad about releasing updates.
Sorry if the update feels small to you. It's more like a remake, but it's FREE. It took more than expected, because we kept adding new things to it. Again, for FREE. This is not "a fix", it's an update that's even larger in content that the PAID L2 expansion. The installer grew from 1.0GB for the previous version, to two separate installers, one for FSX, and one for P3D4, with the total size almost tripled.
The community knows this is the norm for FSDT.
That's exactly the opposite. The community knows we supports our products with updates so constantly, and for so long ( GSX came in 2012 ), which is why this uncommonly long pause between update stick out precisely because of that.
At least you pushed out a solution so we could now fly from Europe to the US without CTD over Canada. Notice how I didn’t say fix even though it only effected GSX users.
I don't know what you are trying to say here but, apparently, you again seems to fail to understand what the problem was. As explained so many times, the SIM WAS CRASHING BY ITSELF. GSX did nothing wrong, it was only calling a simulator own internal API that, apparently, is bugged when flying over sparse areas.
This is of course clearly proven by how the so-called "fix" works. We haven't changed anything in the GSX code, other than stopping to call that SIMULATOR OWN API when cruising.
So, in fact, the problem is NOT "fixed in GSX" because, of course, GSX wasn't the cause. The problem is still there, and it can still happen, either with GSX if flying low, or with another other add-on that would do the same call but, I guess after seeing how users like you can be so easily MISLEAD assuming it's a GSX but "because it only affected GSX users.", but they are confusing the cause with the effect, a typical mistake.
The *cause* is the bug in the simulator that seems to have troubles when somebody ask for facilities in sparsely populated areas.
The *effect* was GSX that was unfairly accused of being causing this problem, when it was only calling a feature of the sim.