![]() ![]() with UHPP being specifically embedded in a file named APX90130.bgl, but since you have an add-on airport, I wouldn't be sure what would take precedence. Not being familiar with FS9's file layouts, I can only guess that assuming you got the change correct, your FS9 is NOT seeing your edited/changed *.bgl file yet and you are still seeing the stock layout.Īgain, not knowing about FS9 files, but knowing FSX files, the STOCK internal airport files for FSX are NOT named directly for the airport such as UHPP.bgl, instead they are embedded within the scenery file structure. I made the changes with ADEX for FSX not FS9. ![]() I would paste a picture of the ILS properties page on here so you can see, but all the icons i see here on avsim editor seem to be about taking this disscusion to facebook and twitter :huh:, and non easily identiable for adding attachment, i do this in hotmail all the time Generally well versed in tweaking fsx for years, but this first time i am using ADE. Its the only uhpp bgl on my PC so i assume it camer with mytraffix and its a not a defualt fsx airport.Īfter chnaging ILS heading to 338.770000 in ADE, i save the fuile using the ADE defualt naming convention, which, then rename it to BR2_UHPP.BGL so i can overwrite exisiting. I have made the changes suggested by Gray_Lensman in ADE9 but i see no change.ĭ:\Microsoft Flight Simulator X\MyTraffic\Scenery\BR2_UHPP.BGL If it was offset an equivalent amount to the other side of the approach path, I would be inclined to think that it had such a purpose but as it is to the wrong side, I am inclined to believe it's another FSX airport design goof of which there are many. If it was meant to guide around obstructions to the airport, then being offset in the direction that it is in stock FSX would actually guide your flight path closer to some higher hills/mountains on the approach path on that side of the approach to runway 34R, a direct contradiction to the purpose of an offset Localizer as described above. However, in this case the chart does not call it an LDA and. ![]() It is then called a Localizer Type Directional Aid (LDA). In some cases, a course projected by localizer is at an angle to the runway (usually due to obstructions around the airport. In aviation, a localizer (LOC) is one of the components of an Instrument Landing System (ILS), and it provides runway centerline guidance to aircraft. ![]() Has anyone checked if this localiser is not offset in reality? In this case, I aligned to the displayed Garmin localizer arc near the apex then snapped the pics. I used the Cessna 172 with the Garmin because it best visually shows the Localizer Arc Zoomed in or out. Here's a pic of the ADEX corrected UHPP airport alignment on my system AFTER ADEX correction: Here's a pic of the stock UHPP airport alignment on my system BEFORE ADEX correction: Correcting the Localizer to also be 338.77 corrects the issue. The further away from the airport you get the worse it aligns especially at distances usually around the FAF. The problem is that the stock airport had the Localizer aligned to 337.00 but the corresponding runway was aligned to 158.77/338.77. I used to see this before in where the localiser actually matches the runway opposite instead of the one its meant to, think i fixed that by moving Mytraffic scenery around in scenery.cfg.īut this time the localiser matches non of the 4 runways at UHPP.Īny idea how to fix this globally in fsx, if not whats the best way to fix for each airport i find the issue. Sitting on the runway Tuned 110.30 for 34R at UHPP, but the localiser is pointing way off to the left. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |