FSDreamTeam forum
FS9 support => Hawaiian Airports support FS9 => Topic started by: debutant on September 29, 2010, 05:23:00 pm
-
Hello, today I downloaded and installed hawai Volume 1 and I have a problem with the texture of the ground tracks of the Lihue Airport! sorry for my English!
thank you in advance for your help.
http://img692.imageshack.us/i/fs920100929164650731600.jpg/ (http://img692.imageshack.us/i/fs920100929164650731600.jpg/)
http://img186.imageshack.us/i/fs920100929164716711600.jpg/ (http://img186.imageshack.us/i/fs920100929164716711600.jpg/)
-
Hi
I got the same sort of problem when landing at the airport - the runway started to vanish in front of the plane and the tyres sank on the slipway until entering the parking area.. When I first explored the airport after purchasing it without taking off, there was a bump as I entered onto the runway and then again as I left it but at that time the runway was still visible.
I have checked and have no other AFCADs for this airport and have scenery set at default 19 with no mesh addons. Any ideas? Apart from that, superb scenery.
Regards
Rich
-
Hi
I got the same sort of problem when landing at the airport - the runway started to vanish in front of the plane and the tyres sank on the slipway until entering the parking area.. When I first explored the airport after purchasing it without taking off, there was a bump as I entered onto the runway and then again as I left it but at that time the runway was still visible.
I have checked and have no other AFCADs for this airport and have scenery set at default 19 with no mesh addons. Any ideas? Apart from that, superb scenery.
Regards
Rich
Rich which runway was it?
-
I have checked and have no other AFCADs for this airport and have scenery set at default 19 with no mesh addons
You mean the max vertex level in the FS9.CFG ? Try to set it at 21.
-
I have the same elevation issue at PHLI. Haven't seen any texture problems because of it, but there's a noticeable "bump" (big enough to reset the aircraft trim to 0, so FS thinks it's a "crash") when entering either runway from the adjacent taxiways.
-
If the FS9 version is setup like the FSX version, both runways at PHLI show an elevation of 154.2' vs. 153' for any taxiways. Thus the drop or sudden "chirp" from the tires when exiting.
-
Hi
Runway 21 I think, had the buildings on the right and turn off right taxiway to the gates. I will try the 21 max vertex level.
Cheers
Rich
-
Hi
Yep landed again at runway 21 and the same happened...it did not happen when I took off from PHLI, circled and landed on 21, just when I come from another airport. I get the call out 500 then the texture ahead starts to blur as I get nearer and goes ahead of me down the runway. Sounds like a problem Mexsim had with their MMAA product (the picture in the forum is the same as I am getting). The max vertex has been set at 21.
Cheers
Rich
-
Hi
Yep landed again at runway 21 and the same happened...it did not happen when I took off from PHLI, circled and landed on 21, just when I come from another airport. I get the call out 500 then the texture ahead starts to blur as I get nearer and goes ahead of me down the runway. Sounds like a problem Mexsim had with their MMAA product (the picture in the forum is the same as I am getting). The max vertex has been set at 21.
Cheers
Rich
I can also confirm the bump. As I was taxiing my little 732 onto rwy 3 at Lihue for my little photoshoot, it bumped up and got the smoke effects as well when it hit...
-
[EDIT: UPLOADING PICTURE LINKS]
Should give you an idea. On short final everything is clear and about 10 seconds before touchdown, the threshhold turns grey and moves to the oppsite end of the runway as you touchdown, all textures dissapear. And the aircraft BUMPED hard when I turned off leaving a lot of smoke behind. Also, when I move eyepoint upwards ALL airport ground textures dissapear. When I move the eyepoint back down, they reapear...
[TERRAIN]
TERRAIN_ERROR_FACTOR=100.000000
TERRAIN_MIN_DEM_AREA=10.000000
TERRAIN_MAX_DEM_AREA=100.000000
TERRAIN_MAX_VERTEX_LEVEL=21
TERRAIN_TEXTURE_SIZE_EXP=8
TERRAIN_AUTOGEN_DENSITY=5
TERRAIN_USE_GRADIENT_MAP=1
TERRAIN_EXTENDED_TEXTURES=1
TERRAIN_DEFAULT_RADIUS=9
TERRAIN_EXTENDED_RADIUS=9.5
TERRAIN_EXTENDED_LEVELS=5
-
Thank's for the description.
Just for info what other package you have installed, apart UT, any mesh ?
-
hello all, then I see that'm the only one having this problem! For my part, the problem is that I always put 21 or 19 it does not change! What should I do! :(
thank you all for your help
-
Thank's for the description.
Just for info what other package you have installed, apart UT, any mesh ?
No mesh or UT here. Just stock FS9. Hadn't noticed the texture problem until last night when flying in from PHNL, as it seems to happen only when flying in from another airport. I still have the "bump down" off both runways (17/35, 3/21) in any instance.
-
Hi Simbio!
In this area of the FS9 world is UT-USA, GE-PRO, FSG2010, and REX. Still working on the pictures to upload. I have a video if you want it. This is the first I noticed it as it was an actual flight and not slewing. I used Wilco CRJ direct from PHTO. newmanix
-
Hi Fabrizio,
because of the problems when flying into PHLI - I did some checks.
Your file for the airport (some would say AFCAD but you use ADE) uses the FS-standard altitude from PHLI, 153ft.
This is (checking it with AFX) 46.634 m
Your LWM-Poly type 2 under the airport is a little bit deeper, 46.625 m
No problem when starting at the airport - the fs engine use your lwm-altitude.
But if you fly to an airport, the altitude from the other source (the standard ap-files or your AFCAD) is used.
And that leeds to the "flickering" and disappearing of your ground textures while and after landing around the plane.
Technical description of lwmpoly2: (terrain vector data.doc - FS2004-SDK)
struct LWMPoly2
{
UINT8 bPointCount:6; // Up to 62 points
UINT8 bReserved:1; // Must be 0
UINT8 bAttrib:1; // Polygon fill attribute, 0 = water, 1 = land
SINT16 iHeight; // Whole elevation value in meters
UINT8 iFraction; // Fractional elevation value in 1/128 meters
};
With lwmviewer I'm able to see your source is used (compiled) with the parameters 46 , 80 at the end,
this is 46m + 80/128m = 46m + 0.625m = 46,625m
46,625 < 46,634 so the poly is underneath your AFCAD and the AFCAD-textures comes above when flying to the airport.
Could you please check this?
Ciao,
Rainer.
-
Having the same problem with the runway disappearing in front of you on landing.
-
I'm having the same problems when I land on Rwy 35. The runway disappears and the asphalt turns to ground. I did notice the bump when I taxied onto Rwy 35. I'm also having flickering issues with PHNL when I land and exit the runway. I wonder if the problems are related? I'm referring to a potential texture design problem and not PHNL caused the problem at PHLI. What's interesting, out of the three Hawaii airports, Hilo is the only one that works fine. They all look great, but just don't try and land at PHNL/PHLI.
Mike Franks
-
Hi Mike,
to answer your question for PHNL and to give some more information about the work in the background the fs-engine produces...
The fs-engine loads (of course) all needed bgls into the memory it has to - depending on the entries from scenery.cfg exactly in the order you could manipulate. Very early the standard-fs-directories are loaded and in these directories are for example the standard flattenings FL* and the standard airport AP* files. Mostly last but not least the "newer" addon scenery-bgls.
Very interesting is:
If you start at an airport, fly around in this fs-cell and land again, all bgls from this airport are loaded last and - more important - they are used correctly. It will lead to no problem, you would be able to place lwm-files for flattening under the standard-airport-altitude. And you could put the complete airport (in the afcad file) on a deeper or higher level as the standard-airport-altitude. All this works and - if in the betatests there were no flights from another destination - this looks all correct.
But the problem begins if you come from another fs-cell, another airport, which is a little bit far away. So that the fs-engine has to load this cell-bgls while flying around. In this case the engine use the method "the first found entry counts". Sadly the first entry is the first airport entry the engine gets. Mostly the standard-entries in the ap-files are the first files. This is the reason why if s.o. have to change the airport altitude to a deeper altitude the designers put altitude-correction-files in the standard-directorys (like world/scenery - it's written "earlier" than the standard AP-files). Or manipulate the standard AP-files (like jabbgl).
Of course you get problems (like in this case) when the AP-files altitude wouldn't be at the same altitude than the airport itself.
In the AFCAD file Fabrizio used the same altitude like standard. So no problem here. But the airport flattening is made nowadays with a lwm-flatten. Sadly the engine isn't able to use an exact definition like 13.36 ft. No, it uses the code from my last statement one page earlier with the fragments for meters and x/128... This leads to many mistakes - not only here...
When approaching from another destination: AP-files found, airport altitude is set.
And now the lwm-flattening (which is deeper I said in my last statemant) puts the flattening "underneath" the AP-files-altitude -> this leads to such a problem like described. I'm sure Fabrizio put the photo bitmap exactly 0ft above his lwm-flattening. Correct Fabrizio?
So there are many reasons if a customer has problems only while landing at an airport, not when starting.
Maybe you (Mike) have changed the standard-ap-altitude in the standard file (from another older addon) or somewhere in your sceneries is another AFCAD with a deeper altitude. I have no problems in PHNL, so there are no faults from standard fs to fsdreamteam-addon without the older influence from another PHNL-Addon.
BTW: this fact often is the reason for sunken wheels or floating aircrafts a view feet above the ground. Only to add this... (not the fact here)
Sorry if I have made errors in writing in english. ;)
Ciao,
Rainer.
-
hello to everyone for my part I can not follow your explanation! I still have a problem and nobody can fix it, I'm disappointed :-[
good day all
-
There's obviously no reason to post the same screenshot twice. The problem will be fixed with an update, we are working on it.
-
Thank you Rainer for the very detailed explanation. I'm sure the patch will fix the problem with Lihue.
To make sure I didn't change any settings, or have an interfering scenery, I got a new hard drive and installed FS2004. I then added PHNL. I went to PHNL, took off in the default cessena, flew around and landed. When I land I have the flickering problem and the disappearing runway markings as I exit. Once I get past the exit ramp, everything is fine again. If I taxi back to the runway, the problem comes back. The only change I made was to the cfg and I added TERRAIN_MAX_VERTEX_LEVEL=21. Everything else is default and default scenery. I wonder if my PHNL download is bad and during installation it's not adding a file I need or something got corrupted? I guess I'll download a fresh copy and see.
The problem I'm having at Lihue is the same as everyone else's.
Mike Franks
-
There's obviously no reason to post the same screenshot twice. The problem will be fixed with an update, we are working on it.
Thanks Virtuali.
-
Thanks Rainer for clarifying the technical stuff!
I'm holding off my purchase until the fixed version is out... but I'm already looking forward to do some island hopping in Hawaii!! :)
Cheers,
Sylvain
-
I too had r/w 35 disappear as I was rolling down it. Also,there are no approached to choose when pressing 'PROC' om the GPS. Have to get close and intercept the gs/localizer.