budreiser

Oh well! I tried that Tiger. Guess it isn't my lucky day. Have other chores waiting but will try again in the morn. Thank you.

WOW! A 5 second hold. Thats amazing. Can't wait to give it a try on my machine. Thanks mate.

Tiger texted.....Have your key bindings been re-set after the last update by any chance? YES! More times than I care to remember. I even tried assigning other keys, like F10. No luck. But thanks for all your sage advice on this post and others from which I've gleaned good info from.

This is probably not a revelation to most, but as the saying goes, if it helps just one soul, it's worth it. I've viewed this video (link below) by a gentleman known as Huddison a few times in the past. But in that past, since my F2 key toggled REVERSE THRUST, I had no need for any other means to utilize such. That ship has since sailed. Now, on my HOTAS X, I chose the NUMBER 8 button to do the job. That button is on the throttle column of the HOTAS, so it is a one-handed operation, but, as the command states, you must HOLD the button down, also while giving it positive throttle . Nowhere near as neat and handy as tapping the F2 key after touchdown, but it brakes the aircraft. Also, when the F2 key functioned properly, the external camera would show the engine cowling sliding back when applied. Not so with HOLD REVERSE THRUST. But it brings that B787 beast to a stop. If you don't release the button, the craft will start backing up. Hope this makes sense and my explanation isn't confusing. https://duckduckgo.com/?q=msfs2020+reverse+thrust&iax=videos&ia=videos&iai=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Djt3CiPb20g0

Thanks once again Tiger. Yes! Really love this aircraft so I have watched mucho videos and read through most everything concerning it. Like others, whenever these problems arrive, it makes you wonder if you are alone. I'm just glad I don't have to pay for all those "other-end-of-runway strobe lights I destroy when I don't stop in time.

Thanks Dave. A thousand pardons. That would be the B787.

Well, it ain't like it used to be, but, through forums on MSFS2020 I have managed to utilize tedious workarounds for many shortcomings (mainly navigational) since UPGRADE 1.33.8.0. An important one that still stymie's me (and obviously many others) is the loss of REVERSE THRUST. The F2 key (or any other selection), for toggling REVERSE THRUST, doesn't do diddley. With the exception of mouse-shoving the REVERSE THRUST levers full forward, nothing I have tried has any effect, and that action doesn't show the engine cowling sliding back in exterior view. Thanks in advance for any responses.

Thanks Tiger. I bookmarked it from that MS Flight Simulator FS (Polls) Aircraft and Avionics Update II (1.33.8.0) Discussion. Was just getting started to read it when I saw your reply.

Food for thought, Randy

Four days ago (30th June), I started a post discussing my experiences with IFR since the 1.33.8.0 UPGRADE. My gripe is generally with the B787-10 as it is my craft of choice, although, because someone else enticed me, I tried the Cessna Longitude, with the same results. I don't claim to be an expert, but since toying with this beaut since Aug. 2022, I've learned a lot and have become quite comfortable with it. In a few days it will be 2 weeks since this upgrade, and many more issues are showing their ugly heads. After reading through much of the Microsoft Flight Simulator FS (Polls) Aircraft and Avionics Update II (1.33.8.0) Discussion, I see my problem is more widespread across the MSFS2020 spectrum. According to this poll, other issues, such as LOCALIZER, APPROACH, inability to (either or both) tune in or lock on to an ILS/GLS, failure for craft to follow Flight Plan, Reverse Thrust, etc., are rife, and I am experiencing those also. Prior to this upgrade (which was supposed to fix problems), things were basically o.k. I could go from A to B and put her down on Centerline. Get real Bud, some of your landings stunk on ice. Alright, for the most part, virtual flying was great. I'm certain the folks at MSFS and their many associates would like things to be perfect, but that's not to be in this world. All we can hope for here is that these deficiencies are rectified somewhere down the line, and, the sooner the better. Happy Birthday, America.

