Understandably its hard to fix something you cant reproduce on your end, but I though I would ask anyway since you couldn't reproduce the KDFW ground texture problems I was having back when KDFW launched, but you guys found a solution anyways.
That problem was entirely different, because even if we can't reproduce it, it was possible to identify the problem, which was caused by *other* addons saturating Simconnect with commands, so we could find another solution by bypassing Simconnect.
In this case, Simconnect is not involved, and I don't think other addons are interfering (maybe not directly, just taking too much video memory, which can be corrupted), it's most likely a video driver bug we don't have much control on it.
It's not as easy as to just remove the object from disk, because this will introduce stuttering, since this is what happens when an non-existing object is being created.
Ok, I understand that.
If for some reason I decided to revert back to my old version can I simply just unistall version 2.0 and then run the old installer to put it back? Or, since I made a backup of my last version (scenery/texture folders) can I just remove the 2.0 scenery/texture folders and replace them with the older one?
If I have to actually uninstall 2.0 and run the older installer V.1.3.2.0 and the update to it v.1.5.1.0, do I need to download and install the addon manager again?
Thanks for the help.
I fly a lot with the Zürich scenery, so this weekend I use the scenery for my test flight of the new PMDG 737NGX. I never once had the pole issue show itself in all the local flights with the NGX. I have an Nvida 460 with drivers from last October.
Yes it weird that I should have that problem. I run a very clean system, tweaked and setup by FS-GS, not a lot of misc addons beside a/c and scenery, plus just rebuilt the cfg and reinstalled drivers. That's the hard part about this hobby with everyone running either XP, Vista, or Win7 and/or 32 bit or 64 versions, ATI or nVidia cards, plus hundred or thousands of possible combinations of drivers mixed with OS'es, it hard to believe that anything works, lol.
I pretty much have no issues with any FSDT, FlyTampa, or any other sceneries I own when it comes to graphic anomalies, but every now and then something like this will pop up.