FSDreamTeam forum
Products Support => Houston KIAH Support FSX/P3D => Topic started by: streichholz on August 24, 2015, 01:20:07 pm
-
Hi, I recently upgraded with a fresh Win10 and Prepar3D v2.5 ...46 Hotfix and installed KIAH and some other FSDT Aiports. At KIAH I noticed groundtexture flickering. What I mean is the ground under the runway is shining through, but only in distance (very small distance).
It's the first time I have this. All other FSDT Airports are working well.
Here is a picture.
http://abload.de/img/2015-8-24_13-18-56-63lfsmz.png
-
Nothing ???
-
I tried to replicate your screenshot at the same position, but cannot see any flickering. See the attached screenshot.
What other addons you have installed, especially mesh ? Does the problem happens with those disabled ?
-
I have just FTX Global installed. All other airports (LAX, JFK ...) working well.
-
I have just FTX Global installed
Does the problem happens with this disabled ?
All other airports (LAX, JFK ...) working well.
That doesn't mean much: each area is different. Also, have you set the Mesh Resolution and Complexity as indicated in the Design Section of the KIAH manual, 10 m/pixel resolution and 100% complexity ?
-
Hello
I have the same problem.
The only Addon I have installed except Houston is FTX Global (without Vector), like Streichholz.
Here is a screenshot:
http://abload.de/img/2015-9-8_17-40-2-331q7shz.jpg (http://abload.de/img/2015-9-8_17-40-2-331q7shz.jpg)
I tried to set the texture resolution to 10 m/pixel, the scenery complexity slider is set to maximum.
Mesh Resolution is set to 10m
-
The only Addon I have installed except Houston is FTX Global (without Vector), like Streichholz.
Does it happen if you disable FTX Global ?
-
It's almost impossible to "disable" FTX Global as it's texture set that replaces default textures, not an add-one package that can be easily enabled\disabled. You either have FTX Global in your sim or not have it at all. I also have flickering with KIAH and FTX Global, but only under certain angles of view, so it's not bothering me much. However, a fix would be welcome at one point of time.
-
You either have FTX Global in your sim or not have it at all.
Then what you have to do to "not have it at all" ? Does it come with a proper uninstaller, or its installation cannot be undone without reinstalling FSX entirely ?
The reason for disabling it was to TEST if the issue was caused by it, not to suggest you must get rid of it permanently.
I also have flickering with KIAH and FTX Global, but only under certain angles of view, so it's not bothering me much. However, a fix would be welcome at one point of time.
After we'll asses if FTX Global is indeed the cause of the problem (or not), we might then start discussing who has to fix what and, how a fix could be done, and by whom.
In any case, one of our developers has FTX Global Base + FTX Vector, and he cannot see any flickering either. If you have a specific position when this happens, please indicate all the following:
- The Lat/Lon coordinates of your airplane
- The direction of view
- Your altitude
- Your zoom level
-
There is no uninstaller for FTX Global. It replaces the textures in your sim. I would have to reinstall the entire sim just to test if the flickering is gone without global. But the airport worked with Windows 7 and Global. I can set the settings in my sim according your manual but this doesn't help at all. It has no affect to the flickering.
It seems to appearing random for people.
Could a reinstallation of the scenery itself help, without downloading the latest AFCAD for it?
-
But the airport worked with Windows 7 and Global.
This clearly proves the scenery doesn't have anything to do with this, since the scenery files don't have any knowledge of the OS used. If you are sure you installed the exactly the SAME products into the sim, and you are SURE you are using exactly the same settings as in Windows 7, the only possible explanation left, is a video driver settings that is different in Windows 10.
In any case, I have Windows 10 too, and you can see from the screenshot I attached earlier, taken from roughly the same angle, I don't have any ground bleeding.
-
Yes, I'm using exactly the same settings without a problem in Win 7.
I never thought of the video driver. Maybe I should use a later version because I have the first came out for Win 10. Will try this.
-
Hello,
I am not having the same luck with Windows 7 64 bit and P3D v3.1. Whilst I have no runway bleed throughs when using FSX, I do have runway bleed throughs using P3D v3 and now again with P3D v3.1.
See attached screenshot.
Following the suggestion in this post, I have updated my NVIDIA drivers to the latest version. The situation is unchanged - a(http://[img])[/img]ny idea what I could try out to resolve this?
Falconrae
-
Any idea what I could try out to resolve this?
I'm sorry, but I can only confirm what I already replied before in this post. I cannot replicate the problem in P3D, see the screenshot:
http://www.fsdreamteam.com/forum/index.php/topic,12372.msg94038.html#msg94038
Don't know if this a difference in drivers between Windows 10 and Windows 7. Maybe it is, but unfortunately we no longer have any Windows 7 PC to test on.
-
Hi Umberto,
experienced this issue on my yesterdays flight, too. But after some investigation on that i meanwhile know why you can't
reproduce it yourself. It's not the operating system!
You need to install EZDOK for that. It depends on the view you have chosen.
If you chose native P3Dv.3.1 views it will not happen. If your EZDOK VC CAM is active you will experience flickering, too. (I've attached 2 screenshot to proof it, pls watch view indicator on the upper right of these pics)
I haven't approached all my airport since i've migrated to V3, but FSDT KIAH seems to be the first of all my airports which
seems to have troubles with EZDOK (Flightbeam, FlyTampa, T2G does not have any issues with EZDOK running with all their P3D compatible airports)
regards
PGB
-
You need to install EZDOK for that. It depends on the view you have chosen. If you chose native P3Dv.3.1 views it will not happen. If your EZDOK VC CAM is active you will experience flickering, too.
If it doesn't happen with default cameras, I'm afraid there's nothing we can do. HOWEVER, we made some fixes to support the new avatar mode, which will appear with the KMEM (but will affect all sceneries), so it's POSSIBLE this might improve other non-standard views too.
-
You need to install EZDOK for that. It depends on the view you have chosen. If you chose native P3Dv.3.1 views it will not happen. If your EZDOK VC CAM is active you will experience flickering, too.
If it doesn't happen with default cameras, I'm afraid there's nothing we can do. HOWEVER, we made some fixes to support the new avatar mode, which will appear with the KMEM (but will affect all sceneries), so it's POSSIBLE this might improve other non-standard views too.
I tried to watch how your other airports behave on that. So i went at least to KJFK, PHNL and CYVR. There is no issue with these airports in EZDOK CAM view. So i am personally just wondering why not here? What development detail FSDT KIAH airport could have, the others don't seem to have? (I don't believe in anomalies without reason :D)
In the long run i want to spare on EZDOK and looking forward to TrackIR to avoid such issues. Btw. EZDOK still doesn't like GSX without selecting GSX short-cut twice to get my keyboard buttons for EZDOK view back. Hope all the troubles will be gone, by changing to TrackIR.
regards
PGB
-
I tried to watch how your other airports behave on that. So i went at least to KJFK, PHNL and CYVR. There is no issue with these airports in EZDOK CAM view. So i am personally just wondering why not here? What development detail FSDT KIAH airport could have, the others don't seem to have?
KIAH is more precise with the ground/polygons altitude difference, so it will have way less issues with vehicles wheels sinking in the ground, which many users found annoying in the other sceneries. T
he downside of it, is that it requires more precision from the camera view, which is why you get some flickering with EZDOK CAM, which I guess is optimized for closer view.
-
Umberto,
so this will not be fixed then? That's a shame, because all your other airports work just fine using P3Dv3 and EZDok. And so do all airports of FlyTampa or Flightbeam for example. I really don't see why KIAH has to be different here. A fix would be highly appreciated.
Markus
-
so this will not be fixed
then? That's a shame, because all your other airports work just fine using P3Dv3 and EZDok.
You already asked this question, and I already replied in the post above. I'll repeat it again: KIAH is more precise with the ground/polygons altitude difference, so it will have way less issues with vehicles wheels sinking in the ground, which many users found annoying in the other sceneries.
The downside of it, is that it requires more precision from the camera view, which is why you get some flickering with EZDOK CAM, which I guess is optimized for closer view.
And so do all airports of FlyTampa or Flightbeam for example
FlyTampa still use the slow FS8 ground polygons, which are processed in realtime by the sim (that's why they are slower) to conform with the round earth, so they don't have this issue. You pay for this in fps cost.
Flightbeam used them too, but it's going to switch to the same method we use for his next sceneries, since he has access to our scripting engine, so it's possible he'll have issues with non-standard cameras too.
We are handling the Avatar mode separately, for example ( a fix which is still not released ), but we can't support *every* other possible camera configuration.
I really don't see why KIAH has to be different here. A fix would be highly appreciated.
The scenery works fine with default cameras, so there's really nothing to fix. You can probably fix it yourself by adjusting the clipping parameters in the EZDOK custom cameras configuration.