Please put your post in the correct forum.
Today we had to move over 150 posts manually.  We do feel the forum structure is logical and the section names are clear. As redirecting posts pollute the forum a lot we will not add them anymore. So if you are unable to find your post, look for it in the most logical forum section.

Jump to content

Jason Birdsall

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jason Birdsall

  • Rank
    Ramp Agent
  1. Is the AN-2 installed in the default location or a custom install location? I seem to recall an issue on another aircraft where problems like this arose from an entry in one of the xml files "pointing" to a file in its default installation location. Anyone who didn't use the default install path would have problems as the called file didn't exist in the location specified. A long shot, to be sure... this does sound strangely familiar though. Cheers, Birdy
  2. Yes I am. Right click to pull the setting knob, then mouse wheel to set the time, then left click to run. Hope this helps. Cheers, Jason
  3. Gentlemen: I appear to be struggling to set the flight deck clock in the AN-2 correctly. When adjusting the time, the minute hand sweeps 2 revolutions for each single revolution of the hour hand (i.e. 120 minutes per hour) and, once set and running, loses approximately 6 minutes for every game hour (the clock will have advanced approximately 54 minutes after 60 minutes of game time [from the P3d "World time and date"] has elapsed). Is there something I am doing wrong and/or any way to adjust this to accurate reflect Zulu time and proper time progression? Cheers, Jason Run on P3d v4.5, Win10.
  4. Gentlemen: BLUF: FMS appears to be sequencing the active leg too soon on large turns (greater than 45* turn) and defaulting to "direct-to intercept next leg at a 45* angle". This places the aircraft in an undesirable location for some departures/arrivals. Discussion: From your screenshots it appears that you're having the same problem I've been having with RNAV SIDs involving substantial turns (more than 45 degrees). It appears that the FMS is computing an excessively early lead turn point to make these turns, causing it to seem to omit specific legs of the departure. My most recent example was on the GYPSM5 departure out of Eagle County (KEGE), the FMS turned the 215* course OK but then turned too soon toward KIRLE, turning into the mountain. While in this turn it then sequenced to RLG (approx 12 nm prior to KIRLE) so that it was turned to intercept the KIRLE -> RLG courseline. This of course also places the aircraft above/into terrain. With a westbound turn to join the enroute structure, the FMS again discontinued trying to get to RLG approx 14 nm prior to RLG, instead sequencing RLG -> WEEMN, turning around to try to intercept the RLG -> WEEMN courseline at a 45* intercept. Recommend developers look at the lead turn coding, as the problem appears to start there. Cheers, BirdyGYPSM5.pdf
  • Create New...