Thanks mucho N069NT! As soon as I finish this little note, I'm moving on to the Longitude. I messed around a little with that craft 6 or 8 months ago, and liked a lot about it, but the B787 has been my love since then, and got to feel like I was married to it . The FMC in the 787 (at least on my machine) is very difficult to make changes, even more so since 1.33.8.0 UPGRADE. A big chunk of the upgrade involved the avionics in the 787. If I try to add or delete a waypoint, I get a "you can't do that" type of message. For instance, prior to this upgrade, I could hand enter the ILS/GLS frequency on the NAV RADIO selection. Now it is verboten. I also do not recall an option to request "direct to the next waypoint" from ATC. Anyway, I suppose I've beat this dead horse enough. Time to move on and try to master the Longitude. Will first have to learn about the Garmin. Wish me luck. And I sincerely thank you for your reply. Have a good day!

Before this latest UPGRADE (1.33.8.0), I never had a problem with an IFR (lo or hi alt) flight. Much of this problem was covered in a previous post of mine titled "Latest Upgrade". I'm starting this new post, wondering, am I the only one with this issue. Not that I'm wishing others are cursed with this, but if you are, I'd love to know I'm not alone. I've tried every avenue I could think of including uninstalling and reinstalling MSFS2020. I always get these same results. In the days of yore (pre 1.33.8.0), if I entered an ILS runway at a destination in FLIGHT PLANNING, the flight plan took me from A to B. To stay basic, but yet get the issue across, I'm showing this short IFR flight from Gulfport, MS to KMSY (New Orleans) shown on VFR map below as rwy 29. The flight path should be continuous from SLIDD to HRV, but is missing between these points, which means, kiss your IFR goodbye. I have already tried flight plans from other A and B points but, alas, it's always the same. On longer flights, MANSEQ is inserted once or twice after departure and/or before arrival. When you see a MANSEQ (Manual Sequencing)), you can also kiss your IFR goodbye. Oh, one other thing. The flight plan almost always...eh, maybe always...shows some sort of flight path continuance beyond your destination, kind of like a holding pattern (see the pale blue line left of rwy 29). Now, not being a "Real World Pilot", I'm not saying this doesn't happen in reality, but what I read about Autopilot, and what my past experience in flight simming portrayed, this makes no sense. As previously stated, I never had this problem in the past. Thanks in advance for any comments... bud

Thanks again tiger. That really had me wondering why I couldn't access such. BTW, just tried a VFR hop from KTLH to KMSY. As it should be, magenta flgt path the whole route until HRV VOR...near HELMT transition and a 286 radial needed to land. Had to enter in ILS freq. for KMSY rwy 29. So apparently, it is only IFR that this MANSEQ crud is affecting. Guess if I want to do ILS stuff, I'll have to learn some workarounds until this issue is rectified.

By today's release, do you mean a June 29th release? Your post above looks awfully familiar to the upgrade on June 23rd. Also, cannot find any reference online mentioning any release after June 23rd.

That upgrade (1.33.8.0) came out on (I believe) June 23rd. It is was I started this thread about and it was after upgrading that all these probs befell me.

Tiger, here's another "Thank You". Looked over the link you mentioned and also this one: "Direct to" explanation - General Discussion & Community Support / General Discussion - Microsoft Flight Simulator Forums All this might be more than my old brain can comprehend. Maybe it is time to join the ultra light genre.

O.K. tiger, I'm back to start a new day of trying to rectify this issue. But first, let me digress to yesterday: I started by making sure the "COMMUNITY" folder was empty, including the file "B78XH-v0.1.15_vjS4m (B78XH (B787-10 Heavy). Next, I did a Uninstall of MSFS2020. Then spent from 10 a.m. until near 4 p.m. DL'ing and reinstalling it. Results...No change. Today, right or wrong, I might try uninstalling once more and directing it to a different drive. I'm running out of options and near the end of my wits. Thanks for being a sounding board.

Once more, THANKS. I think I ditched that Heavy Division mod but will have to wait till tomorrow morn to make sure.

