Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Budbud

Members
  • Joined

  • Last visited

Solutions

  1. Budbud's post in FS2Crew do not start was marked as the answer   
    Hi Larsjolls,
     
    The problem is that in your panel.cfg, there is only the window titles corresponding to Fs2crew but not the defintions [Window XX]
    corresponding to these window titles.
    So you need also to copy these definitions from the panel HiDef to the panel.cfg.
  2. Budbud's post in VOR/DME - lateral guidance? was marked as the answer   
    That's correct. However you may need to adjust your course to allow the FMS to intercept the radial.
     
    Once reaching the heading 233, you will have to check if the LOC mode is active on the FMA (or try o anticipate).
    If not, then you have to check on which side on the radial you are and change your course to intercept the radial.
    Keep in mind that to intercept the radial when the VOR/LOC is armed, you still need to be on intercept heading to the radial, otherwise you will remain on HDG SEL and fly parallel to the radial without ever catching it.
     
    It is important to monitor the FMA, it will help you understand what your aircraft does.
  3. Budbud's post in Active Sky 2016 and ASCA compatibility with PMDG 777 was marked as the answer   
    For info, a little search in the PMDG B777 and you would have had your answer without re-posting.
    (12th thread)
     
    http://www.avsim.com/topic/491604-wx-radar-and-as-2016-compatibility/
  4. Budbud's post in Step climbs and RVSM definition was marked as the answer   
    Hi,
     
    1) Step climb:
    To perform a step climb with the T7, you have to set the new altitude on the MCP, wait for the indication "Now" and then press the Alt intervene button on the MCP. The AP will then switch to VNAV SPD and THR REF and climb to the new altitude.
     
    2) Step size: 
    The box step size allows you enter the size of the steps you want to be calculated by the FMC. If set 1000ft, the FMC will computes the step climb every 1000ft. So If you start at FL320, the further S/C will be FL330, FL340, and so on.
    For 2000ft, you will get FL320, FL340...
    The default values are:
    _ 0 : no step climb
    _ RVSM: steps every 2000ft
    _ ICAO: steps every  4000ft
    _ Manual entry (1000...): steps computed on the value entered.
     
    3) RVSM: The steps will be calculated every 2000ft as the levels for one way on a airway are separated by 2000ft (so to keep minimum 1000ft vertical separation between aircrafts on opposite course on the same airway).
    General rules for the RVSM is even levels on 180-359°, odd on 000-179°, but there are numerous exceptions. In Europe, some countries like France, Italy and Spain adopted a North / South RVSM (Even to the North, odd to the South). In Asia, some countries like China and Mongolia have a RVSM based on metric FL.
     
    RVSM is now implementated almost in the whole world if I'm correct (needs to confirm there as I can't find an actual chart of the implementation, mine is dated 2011), between FL290 and FL410. However, out of these levels and in some places remain other kind of separations:
    Over FL410, the minimum separation is 2000ft, hence steps are 4000ft on a same course.
    In non-RVSM airspaces (CVSM, if some remaining), all the flight levels are odd and separated by 2000ft on opposite direction (so 4000ft on a same direction).
     
    On particular areas like the North Atlantic Ocean region, FL are allocated to the NAT tracks every 1000ft but you may not be allowed to perform step climb as the separation there is based on waypoint reporting with no radar coverage.
    (It may be different now with in the implementation of the ADS-C and CPDLC on the tracks).
  5. Budbud's post in What prevents the autopilot from engaging? was marked as the answer   
    Are you trimmed and controls at the center? The aircraft attitude must be stabilized before trying to engage the autopilot.
     
    If you move the controls at the time you try to engage the autopilot it will be rejected without any warning.
     
    "
    The A/P cannot be engaged unless both of the following conditions are met :
    - No force is applied to the control wheel or column.
    - The Stabilizer Trim Autopilot Cutout Switch is at NORMAL.
    "
     
    And by the way the minimum autopilot engagement height is 400ft.
  6. Budbud's post in Noob Route Ques was marked as the answer   
    I have just checked on the FMC now.
     
    I think you have not selected the transition.
    When selecting an approach in the FMC, you must select the final approach on the right (ILS 26L), the STAR on the left (e.g.: Timba --) and in some case a transition on the right below the final approach. In that case, TIMBA.
    It will add automatically the waypoint from the last point of the STAR (usually the IAF) to the final approach (IF).
  7. Budbud's post in VLAV/LNAV Keyboard assignment was marked as the answer   
    Hi,
     
    Full names in that forum please.
     
    PMDG setup > Options > Key commands > Autoflight > VNAV switch / LNAV switch (page 3/8 for the NGX and page 3/7 for the T7)
     
    Is it what your looking for?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.