FSDreamTeam forum
Products Support => Dallas FSX/P3D => Topic started by: Andi on December 08, 2010, 06:37:57 pm
-
Hi!
I bought all FSDT Addons and in Dallas (FSX) I have a problem with the runways.
http://img820.imageshack.us/img820/2912/fsx2010120814554395.jpg (http://img820.imageshack.us/img820/2912/fsx2010120814554395.jpg)
I have this problem on all runways with all aircrafts day and night in DFW.
Update 2.0 ist installed.
Do you know what to do?
-
Not a problem of the scenery but, most likely, a duplicate AFCAD for KDFW coming from another product, they usually come with AI traffic packages and, since are made for the default airports, must be removed when using with 3rd party airports.
To find AFCAD duplicates, you can use the free FSX Airport Scanner available here:
http://www.scruffyduckscenery.co.uk/ (click the "Download Center" link )
-
Thanks for your answer.
Can you please tell me how to use this.
-
Just launch the program, press the Scan button, and look for any duplicates for KDFW. The path field will indicate where each file is, when you select it.
You should remove only those files related to KDFW that are NOT in the fsdreamteam\kdfw path.
-
I ran the program but it didn't find anything.
So what else can I do?
-
Are you using the Mesh settings as suggested in the manual, which is Complexity at 100 and Resolution at 10m/pixel ?
Have you turned off Adaptive Anti Aliasing in your Video Card control panel (on an ATI it's called AAA, on nVidia is called "Transparency Antialiasing") , as suggested also in the manual ?
-
I have set all settings as suggested but nothing changed.
-
I'm sorry, but there are no other explanations, other than a different problem that happens on your system only, because nobody else has reported it.
What other sceneries you have installed for this area ?
-
Ultimate Terrain USA and Ground Environment USA,Canada,Alaska is installed.
After deactivating these addons nothing changed.
-
Does the problem happens at a specific place, or everywhere in the DFW airport area ?
-
It happens on all runways and taxiways.
-
Sorry, but we don't have any other explanation, other than this has been observed to be caused by Adaptive Anti Aliasing or Transparency Antialiasing, or possibly another scenery in conflict.
-
I have the demo and would like to purchase however I have this same issue - and will not purchase unfortunately until I can find a solution.. Have tried all of the above.
Here are some screenshots to hopefully help. It does not seem to be a scenery conflict error because sometimes it looks "normal" with the correct brownish/cement colour, then suddenly the grey runways "pop" in to the scenery view. See below
-
I have some more interesting observations, for the heck of it I put the siminto slew mode and took some screenshots.
Hope this helps you determine the problem as I really like the scenery otherwise!
Photos 1-3 below: Notice the ONLY thing I am doing is changing the zoom factor (I do not move an inch except changing zoom in simulator).
Photos 4-5 bleow: Shows what happens when I keep zoom factor the same but simply slew from point a to point b (just a bit west).
-
Not a problem of the scenery but, most likely, a duplicate AFCAD for KDFW coming from another product, they usually come with AI traffic packages and, since are made for the default airports, must be removed when using with 3rd party airports.
To find AFCAD duplicates, you can use the free FSX Airport Scanner available here:
http://www.scruffyduckscenery.co.uk/ (click the "Download Center" link )
Fact it's another AFCAD from another product in conflict, can be seen in your screenshot, because when the conflicting runway is visible, it has numbers, while the AFCAD that comes with KDFW doesn't have any numbers/markers, since the runways are fully custom so, it can only be another AFCAD from another product in conflict.
-
Not a problem of the scenery but, most likely, a duplicate AFCAD for KDFW coming from another product, they usually come with AI traffic packages and, since are made for the default airports, must be removed when using with 3rd party airports.
To find AFCAD duplicates, you can use the free FSX Airport Scanner available here:
http://www.scruffyduckscenery.co.uk/ (click the "Download Center" link )
Fact it's another AFCAD from another product in conflict, can be seen in your screenshot, because when the conflicting runway is visible, it has numbers, while the AFCAD that comes with KDFW doesn't have any numbers/markers, since the runways are fully custom so, it can only be another AFCAD from another product in conflict.
Thanks, I ran the program however it did not find duplicates..
-
Thanks, I ran the program however it did not find duplicates..
Tlittle, just a shot in the dark but you dont have "View Optimizations" checked in addon manager do you? It's in the lower right hand corner next to the Anti-popup and Altitude cull adjustments.
The reason I ask is because I was experimenting with that box checked not long ago to see if it made any performance difference and when flying around KDFW it made mine look like what your screen shots are showing as the ground textures would disappear then come back in. Once I unchecked that box it was back to normal.
The "View Optimizations" check box doesn't do this to the ground textures at other FSDT airports that I own, only at KDFW and I imagine that is just because the ground textures are rendered differently at KDFW that the other FSDT airports.
-
Thanks, I ran the program however it did not find duplicates..
Tlittle, just a shot in the dark but you dont have "View Optimizations" checked in addon manager do you? It's in the lower right hand corner next to the Anti-popup and Altitude cull adjustments.
The reason I ask is because I was experimenting with that box checked not long ago to see if it made any performance difference and when flying around KDFW it made mine look like what your screen shots are showing as the ground textures would disappear then come back in. Once I unchecked that box it was back to normal.
The "View Optimizations" check box doesn't do this to the ground textures at other FSDT airports that I own, only at KDFW and I imagine that is just because the ground textures are rendered differently at KDFW that the other FSDT airports.
I opened FSX, "View Optimizations" was unchecked. I tried to check it then looked, same problem. So I put it back as it was unchecked. Thanks anyway!
Virtuali I don't doubt that there might be an AFCAD somewhere since what you say about the runway numbers makes sense. But I just cannot find any other AFCAD? When the scenery loads initally I do see a grey runway WITHOUT the runway numbers, then as it loads the runway numbers come in. ALSO here's yet another possible CLUE - when the DEMO runs out the grey runway stays BUT the runway numbers disappear?
-
I am happy to report that I have resolved the issue.
I completely removed ALL FS DreamTeam demos I had i.e. Dallas, KORD, etc. then removed the addon manager and the coatl enigne. I then re-downloaded the latest addon manager and scenery ran addon manager installer first then all sceneries, and now all is good!
-
I completely removed ALL FS DreamTeam demos I had i.e. Dallas, KORD, etc. then removed the addon manager and the coatl enigne. I then re-downloaded the latest addon manager and scenery ran addon manager installer first then all sceneries, and now all is good!
It's possible that you move the scenery in the Scenery Library ? It should be at the top, which is were the installer automatically puts it. That's why it was fixed by reinstalling.
-
I completely removed ALL FS DreamTeam demos I had i.e. Dallas, KORD, etc. then removed the addon manager and the coatl enigne. I then re-downloaded the latest addon manager and scenery ran addon manager installer first then all sceneries, and now all is good!
It's possible that you move the scenery in the Scenery Library ? It should be at the top, which is were the installer automatically puts it. That's why it was fixed by reinstalling.
No that wasn't it either, I tried putting kdfw at #1 long before that thinking it may have been a layer issue. But for whatever reason uninstalling and reinstalling newest version worked ???