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.

sinandgrin

Frozen-Inactivity
  • Joined

  • Last visited

Everything posted by sinandgrin

  1. Some feedback and tests with FLC mode. I am noticing that I can only perform climbs in FLC mode, not descents. Can anyone else get the mode to perfrom a descnet using Murfman's instructions? For climbs - I am level at say 3000 feet in ALT captured mode. I select a new higher altidute say 6000 and hit FLC. The plane pitches up fairly agressivly and then starts to lower the nose back down to eventually settle at a pitch that holds my selected airspeed minus 10 knots. I am noticing that the FLC mode always seems to hold a speed 10 knots less than that selected at the top of the speed tape. Not a hige deal just an observation. As the plane reaches the selcted altitude it goes from FLC (with ALTS armed) to PIT to ALT to eventually capture the selected altitude. Good! For descents - I am level at 6000 now with ALT captured and active. I select a new lower altidue 3000 feet and hit FLC. The plane agressivly pitches up and will climb until I intervene. If I hit the Nose UP key to raise the selected airspeed the nose will lower and eventually settle at a level 0 FPM pitch while trying to accelerate to my very high airspeed I selected. If instead I go back to level flight in ALT mode and try to start my descent in VS mode I can dial in a VS -500 FPM (with ALTS armed) but if I hit the FLC button here I get the same unwanted pitch up behavior. Is this a bug? Should the FLC mode be able to do descents? Can anyone else do descents with FLC mode?
  2. Thank you Murfman and JYW for your input here. I just bought this plane and have been wondering if these issues were bugs or if I was just doing something incorrectly. I am excited to read these sugestions and will give them a full test later today! I did have some follow up questions for the community with this plane. I wanted to see if there was anyway to bind a key command to change the autopilot's heading, speed, altitude. I would like to map these controls to my X-52pro like I do in PMDG/Aerosoft Airbus products. Since the C400 does not seem to use the FSX/P3D defualt autopilot commands I am at a bit of a loss here. Any suggestions or successes in this area?
  3. Thanks for the info, I'll use this as a rough guide when I do my RNAV approaches. Thanks for confirming that the 777 is not capable of the GLS (LPV) approaches. ...Danger Zone! :wink:
  4. Yes I was thinking that too since the LPV mins @ 486ft are still 200ft above the TDZE so it wouldn't make sense to be able to autoland. With that cleared up and confirmed are there any unique FMA anounciations or other ques that I can look for to ensure that an RNAV apporach is correctly setup and that the plane is capable of flying to the lowest (LPV) mins? Aside from looking at the FMA for the VPATH Pitch mode is there anything else?
  5. I have been struggling to find information in the FCOM, FCTM and in the forums that fully address the capabilities and limitation of the RNAV approach functions in the 777. I have no problem flying CAT III ILS Autoland approaches but I want to know if the autpilot will also fly an RNAV GPS approach and to what minimums, is it possible to fly an Autoland RNAV apporach, is this even possible or make sense? Also I would like to make sure I understand the requirements, in terms of cockpit setup, to complete say an RNAV GPS apporach to LPV mins. For example the RNAV (GPS) Y RWY1C to LPV mins into KIAD. Thanks for any help or references.
  6. Humm, I did have a Flight saved as the default which loads each time FSX boots up to the Free Flight screen. I would normally then change my aircraft and other preferences before going flying. I did have the 777 in the PMDG house colors selected as the aircraft in that saved flight file. So I went in and changed the default flight so that it would load the FSX C-172 instead when FSX boots up, and then changed my aircraft to the PMDG 777 in my custom livery and the Fans now show up. I guess that fixed the problem, thanks for the tip Kyle!
  7. I took a stab at painting my own fictional 777 yesterday and aside from this one issue was successfull. I read through the manual from the paintkit and also I couldn't find any comments on the forums so I thought I would post here to see if others have had this problem. I am missing the N1 Fan in both engines with my custom 777 paint job. As far as I can tell this is the only thing that is missing. I made sure that my Texture.cfg file had the proper fallback references, which it should since I simply copied it from the paintkit. I even tried coping the pmdg_777_misc.dds and pmdg_777_misc_parts.dds files from the texture.common200LR folder into my custom texture folder but still had no luck. Here is what I am talking about, any thoughts?

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.