• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About burle1

  • Birthday 07/07/1962

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Profile Information

  • Gender
  • Location
  1. burle1

    POSKY B737

    Be aware that FS Nav displays localizer back course approaches on the map, by default. There is a checkbox in the settings that can turn this feature off.What runway were you landing on? In the real world, KSNA has both an ILS and an LDA (a form of offset localizer) on Runway 19R. If you were landing on Runway 1L, you were probably receiving the back course.Todd
  2. The Clearance Delivery frequency is for issuance of an IFR clearance.Try filing an IFR flight plan in the Flight Planner. After loading your plan, you will be given an option to contact Clearance Delivery. Upon readback of your clearance, you will be given the option to contact Tower, Ground or Traffic, depending on the airport.In FS your IFR clearance will always be delivered "as filed." In the real world, that is not always the case.Todd
  3. George,This question comes up occasionally. It has to do with changes in magnetic north models over time.Airnav.com shows the EYW VOR has a magnetic variation of 1E, using data from 1965.The published variation for KEYW airport is 4W, using year 2000 data. The FSX flight planner and GPS also use magvar data from 2000.If you fly the J79 airway on a true course of 038, you will be flying the 037 radial from the EYW VOR (38 - 1 = 37), but your compass bearing will be 042 (38 + 4 = 42). This assumes the absence of a crosswind, of course.This situation is quite common in the USA. Many VOR navaids are defined using old data. FAA policy calls for realignment of the VOR when published and current magvar data are off by 6 degrees or more.Looks like they need to put EYW on the list.Todd
  4. You need three items to make your refueling station work.One is the physical model. You already have that.The second is the trigger element. This defines the invisible boundaries of the fueling area. I don't know of any scenery programs that can do this. You would have to hand code the xml and then compile the .bgl with Microsoft's BGLComp.The third item is the services element, which also has to be coded in xml and then compiled. This item tells the Map View and the GPS that fuel is available at your airport.If I can be of any assistance, let me know.Todd
  5. Others have reported similar problems.Sometimes this is triggered when AFCAD and AFCAD 2 files are mixed in the same scenery. You might want to check the offending sceneries and look for AF_* and AF2_* files mixed together.Also, a poorly written exclude or flatten file can cause the same effect. You might want to try removing these files one at a time until the problem is cured.Todd
  6. burle1

    A Puzzling Approach

    As Reggie said, there is a problem with improper back course capture if both localizers are on the same frequency.There is another complication at KAVP. Both of the localizers are offset from the runway heading in the real world. I don't know how accurately this is modeled in FS 9, but the back course capture issue is even worse when there is an offset localizer involved, at least in my experience.Todd
  7. burle1

    ILS problem at KPDX rwy 28R

    The ILS at KPDX is a known problem. There are offset ILS installations in the real world. This is not one of them.You might want to check the file library here for an AFCAD file for KPDX. AFCAD is an airport facilities editor, considered by many to be a must have for FS9.Todd
  8. burle1

    Edit VOR designation

    You are correct. Setting the navaid frequency to zero will render the navaid out-of-service, but will not remove it from the map. There is no harm in doing this.Todd
  9. burle1

    Edit VOR designation

    The easiest way to accomplish this is by using AFCAD2, available in Avsim's library as well as elsewhere.You would need to create a new VOR with the new name and identifier, with all the other attributes identical to the old VOR. Then you edit the old VOR and change its radio frequency to zero.Completely removing a navaid is not a good idea even if it could be done, as any instrument approaches which reference the navaid would be rendered unusable.Todd
  10. This topic has come up several times lately. Did you install any 3rd party scenery before you noticed the problem?You might want to disable any addon scenery and see if the problem goes away. There was a thread here a few weeks ago about a South American scenery which broke magnetic variation all over the globe. The scenery contained a corrupt exclude file. Once this file was removed, the problem disappeared.Let us know if this helps.Todd
  11. burle1

    ILS in AFCAD

    Rick,AFCAD can add the ILS facility, but it cannot add the instrument approach procedure for ATC to assign.The approach procedure must be coded and compiled into a BGL scenery file using BGLCOMP from Microsoft, following the meager instructions in the BGLCOMP SDK.Which airport and approach in particular? If these are US Airports I might be able to help.Todd
  12. burle1

    Compass Errors

    Try looking for the addon scenery Torres Straits. If you have this scenery installed, find and delete ydni_excl.bgl .There are several posts here and elsewhere about this problem. It seems this one rogue file is disabling magnetic variation.Hope this helps,Todd
  13. The magdec.bgl file defines the compass bearings displayed on your airplane's instruments. This includes the magnetic compass, HSI, Shift-Z information display and GPS.Each airport has a defined magnetic variation in the ap*.bgl file. As far as I can see, this element does nothing but allow the ATC to calculate the correct bearings to the airport. There are also magvar elements for each ILS, which serve the same purpose.It's worth noting that the information in magdec.bgl seems to represent a 1985 magvar model, while the ap*.bgls appear to contain 1995 information. This means that when you are shooting an ILS there will be a slight difference between the heading on your compass and the heading shown in the map view dialog.Hope this helps,Todd
  14. Interesting observations. Here are some of my own:NewBGLAnalyze corrupts AWOS and ASOS radio frequency type parameters. "AWOS" is changed to "ASOS", while "ASOS" is changed into a null string " ". This stops the string from compiling.NewBGLAnalyze changes 4-light PAPI displays into 2-light displays. This occurs when the parameter "PAPI4" is decompiled as "PAPI2". Note that the genuine "PAPI2" parameter is decompiled properly.Sometimes BGLXML inserts a bogus "deleteAllWindsocks" parameter into the DeleteAirport element. I have only seen this happen once. The resulting string did not compile.For what it's worth, NewBGLAnalyze seems to do a better job than BGLXML, especially with Approach elements. Neither program is perfect, but the shortcomings of NewBGLAnalyze are more easily identified in the decompiled output.Todd