FSDreamTeam forum
Products Support => Dallas FSX/P3D => Topic started by: Michael_B767_ATP on August 10, 2010, 05:16:51 pm
-
Hi,
I've enclosed some screen shots showing some of the problems I'm having with KDFW. Shots 1, 2, 4 & 5 show taxiway lighting shift onto the taxiway as well as artifacts. Shots 3 & 6 shows FSX once it crashes when attempting to cross elevated taxiways A, B, Y & Z.
-------------------------------------------------------------------------------------------------------
NOTE: KDFW has the highest priority within FSX's scenery.cfg file / No other KDFW airport scenery installed
-------------------------------------------------------------------------------------------------------
(http://www.rmfc.us/photos/KDFW01.jpg)
(http://www.rmfc.us/photos/KDFW02.jpg)
(http://www.rmfc.us/photos/KDFW03.jpg)
------------------------------------------------------------------
The screen shots below show the same problems as the shots above
------------------------------------------------------------------
(http://www.rmfc.us/photos/KDFW04.jpg)
(http://www.rmfc.us/photos/KDFW05.jpg)
(http://www.rmfc.us/photos/KDFW06.jpg)
-
Michael,
I dont know if you have looked at my thread http://www.fsdreamteam.com/forum/index.php?topic=3350.0 , but I am also experiencing some of the same issues as you are, like the artifacts(bleed thru) and shifting of small objects, as well as some seams in the ground texture, like in your 2nd picture titled "taxiway A".
It seems that from what Umberto has said in my post at least, is that simconnect can get flooded and that it can create the problems in the ground textures because they are controlled by the addon manager. My scenery works fine until I have UT2 enabled and EZDok enabled, then addon manager and simconnect seem to get to much info to process and I start getting things like you are seeing. I am still testing on my end by enabling one module at a time to see which one causes the worst interaction.
I have also noticed that I get a lot of problems with this scenery when flying the LDS 767, which is my primary plane that I use in FSX. In my testing the last few days I have also noticed that the ground textures behave differently when I am using the LDS 767 with native FSX paints using .dds textures. If I use other LDS paints using .bmps originally for FS9 paints but work in FSX, then I seem to get more problems in the ground textures.
I am wondering if not only the simconnect flooding is causing these probelms but if there is an issue with the way some video cards handle these textures when mixed with other things using .bmp's, like the LDS 767 since everytime I fly a plane that has .bmp textures I get more issues at this airport.
Frankly, as much as I love what FSDT did at this airport, I fear that it is almost too advanced in it way it uses the gorund textures, because there seems to be no leeway if you load it up. I would be willing to go back to their older style of ground textures, even if they are lower res and have no specs or bumps, just to make it easier on the system.
I am confindent that FSDT will be able to help us get this straightened out. Although I will admit I will be disappointed if I can never get mine to work consistantly well depending on which addons I have running a the time. Plus if there are going to use these methods to texture the ground in all their new airports then I am afraid I will not be able to use them the way I want.
BTW, where are your terminals in the last pic?
-
cmpbllsjc, please, let me handle support, the problem Michael is having doesn't have anything to do with yours, this is something very specific to the elevated taxiways area, doesn't have anything to do with Simconnect or with other addons.
Michael, we have updated the scenery, can you see if the airplane crash is fixed with the 1.02 update we just posted here ?
Also, try to put your Mesh complexity slider at 10 m/pixel and not higher, it should fix the visual artifacts.
-
Hi,
Thanks, I'll give it a try.
-
cmpbllsjc, please, let me handle support, the problem Michael is having doesn't have anything to do with yours, this is something very specific to the elevated taxiways area, doesn't have anything to do with Simconnect or with other addons.
Sorry.
The only reason I spoke is cause it looked like some of the issue I had.
-
Hi,
Just installed the update (1.0.2.0), restarted FSX. Same problem as shown above, Artifacts, shifted taxi lights and aircraft crash when entering the elevated taxiway. This is with the Level-D 767.
Thanks
-
Have done this ?
Also, try to put your Mesh complexity slider at 10 m/pixel and not higher, it should fix the visual artifacts.
-
Hi,
I changed the mesh complexity slider just about all the way to the left, down to 10. The Artifacts are slightly reduced. Here is another screen shot of the level-D falling through the elevated taxiway. You can also see some artifacts.
(http://www.rmfc.us/photos/NewKDFW.jpg)
-
What other meshes have you installed ? This is what I see there:
-
Hi,
The only mesh I have installed is everything from FSGenesis (GalaxyPlus Lifetime Membership) for FSX.
1. Canada Terrain Mesh V1.0
2. Alaska-Hawaii Terrain Mesh V1
3. North America Terrain Mesh V2.02
4. Mexico Terrain Mesh V2.0
5. Northern Russia & Siberia Terrain mesh V1.0
6. United States Terrain Mesh (West Coast) V2
7. United States Terrain Mesh (Rockies) V2
8. United States Terrain Mesh (Plains) V2
9. United States Terrain Mesh (East Coast) V2
10. World Terrain Mesh V1.2
-
The only mesh I have installed is everything from FSGenesis (GalaxyPlus Lifetime Membership) for FSX.
Could you try to disable it, momentarily ? Just turn it off in the Scenery Library and restart FSX
-
Hi,
The only one listed in the Scenery Library is FSGNorthAtlantic, no other FSG Mesh is listed.
-
The only one listed in the Scenery Library is FSGNorthAtlantic, no other FSG Mesh is listed.
Is it possible they are installed in the Scenery\World\Scenery folder ? In that case, you should move the addon .BGL to a different folder (outside FSX) to disable them
-
Sorry for opening my mouth, but when reading the conversation between you two I think the dialogue has gotten skewed.
Umberto said to "put your Mesh complexity slider at 10 m/pixel and not higher." I think what he mean was put the Mesh Resolution slider at 10m.
Michael said "I set up the mesh just about all the way to the left, down to 10" which leads me to believe he lowered his Mesh Complexity to 10 since thats where it would be if he put it all the way to the left.
I think its supposed to be set like this:
Mesh Complexity 100
Mesh Resolution 10m
Sorry guys for butting in since Umberto told me to stay out and leave the support to him, but it looked like there was a misunderstanding in your conversation.
I wont say another word.
-
Hi,
I removed all FSGenesis.bgl files from the Scenery\World\Scenery FSX sub folder and restarted FSX, same problem. So I put everything back into the mentioned folder and tried the following.
Since the original setting change of Mesh Complexity to 10 did not fix the problem, I thought I would try cmpbllsjc's change of Mesh Resolution to 10m, keeping the Mesh Complexity at 100. That got rid of the artifacts and I am now able to taxi across all elevated taxiways.
The only thing I still notice is the taxi lighting on four out of the six elevated taxiways are shifted onto the taxiway.
(http://www.rmfc.us/photos/NewKDFW1.jpg)
Thanks for the help
-
Yes, sorry I should have said "Mesh resolution", which is measured in m/pixel, not Complexity, which is a linear value from 0 to 100.
The issue is, my current FSX install is in Italian so, when I name a setting for FSX in English, I need to guess what the English term for what I read in Italian might be.
-
I'm glad it worked Michael.
Frankly I was scared to say anything since Umberto said to leave it to him, but it looked like some of the words were mixed around and I couldn't help but open my mouth.
I almost created another account to say something so Umberto wouldn't know it was me, lol.
-
I'm glad it worked Michael.
Frankly I was scared to say anything since Umberto said to leave it to him, but it looked like some of the words were mixed around and I couldn't help but open my mouth.
I almost created another account to say something so Umberto wouldn't know it was me, lol.
lol Sean he would know it was you from the ip address lol. :D thats the problem with having so many add-ons it causes to many problems.
-
So I see the same artifacts but my mesh resolution is all the way to 1m. Should I dial that back to 10m? Ive only flown in DFW with the MADDOG2008 so far. I am also getting random FSX crashes ever since I installed the DFW scenery but its been happening not locally to DFW, but mostly at DFW so I can't truly link it to the DFW package.
Chris Lezama
-
So I see the same artifacts but my mesh resolution is all the way to 1m. Should I dial that back to 10m?
We usually test it at 10m but, it should work with higher settings as well. However, having 10m resolution it's not enough, you also have to set the Mesh Complexity to 100.
its been happening not locally to DFW, but mostly at DFW so I can't truly link it to the DFW package.
If you are having crashes outside 16 nm from KDFW, then you can be sure it's nothing related to it because, nothing of KDFW is loaded after that distance.
-
I had it maxed out at 1m with the mesh complexity maxed to 100 as well and I was seeing these artifacts. I moved the slider to 10m and the artifacts dissappeared.
Don't know why im getting these crashes, they are quite annoying, but I will keep looking for an answer... somewhere... :(
-
So i tried to start a flight at DFW with the MADDOG2008 about 5 times tonight and couldnt even get off the gate before FS crashed on me, usually with it saying FSX had a fatal error. I have never seen this before. Thinking back to the other FSX crashes I experienced since i installed DFW, the majority of them were at DFW, or in the air while DFW was in range. The others were in range of other FSDreamteam sceneries (KORD, KLAS).
After the 5th try tonight, i decided to try the reverse route. Loaded up at LGA and flew down to DFW. The flight was uneventful until DFW came in range and loaded up. Then my soundcard went wacky, weird noises started the play like my sound card was crapping out on me. Then it went silent. I was able to complete the flight without FSX crashing on me, but i was soundless the rest of the way into landing and parking.
I am also using FS2Crew Maddog Voice Commander. Since I am experiencing these crashes around FSDT sceneries, maybe its something installed with DFW that is common among the other sceneries that could be causing my crashes? I do not know how to determine what that would be. Any help would be appreciated!
Chris
-
The usual answer is always:
have you tried with a DEFAULT airplane ? This should always be the first step, when trying to understand if a *scenery* has a problem: excluding the airplane first.