Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

5 Neutral

About DLP084

  • Rank

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. Would be also interested in the correct 1:1 zoom value.
  2. The course displayed on the PFD (number 2 circled) is always the correct one, as this is the result of the FS TRUE Bearing + the variation stored in the magdec.bgl All other courses have to be ignored. So always look what the PDF displays and set the NAV/RAD course according to that value. Otherwise you are going to fly an offset. The 206 is the correct "FS" course in your case. Updating the magvar.bgl helps to get that value closer to the real one. Jan-Paul
  3. Guys, there is no need to apply the Magnetic Variation Corrector to BGL Files. It has no influence on the navigation of the aircrafts. It only changes the displayed courses on the map view (world/map) within the navaid list. The indicated values on the aircraft instruments and SHIFT + Z have already been changed by the magdec.bgl Jan-Paul
  4. Could you please try the following: Disable ALL Add On sceneries (including Add On Scenery folder itself) and try again with default scenery only. If that solves your problem, enable each add on scenery step by step to find the afcad file that causes the trouble. With FS9, corrupted afcads anywhere in the world were known to create such problems. Could be the same with FSX. But I am not sure about this as I dont use FSX. But maybe its worth a try. Jan-Paul
  5. In Both cases yes. The new magnetic declination will make the FS Bearings matching more or less the current published ones. + / - 2° of tolerance can be expected due to the fact that state sources (AIPs) are not always adhering to the current magnetic variation. Jan-Paul
  6. But that one is only useful to correct the variation inside the afcad files. It has no influence on the behavior of the aircrafts. The AFCAD variation is used, to determine the bearings for the internal fs map as well as for some external applications like FSNavigator or the MakeRWYs tool from Pete Dowson. If the tool does not correct the variation, you still have the old bearings on the map display (facility information), whereas the aicrafts show the new values according to the magdec.bgl Jan-Paul
  7. Here is the new Link:http://www.aero.sors.fr/index.htmlJan-Paul
  8. Hi, could you please also correct the GPWS Bug at the 744 FS9 Version? Shouldn't be a big problem since it works as it should in FSX (GPWS alitude callouts not inhibited with Gear up). Jan-Paul
  9. Hi, just tried it with the FSX Version. Everything works fine here. Is it possible to fix that issue for the FS9 Version? Jan-Paul
  10. Hi, it seems to be a bug. Look at this video: The gear comes down after the 2500ft callout. http://www.youtube.com/watch?v=llp3EN-WyukPlease make sure that the MD-11 doesn't have the same bug. Jan-Paul
  11. Hi, I have noticed that the altitude callouts on both 747 and 737, are inhibited when the gear is up. They only sound when the gear is down. Is this a bug or a feature? Jan-Paul
  12. Hi, looks good for a preview picture. Is this FS9 or FSX? Looking forward for an FS9 release also. Jan-Paul
  13. Hi, RTFM: Page 350: "Speed constraints must always be entered in association with in altitude constraint." Jan-Paul
  14. Hi, I found the soloutions!!!1. Way (Best I think) Simply swap the NDB and the VOR entries. The 737 reads the first entry for displaying radials. Should now look like: CALEDONIA CHU NDB 43.586914 -91.490419209.00NPISA PIS VORD 43.677167 10.390611112.10HPISA PIS NDB 43.589222 10.297083379.00NNICE NC NDB 43.590278 7.129444338.00N2. Way: Rename the NDB to PISNB should look like(sytax is very important, no spacing!! between pisnb and ndb: CALEDONIA CHU NDB 43.586914 -91.490419209.00NPISA PISNBNDB 43.589222 10.297083379.00NNICE NC NDB 43.590278 7.129444338.00NAttention: The coordinates should be at the same vertical position when reading down, not as displayed in the thread. Jan-Paul
  15. Hi, maybe it helps to rename the NDB to PISNB in the Nav Database. Richard Stefan has done this (adding "NB") with the SID/STAR Files when NDB's and VOR's use the same identifiers. Jan-Paul
  • Create New...