Originally you stated it was my system which was the issue at KDFW but it was fixed with an update not by changing anything regarding my setup
Yes, it WAS your system, fact that we were able to fix it on your system by changing the scenery, doesn't mean it wasn't your system that had the problem in the first place.
KDFW, initially, used Simconnect to handle the ground scenery and, on SOME systems (very few, including yours), because of OTHER addons (like UT2, but not only) clobbering Simconnect with too many commands in a short time, made difficult for our module to "talk" with FSX with enough speed in order to handle the ground scenery without flickering. Under normal circumstances, this shouldn't happen.
What we changed in the KDFW update, was to use a different method which was NOT relying on Simconnect anymore, so it would work even if *other* addons were flooding Simconnect with commands.
I've written this explanation, so you don't have the wrong impression that we "fixed" the scenery, because there was nothing to fix in the first place, we only made more resilient to problems created by *other* addons that used Simconnect in the wrong way, and created the flickering on some systems.
You stated the Autogen Fix would not fix the flckering/texture bleedthrough but to try it anyway. What is the value to try another fix which will do nothing for the issue I have?
I've said THAT Autogen fix, the first one that can be downloaded in the OTHER thread, would not do anything for the flickering.
THIS new file, even if it's named "Autogen fix 2", it's a different file, which INCLUDES the previous Autogen fix (that's why is named that way), but it WILL (or at least it should) also improve the flickering. If it wasn't, I wouldn't have said:
try the updated file attached here, it would be helpful to know if it improve the flickering
in my previous message.
So please, TRY the updated file, and report of ANY difference.
If an update is on the horizon which will fix the problem I have fantastic, if not no worries.
The update will be much larger, this is just a small part of it, that covers minor issues like the Autogen exclusion and (hopefully) the flickering.
I have airports from FSDT, Aerosoft, UK2000 and Fly Tampa. All work well on my system so I wonder what you mean by "That doesn't make any sense, since if the problem is something else, it won't be fixed by using another airport, you would just waste double the money, without knowing what was the real cause of the problem."
We were discussing about ZURICH. If there's a problem in the Zurich AREA (like a conflicting scenery or a setting) , which is specific to your configuration, it won't be fixed using a *different* scenery for Zurich.
