FSDreamTeam forum
Products Support => Honolulu FSX/P3D => Topic started by: 9Y-POS on March 21, 2010, 09:14:21 am
-
I have a fresh new install of both FSX and PHNL and i'm still having an issue of grass textures bleeding through 4R, it's pretty bad to the point where you can't see the runway at all.
Also have excessive shimmering on baggage carts, if i'm not mistaken wasn't this addressed in this latest update which i'm running 1.0.3?
I'm not using any mesh for the area either.
-
As was explained already, we just can't replicate this. I don't see any ground bleeding, either with the default mesh, or with the FS Genesis, provided the two mesh complexity sliders are set to 100, as explained in the patch readme.
However, the 100 level is needed only with the FS Genesis mesh, to allow our own higher-res mesh to be displayed and fix the FS Genesis one. With the default mesh, the mesh sliders can be set to lower values as well and, in both cases, there is no ground flickering or bleeding.
Note that, this can also an video drivers issue, like a problem with the Z-buffer settings, that might be either bugged in the drivers, or might have been wrongly set by some tweak utilities.
Also, remember the scenery is only compatible with DirectX 9.
-
Well i've done everything underscored by you not just in this post but another one that addresses the mesh issue and still the problem is there, not too sure what else can be done here?
Here's a shot
http://i255.photobucket.com/albums/hh157/stanmantt/FSDTPHNLR4.jpg (http://i255.photobucket.com/albums/hh157/stanmantt/FSDTPHNLR4.jpg)
Funny how this only happens on approach, it doesn't seem to rare it's ugly head when your leaving.
-
Can you check what happens if, when the problem surfaces, if you stop the sim in Slew mode and wait some time, if it goes away ?
-
Can you check what happens if, when the problem surfaces, if you stop the sim in Slew mode and wait some time, if it goes away ?
OK, so i tried what you suggested and "no can do" same problem the texture bleed just stays there.
-
Same Problem here...
-
I can only confirm, it doesn't happens here.
Note, this is not something that can be created only by another mesh. It can also be created by another AFCAD with a slightly different altitude.
Check you don't have any other AFCAD files for PHNL, other than the one we supply, and the MS default. If you have more than these two, remove all the extra. Also, check you are using the AFCAD as we supplied, not a modified version.
-
I can only confirm, it doesn't happens here.
Note, this is not something that can be created only by another mesh. It can also be created by another AFCAD with a slightly different altitude.
Check you don't have any other AFCAD files for PHNL, other than the one we supply, and the MS default. If you have more than these two, remove all the extra. Also, check you are using the AFCAD as we supplied, not a modified version.
I can absolutely confirm no other afcads, like i stated in an earlier post i have a brand new install from OS to FSX and i ran it w/ just FSDT sceneries that i purchased so i could elimante any conflicts, i don'teven have mesh for hawaii installed just AC and ai traffic, although i did notice that i have a new start location ever since installing My Traffic today. I even ran a tool for double afcads just in case but came up blank.
-
although i did notice that i have a new start location ever since installing My Traffic today.
Since the only place where a start location can be specified it's inside the AFCAD, if this has changed at PHNL after installing My Traffic, you have at least a duplicate AFCAD, which is the My Traffic AFCAD for PHNL, and it's taking precedence, otherwise you wouldn't had noticed the change of the start location.
If this has a even slightly different ground altitude than ours, it surely can create that problem.
-
Yes but i only installed MY Traffix this morning, this issue has been going on since i installed the PHNL scenery, long before My Traffic. You are right about afcads w/ My Traffic but it's been removed and still the problem persists.
-
That doesn't change the fact that now another AFCAD is taking precedence at PHNL. So, please, remove it and check again.
-
That doesn't change the fact that now another AFCAD is taking precedence at PHNL. So, please, remove it and check again.
so no double afcad, no mesh, and still texture bleeding persists, can an adjustment be made to the PHNL afcad "elevation" to try to eradicate this problem?
-
so no double afcad, no mesh, and still texture bleeding persists
These are just the most *common* causes. However, it can be also any BGL, not just an AFCAD, it would be enough if if contained only a single runway.
can an adjustment be made to the PHNL afcad "elevation" to try to eradicate this problem?
The PHNL afcad elevation is already correct, and there's also a VTP flatten which is also correct, and there's also a very high res mesh, which is entirely flat, to the corrected airport elevation. The mesh is even purposely set to be slightly *below* the airport elevation, in order to be sure to eliminate any mesh problems. Usually, you have these issue, when a mesh is exactly at the same airport elevation or slightly above, maybe only parts of it.
Also, you said yourself the problem doesn't appear when departing, only when landing.
If it was something wrong in the scenery, it should appear in both cases. There's no such thing as a "departing elevation" or "landing elevation". There's just *the* elevation, and it can be either always wrong, or always right. If it doesn't work in one direction only, it might be also an FSX bug that we can't do anything about it, as if not being able to load the hires mesh (it's 4.75 mt/pixels, but entirely flat of course) only when approaching.
-
Fresh install of FSX with Acceleration. Have FSG mesh, slider at 100. Only scenery for area is FSDT PHNL. I get this as well. Landed on 8L and expereienced this issue. Horrible looking bleed through. Never seen this with any other FSDT scenery. This is on Window 7 x64. No AI traffic either. I remember last year when Imaginesim came out with KATL. They had this issue with part of their scenery. I believe it was around runway 10/28. It got fixed but I don't remember how it was done. So this issue does crop up now and then.
Went back and found the post on avsim where afcad maker Jim Vile found the texture bleed through problem with KATL (its post # 115): http://forums1.avsim.net/index.php?showtopic=231498&view=findpost&p=1476646
-
Obvious question here: does it happen if you disable FSG Mesh ?
-
Went back and found the post on avsim where afcad maker Jim Vile found the texture bleed through problem with KATL (its post # 115):
Checked this and, it's not exactly the same issue, because both our main airport elevation and all the runways were set exactly to the same height to the latest decimal. However, they where both set at 12.9999 ft, and the flatten mesh we included with 1.0.3 patch is set at 13.018049ft so maybe the issue is similar.
I think it IS video-card dependent, because it might be related to the Z-buffer resolution.
Find attached a modified AFCAD, is exactly the same than the one that comes with the scenery, but the altititude is set to 13.2 ft, which should be enough.
Let me know how it works because, I can't see any difference with either AFCADs (I'm using an ATI, BTW)
-
Umberto,
Ok, will give this a try but likely will not be until Monday or Tuesday before I can test it. I also think this will fix the issue. BTW, I am using an ATI card as well. Two 1GB 5800 series cards.
-
It looks like it solved my problem.
-
OK i can report the issue is still there but not that much, it was a huge improvement. I can actually see the centreline of the runway now ;D I think with just a bit more tweeking, we should have perfection!
-
I get this as well. Landed on 8L and expereienced this issue. Horrible looking bleed through. Never seen this with any other FSDT scenery.
I just saw this for the first time last night. I was landing on 8L, and when I was about 50 feet from touchdown, the bleed through showed up, and followed me the length of runway, until I turned off. I don't have any other AFCADS, traffic apps, or mesh.
I'm running 1.03
I will try the modified AFCAD. By the way, I'm using an Nvidia card.
- John
-
I get this as well. Landed on 8L and expereienced this issue. Horrible looking bleed through. Never seen this with any other FSDT scenery.
I just saw this for the first time last night. I was landing on 8L, and when I was about 50 feet from touchdown, the bleed through showed up, and followed me the length of runway, until I turned off. I don't have any other AFCADS, traffic apps, or mesh.
I'm running 1.03
I will try the modified AFCAD. By the way, I'm using an Nvidia card.
- John
Ok, I have an update. I just tried again by going directly to PHNL starting at 8L. I don't see it now. I didn't update the AFCAD yet, but for some reason, I can't make it happen. The only difference between when I saw it yesterday, and now is that I flew a flight from KLAX to PHNL using the LDS 767. This time, I just went directly to the airport. Strange... I even have a screenshot from when it happened. See attached.
Thanks,
John
-
I get this as well. Landed on 8L and expereienced this issue. Horrible looking bleed through. Never seen this with any other FSDT scenery.
I just saw this for the first time last night. I was landing on 8L, and when I was about 50 feet from touchdown, the bleed through showed up, and followed me the length of runway, until I turned off. I don't have any other AFCADS, traffic apps, or mesh.
I'm running 1.03
I will try the modified AFCAD. By the way, I'm using an Nvidia card.
- John
Ok, I have an update. I just tried again by going directly to PHNL starting at 8L. I don't see it now. I didn't update the AFCAD yet, but for some reason, I can't make it happen. The only difference between when I saw it yesterday, and now is that I flew a flight from KLAX to PHNL using the LDS 767. This time, I just went directly to the airport. Strange... I even have a screenshot from when it happened. See attached.
Thanks,
John
That's the odd thing it only happens for the most part when you arrive at PHNL and not when you're leaving, dunno?
-
Ok, I have an update. I just tried again by going directly to PHNL starting at 8L. I don't see it now. I didn't update the AFCAD yet, but for some reason, I can't make it happen. The only difference between when I saw it yesterday, and now is that I flew a flight from KLAX to PHNL using the LDS 767. This time, I just went directly to the airport. Strange... I even have a screenshot from when it happened. See attached.
That's the odd thing it only happens for the most part when you arrive at PHNL and not when you're leaving, dunno?
Yes, that's what I was trying to say in a long winded way! Why does it only happen when arriving, and not when starting from PHNL? Thanks for making it simple.
John
-
Please, let's try not to digress: is everybody using the updated AFCAD ? Have you seen any difference ?
-
Please, let's try not to digress: is everybody using the updated AFCAD ? Have you seen any difference ?
Yes, i installed the updated afcad and there was a marked improvement, i'm hoping with a little more tweaking it would be perfect.
-
It looks like it solved my problem.
I have to report, that I still have the problem.
I noticed it landing on Runway 4R and at the Military-Apron.
I have an ATI, as well.
-
I have to report, that I still have the problem.
I noticed it landing on Runway 4R and at the Military-Apron.
As I've said, it's more important to know if you see a *difference*, compared to the normal version without the updated AFCAD
-
I have to report, that I still have the problem.
I noticed it landing on Runway 4R and at the Military-Apron.
As I've said, it's more important to know if you see a *difference*, compared to the normal version without the updated AFCAD
I installed the new AFCAD last night. The problem is (like we mentioned earlier), is that I don't see the bleeding on 8L when starting a flight from PHNL. The only time was after a flight from KLAX to PHNL. I will duplicate the flight to PHNL this weekend and see what happens.
Thanks
-
The problem is (like we mentioned earlier), is that I don't see the bleeding on 8L when starting a flight from PHNL.
Ok, this is interesting to know (although we don't have any idea why it would work on departing, and not on arriving) but, assumed the problems happens only when arriving, do you see any difference between the released version and the AFCAD posted on this thread ?
-
The problem is (like we mentioned earlier), is that I don't see the bleeding on 8L when starting a flight from PHNL.
Ok, this is interesting to know (although we don't have any idea why it would work on departing, and not on arriving) but, assumed the problems happens only when arriving, do you see any difference between the released version and the AFCAD posted on this thread ?
Ok, I just tested another flight with the new AFCAD, and the problem is still there. The AFCAD didn't make a difference for 8L. Again, it only happens when flying to PHNL, not starting from PHNL.
Any suggestions?
Thanks,
John
-
I landed on 8L yesterday coming from Tahiti and had the bleeding issue.
When I flew from Honolulu later that day from 8L she was fine.
-
I have an ATI card also with the most recent drivers. When I landed at about 150 knots I too had this bleed issue. I also noticed some large light grey flashes coming from the airport on the approach. JFK and ORD do not do this for me.
Thanks
-
I have an ATI card also with the most recent drivers. When I landed at about 150 knots I too had this bleed issue. I also noticed some large light grey flashes coming from the airport on the approach. JFK and ORD do not do this for me.
Thanks
I see a light grey cover on the airport on approach too but didn't quite no what it was, it's extremely noticeable at dusk and dawn, very pronounced at those times, definitely a common thread here if somehow we can just get down to the bottom of this issue ???
-
Seeing a flat grey polygon on approach, that will be eventually texture when closing down, it's normal, and it's not an indication of any problems.
-
FWIW, I too still see this green texture flickering through the runway texture when arriving on 08L. It doesn't appear until I'm actually on the ground after flying in from LAX unsing the PMDG 748i.
-
FWIW, I too still see this green texture flickering through the runway texture when arriving on 08L. It doesn't appear until I'm actually on the ground after flying in from LAX unsing the PMDG 748i.
Can you confirm that you don't see it if you start at 8L?
Thanks,
John
-
Umberto,
Any luck on tracking down the issue with 8L, and why it only happens when flying to PHNL?
Thanks,
John
-
Put the new AFCAD in, did not help at all. Landed on 4R and all I saw was the default ground textures until I taxied off the runway near the terminal. Horrible looking. Makes landing at PHNL useless.
-
Virtuali,
Do you have anything else we can test to see if we can solve the issue on 8L?
Thanks,
John
-
And it's weird too. Looking at the runway texture after landing with my PMDG 748i and remaining parked about 1/2 down 8L, as I panned around the aircraft in the outside view, only the portion of the runway directly underneath, or slightly in front of the aircraft conintued to flicker and blead through the concrete runway texture.
It's almost as if some kind of alpha channel texture conflict or something when close an aircaft. Why only after landing from a long trip to PHNL is what gets me. And after observing it for a good 5 minutes or so, I pulled off to the taxi-way and the flicker goes away from underneath the aircraft and is not observed on the taxi ways or tarmacs; only on the runway, directly under the bird.
-
And it's weird too. Looking at the runway texture after landing with my PMDG 748i and remaining parked about 1/2 down 8L, as I panned around the aircraft in the outside view, only the portion of the runway directly underneath, or slightly in front of the aircraft conintued to flicker and blead through the concrete runway texture.
It's almost as if some kind of alpha channel texture conflict or something when close an aircaft. Why only after landing from a long trip to PHNL is what gets me. And after observing it for a good 5 minutes or so, I pulled off to the taxi-way and the flicker goes away from underneath the aircraft and is not observed on the taxi ways or tarmacs; only on the runway, directly under the bird.
Yes, I concur with your observations. This is exactly what I'm seeing. I'm perplexed as to why it happens after a long trip as well. Very strange indeed. Try an island-hop from PHKO to PHNL, and see if it does it. I suspect it won't, but not sure yet.
Thanks for sharing.
- John
-
Ya know, my account just above was after testing an arrival with the 748i from a saved flight which begins just before the ToD, about 120nm to the northeast of Honolulu, down across the CHK arrival and back around into the 8L ILS. I now recall, that I had just finished completely rebuilding my rig, upgrading from WinXP_x64 to Win7_x64, and noticed the same issue before and after the upgrade. That's when I stopped on the runway to observe the flicker for quite some time - I was testing the rebuild using a saved-flight from about 100nm away, which was origionally created from a KLAX to PHNL flight a month or two earlier.
-
I'm getting the same texture issues. I get them on both 4's and 8L -haven't landed on 'water'. I get the issue even if my flight originates from a near by Island (phog or phto). To avoid the texture issue, I reload the scenery library before approach into PHNL. The funny thing is this; as long as the refreshed scenery library stays in memory I can travel the world and even exit FSX and return to PHNL and not have the texture issue, but if I reboot my puter and return to FSX the texture issue will return unless I again rebuild the scenery library.
-Ken C.
p.s. I use FSG Hawaii V2.1
-
To avoid the texture issue, I reload the scenery library before approach into PHNL.
You can try a similar solution: there's a command in FSX which is not assigned to any key by default, that is called "Refresh Scenery". You might assign it to a free key, like CTRL+SHIFT+R, which might be convienient to use when approaching, and see if it has the same effect.
-
Hello,
Has this issue been solved? I'm still having problems with runway bleed through. Presently I have v 1.0.3 installed with the file I downloaded from this thread. I also have fsgensis v2 installed along with FS Dreamscapes NEXTMap ProMesh Hawaii. Each time I fly a flight plan from KSFO to PHNL using LVLD 767 and the NEXTMap ProMesh Hawaii disabled from the scenery library I still get the bleed through on runways 04R and 08L when landing. My system, if it does matter is Win 7 64 bit, i7 920 OC to 4.0, evga GTX 285, and mushkin DDR3 1600 6 7 6 18.
Karl
-
Has this issue been solved?
Have you tried the suggestion posted in the previous post ?
-
Hello,
Thanks for your reply. I tried the suggestion by setting a button key for refresh scenery. When passing PERLY INT for runway 04R I refreshed the scenery by using the assigned button key but unfortunately when touching down on the runway the bleed through happened again. The NEXTMap ProMesh was disabled.
-
Try this, put the attached .BGL in the:
Scenery\World\Scenery
folder under FSX
-
I have an update. the bleeding issue on 8L only used to happen when taking a long flight (KLAX-PHNL). Last night, I took a short hop (PHKO-PHNL) via Japan Air flight 079. The bleeding issue occured. I see that there is a new .BGL I will try that to see if it helps.
- John
-
I had accomplished serveral test flights from KSFO to PHNL with the new BLG file. My first flight was with NEXTMap ProMesh and FSGenesis Alaska-Hawaii and Terrain Adjustment Pack uninstalled. I landed on 4R with no bleed through.
Next flight, I flew the same flight plan with all addon's installed and landed on 8L with no bleed throught on the runway but when approaching the runway the terrain in front of the runway started to bleed through.
I will keep on testing and post my results.
Karl
-
FWIW I just completed a KDFW PHNL onto 04R and had the green texture bleed through the RWY. But this is pretty much normal ops for PHNL on my machine. Keep hoping for a solution.
-
FWIW I just completed a KDFW PHNL onto 04R and had the green texture bleed through the RWY. But this is pretty much normal ops for PHNL on my machine. Keep hoping for a solution.
Just to let you know that flying a 763 im assuming they always land on 8L in HNL
-
FWIW I just completed a KDFW PHNL onto 04R and had the green texture bleed through the RWY. But this is pretty much normal ops for PHNL on my machine. Keep hoping for a solution.
Did you try the .bgl file that was posted the other day?
- John
-
FWIW I just completed a KDFW PHNL onto 04R and had the green texture bleed through the RWY. But this is pretty much normal ops for PHNL on my machine. Keep hoping for a solution.
Just to let you know that flying a 763 im assuming they always land on 8L in HNL
Yes, I fly the LDS 763, and see it when flying this A/C. I haven't tried the .BGL file yet. I will hopefully have time this week.
- John
-
I completed two flights from KSFO to PHNL, landing at ILS 08L and 04R using the addons FS Dreamscapes Hawaii NEXTMap ProMesh and FS Genesis Hawaii v2. With the new BGL file I no longer have bleed through on the runways. That being said there are still some issues with bleed through on the taxi ways and ground terrain. I added two youtube links to display the bleed through on landing at runways 08L & 04R.
-
I completed two flights from KSFO to PHNL, landing at ILS 08L and 04R using the addons FS Dreamscapes Hawaii NEXTMap ProMesh and FS Genesis Hawaii v2. With the new BGL file I no longer have bleed through on the runways. That being said there are still some issues with bleed through on the taxi ways and ground terrain. I added two youtube links to display the bleed through on landing at runways 08L & 04R.
Was the bleed through visable on the taxiways and ground terrain prior to the new .bgl?
- John
-
Was the bleed through visable on the taxiways and ground terrain prior to the new .bgl?
From what I recall there was no bleed through on the ground terrain. There was some bleed throught on the taxi way only when exiting the runway.
Karl
-
Will there be any further changes to the files?
Haven't heard anything in a while.
Karl
-
I have a theory.
Those of you that have the issue on 8L or 4R, please list what specific aircraft you were flying (i.e. LDS 767, PMDG 747, etc..). I want to see if this is happening only with specific aircraft. Conversely, we can try using the default A/C :o to see if the problem exists.
Thanks,
John
-
Try this, put the attached .BGL in the:
Scenery\World\Scenery
folder under FSX
Tried that file on a flight from LAX with the QW 752 and had no issues on landing. First time I landed on 8L without any bleeding issues.
-
I tried the .bgl file this weekend. I landed twice on 8L, and no bleeding issues so far. Crossing fingers..
- John
-
Havent encountered any problems with surface texture flickering with the new BGL posted in this thread.
-
The BGL fixed the bleeding on the runways but its still bleeding on the taxiways and on the grass on approach.
-
Yup, same thing here - on the approach grass and taxiways.
-
Yup, same thing here - on the approach grass and taxiways.
Same here for me as well but still a vast improvement to what was happening before, maybe a bit more tweaking and all will be well?
-
Yup, same thing here - on the approach grass and taxiways.
Same here for me as well but still a vast improvement to what was happening before, maybe a bit more tweaking and all will be well?
KCGB, Jordanal, 9Y-POS,
What Aircraft were you flying when you noticed the grass and taxiway bleed through? Just trying to see if there is a pattern.
Thanks,
John
-
IIRC, it was the PMDG 748i pax variant.
-
I've used quite a few, from the QW757, to CLS340 &320 to the AerosimL1011
-
And for me it's been the LDS 767 and the PMDG 747. Strangely enough when I flew the PIC737, the flickering and bleeding didn't happen. Since then I've applied the new .bgl.
- John