Mike777

This might help. It's for a different model 787 and may be slightly out of date, but it should still be worth looking at: https://flightsimulator.azureedge.net/wp-content/uploads/2023/06/B787-10-Tutorial-Flight-v1.pdf Mike

Hi Langeveldt, This sounds like an MSFS problem -- some problem with your controller -- maybe you bumped it accidentally or it is "noisy." It could also be a problem from some other source, such as scenery. I doubt it stems from your flying technique or some realistic aircraft behavior. Perhaps try a runway at a different airport and see if the problem reappears.

In past versions of Flight Simulator there have been addons such as Active Sky that performed very well for past weather. I gather that the MSFS folks are not open to such addons. Does anyone know why?

South African is Springbok and I believe TW Express was Waterski.

Check the OAT, which is displayed on one of the screens. In the past, some addons have caused very high air temperatures at high altitudes, which can seriously affect performance. Also, in the current heat wave, some mid-level altitude temperatures are (realistically) unusually high.

Hi Alexgorider, Just be sure you are in the Community folder and not the one you described in your earlier posts.

Hi Alexgorider, That is not the community folder. The default Community folder is at: ... AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community The folder you found appears to have folders for each installed aircraft that keep track of that aircraft's use. Deleting the entry for Kuro_B787_8 won't delete the aircraft at all. There is no global SimObjects\Airplanes folder in the Community folder (there is one within each aircraft's folder). So start by removing to a different folder all the 787-8 liveries (which can be fixed to work with the new 787-8). Then delete the 787-8 folder(s) in ... Packages\Community. Then redownload the newest version of the Kuro 787-8 and place it in the ... packages\Community folder. Hope this helps! PS: If you have a 787-10 Heavy Division version in your Community folder, you need to remove that too.

In the all-time worst crash, KLM and Pan Am 747s on Tenerife, the KLM co-pilot was unsure whether their 747 had been cleared for takeoff in very foggy conditions (it hadn't), but was not assertive enough toward a very senior captain. I am very uncomfortable with generalizations about Asian pilots. There are plenty of examples of dumb mistakes by pilots of many different cultures and nationalities. In the Air Asia incident, the A330 systems programmers, who may well have been French or German, deserve some blame for not including a warning in the event of a discrepancy between GPS position and entered position from the first software version. People make mistakes. Mike

Tutorial 1.5 is at the following link. You will see the download link near the top. http://precisionmanuals.com/pages/downloads/docs.html Mike

i heartily agree with Michael C.'s suggestion that you fly the tutorial and read the intro manual carefully. Also, I mis-spoke in my earlier entry. Thrust mode is shown on upper LEFT side of PFD. Pay attention to what thrust mode you are in when the thrust reduces or increases unexpectedly. Again, I am guessing that your issues are arising from accidental throttle hardware inputs in HOLD mode, both on takeoff and during VNAV descents. Search FCOM2 for "Hold mode" -- you will see that the autothrottle stops controlling the throttle levers in that mode, leaving them open to any deliberate or accidental input from your throttle hardware. Also read up on the options for how you set your throttle hardware to override the autothrottle commands. As Bob S. said, PMDG wants you to sign your full name in its forums. Mike

Most likely your throttle hardware is sending spikes/commands that you are unaware of. In both situations the Autothrottle (A/T) is most likely in HOLD mode, which allows movement of the throttle levers to adjust thrust. On takeoff, the Autothrottle goes into HOLD mode at 80 knots. This allows manual adjustment of thrust; if your throttle hardware is set to a minimum position and you touch it accidentally or it sends a spike, thrust will drop. In VNAV descents the Autothrottle also often goes into HOLD mode. Again, depending on your hardware throttle's position, you might send a full thrust or other command that you are unaware of. For both situations, check what thrust mode the A/T is in on the FMA (upper right of PFD for Thrust mode). See if it is in HOLD mode. There is also an option to display the hardware throttle position on the N1 EICAS indications. That should help you troubleshoot. Mike

Thanks, Michael. I was looking in the wrong place! Mike

You may have a scenery problem, specifically more than one AFCAD (runway and airport nav info) file for the same airport. Please give the specific airport and runway where this is happening. No. For vertical mode you can be in VNAV, FLCH (flight level change) or VS (vertical speed) or Altitude hold. For horizontal mode you can be in LNAV, Heading Hold or Heading Select. If you have APP pressed and you intercept the localizer followed by the glideslope, it will follow both. You should always check the FMA at the top of the PFD to see what are the active vertical and horizontal modes, and what modes are armed Yes, along with the final approach course heading, but in most cases it shouldn't be necessary. Francis, I think you have not done the tutorial that comes with the PMDG 777. You aren't going to be able to learn to fly it just by asking questions. Also, you need to give the specific airport, runway, frequency, and heading where you are having a problem. Mike Michael, can you point Francis to Kyle's tutorial 1.5? I can only find his original Sept. 2013 video. Thanks, Mike

Hi, Francis, After reading through this thread it's unclear to me what you are doing. I often take a shortcut while flying a STAR and often eliminate the initial waypoint of an ILS approach, without the autotuned frequency disappearing. So let me go over a few things: A STAR is an arrival that sets you up for the final approach. A STAR will end either with a transition waypoint to the final approach, or with VECTORS, which means you have to be vectored by ATC or vector yourself to the first waypoint of the final approach. So the STAR and the final approach are two different things. The STAR ends at or before the beginning of the final approach. (From a VECTORS waypoint, you may have to fly using heading select until you are in a good position to aim for the initial waypoint of your final approach. You can eliminate the VECTORS waypoint by selecting the first waypoint of the final approach as your next waypoint.) Before you are close to the arrival airport, first you select your final approach which is for a specific runway. Then you select your STAR. This is because some STARs are not available for all runways, so when you select your final approach/runway, the inappropriate STARs won't show up any more as choices. If the final approach you select is labelled "ILS" it will autotune the ILS frequency as Michael described above. (If you select another type of approach, such as an RNAV or VOR approach, the ILS frequency will NOT be autotuned.) Deleting some or all waypoints in the STAR won't affect the final approach or the tuned ILS frequency. Even choosing to go direct to an intermediate waypoint on the final approach, instead of the initial one, won't delete the autotuned frequency, in my experience. The other thing to be aware of, is that there can be a discrepancy between the ILS frequency autotuned by the FMC, and the frequency in the FSX scenery. This is because the scenery is old and the FMC is using recent data. In that case you won't see the localizer or GS indications on the PFD or ND (or you may land on the wrong runway!). This is not an autotune problem. You can check by opening up the FSX map and comparing the frequency there to the frequency autotuned by the FMC. Mike