So it seemed that when I started at DFW with the LDS 767 I had problem, but when I started at another airport and flew here no problem and this was done with the same settings.
Does it happen with a default airplane and with the Level-d module disabled ? Sorry, but there are no shortcuts, as soon as you find a possible issue, there's no other way, than isolate items one by one.
Having said that, what if there is no way to have all the modules turned on or some of them turned on and still get the ground to work ok because sim-connect is getting flooded?
First, we need to discover what module is flooding (if this is the issue) Simconnect. Once you know that, you'll have to decide if that module is worth more or less KDFW, and decide which one to use it.
I have a decent computer E8400 at 3.85 ghz, GTS 250 OC 1GB, 2 GB ram at 1088mhz and all the other FSDT sceneries work ok and I am getting good FPS here.
If Simconnect is really getting flooded (we still are not 100% sure), it's not really depending on hardware capabilities, it can happen with any system. Other FSDT sceneries doesn't have anything in common with KDFW, with regard to this issue.
Would it be possible to have some type of alternate ground textures that would work seperate from Simconnect so that for some of us who have lots of info going thru simconnect we can avoid this problem?
We don't use Simconnect for the ground just for run: until now, NO FSX scenery was ever be able be drawn using fully native FSX code, because it would simply flicker like mad. The Addon Manager use Simconnect just to solve that problem and without it, it wouldn't been possible to do that kind of ground in the first place, which is the one and only thing that makes KDFW running and looking so good in FSX, compared to all other sceneries (including our previous ones), with the aggravation than KDFW is so large that, if we had to use FS9 methods, it would looked far worse (blurrier than JFK, at least) and it would have been almost unflyable.
Prior to having all the stuff in the dll.xml and exe.xml turned off, I did have a marked improvement in the ground bleeds with the mesh.bgl removed so maybe a flatten would work better for some of us even if it means the PAPI's dont work correctly all the time?
The scenery can't just use a flatten, because it's not flat! It's fully 3d, a simple flatten would kill the mesh, which makes possible the elevated taxiways.
Frankly as much as I love this airport, I am scared that if I cant pinpoint which module or the amount of modules running that I and maybe others will be having this problem with the ground textures.
You CAN, if you simply follow my advice, and test every module one by one. DO NOT remove mesh.bgl, if you keep changing multiple variables, you'll never find the solution.
The problem these days is there are so many items running thru simconnect for me like Active Sky Advanced, Ultimate Traffic, Addon Manager, LDS 767, and maybe other things that I dont even know about that rely on simconnect.
What uses Simconnect, it's either in DLL.XML or EXE.XML so, it's no difficult at all finding it out. If a product uses Simconnect without being listed in the XML files, it's a module that requires the user to manually launching it so, it's not difficult to find either.
One last thing. Is there any particular order that the different addons should be listed in dll.xml that may make a difference as far as priority.
It doesn't make any difference in regard of Simconnect usage. There might be differences in compatilibility: some modules simply don't run if another module is loaded first. But that would simply kill one module. If they work, they will work just the same, regardless of the order.