To tiger 1962. Being disrespectful is not one of baddies, so I hope I don't sound so. I see how much you and many others have helped this community and I am ever grateful. You might be missing my point with this "Flight Path" issue I'm experiencing, or perhaps I'm not explaining myself well enough. Prior to this latest upgrade, when I filed a flight plan, once I engaged AP, AT, VNAV and LNAV, the MSFS B787-10 would fly the magenta course from AP activation to destination. Most all I had to do was to set climb and descend amounts, apply proper flaps, control landing speed, de-activate AP at 2 or 3 hundred feet AGL, then flare at 100 feet. Quite elementary. NOW, since this most recent upgrade, that dog won't hunt. When I view the flight path on the World Map, whether it be the MSFS2020 feature or the SimBrief program, the unbroken flight path is there. When I go to "FLY" (or "READY TO FLY"), I get truncated flight paths as shown below. I can hand-fly the aircraft to the first waypoint but that is fruitless. I can hand-fly to Transition with the same result. AP (or LOCALIZER/APPROACH) will NOT lock on that course. I have been messin' with flight sims since the Sub Logic days. I don't recall what version introduced AP flying, but I've been hooked on it since. Never before this upgrade have I seen an entry such as "MANSEQ". When it first appeared I googled it and looked it over: https://forums.flightsimulator.com/t/manseq/447704 I did not make any changes to my system before this problem. Since it occurred, I have tried removing files in the "COMMUNITY" folder, resetting MSFS2020, going back to the previous NVIDIA RTX3060 driver, and Lord knows what else. I hope to make another more successful attempt with the ZEN folks soon, but since I don't see others with this problem, I doubt it will get any attention. What I would appreciate, is someone else entering this same plan (KORD--KPIT) and posting a few pics of the route. I'm betting it won't have chunks of the path missing, nor any "MANSEQ" entries. Thanks tiger, and all others who have commented on this post.

After countless hours of attempting a fix for this problem...including removing everything in COMMUNITY folder and an hours long RESET of MSFS2020...nothing has changed (See new attached pics). I searched for others experiencing the same but didn't find much. After yesterday's fruitless endeavor, I thought I'd pass this bug on to the Zen gang (or whatever their proper nomenclature). Maybe I'm too old and/or too stupid but got off that avenue after being led from one site to another and getting the feeling I was lost. This is supposed to be a flight from KORD to KPIT. First screenshot shows KORD rwy28R with the start of flight path across Lake Michigan at ELX. Second shot shows flight path ending at MANSEQ northeast of KPIT. Every flgt pln I've tried so far gives me the same result. Either cut off at the beginning, the end, in the middle, or a combination. When it comes to IFR autopilot flying, I guess I'm grounded. Maybe the FAA is spot on with that age 65 rule. Whatever will I do?

VERY INTERESTING...The year I was born. I remember my Dad taking my 2 brothers and I to Shushan Airport (Now KNEW Lakefront) before and after WWII. Also watching newly built PBY Catalina's rolled out of the factory, down a huge seaplane ramp, and taking off for the war effort. Ah, the memories.

Thanks Mr. Zippy. Ya done it again!

This might sound dumb, but how can I replace that giant letter "B" with an old photo of me.

Kingnorris, I'm sorry you're also having probs, but glad I'm not alone. When I first tried a flgt with the new upgrade, I too had a barrel roll incident. Thought maybe I did something wrong so just restarted the flight. Now, on to this prime prob. First thing this morning, I made sure no files were in community folder. Then I started MSFS2020 and removed the two upgrade files from 06/23/2023. Upon restarting, I noticed it removed the B787 from MY HANGER. I then re-installed those 2 files, got the 787 back, and filed a flgtpln from KLAX to KDEN. All looked honky-dory until "Ready to Fly. Brought up the VFR map. Flgt path was much worse than the KJAX-KMSY of yesterday except I could only spot one MANSEQ, in the Pacific off KLAX. Screenshot below shows much-broken flight path near destination with KDEN in lower right corner:

Thanks Cavulife. I was going to bring that up in a later post. ETA's are missing in latest 787 upgrades, but were not much use prior as they were 4 or 5 hours behind GMT. Thought I'd try a different bird, but just got the same results with the Cessna Longitude. The flgtpln is from KJAX to KMSY. All appears normal after selecting IFR High Altitude, runways for departing and arriving...and cruise altitude. All waypoints are shown in the graph. It is after "Ready to Fly" that the monkey wrench enters the scene. Examining the VFR map, there are two "MANSEQ" entrees which at first glance look like Waypoints with 6 characters. The first panel plants one on the KJAX runway probably prior to reaching VR1. This MANSEQ stuff was explained somewhat in this link: Manseq - General Discussion & Community Support / General Discussion - Microsoft Flight Simulator Forums