salokin

1.0.8, MSFS2020 How do I explain to the passengers that the computer suggests that the last 160 or so miles of the flight is going to take around 4 hours or more ?!?

Update: this was the start of major problems with the plane leading to abandonment of the flight. With engines showing near 100% thrust, the plane was unable to maintain speed resulting in an alpha floor situation. I couldn't see a way to reset the situation.

MSFS2020 ver 1.0.7 Instead of waiting for the programmed waypoint for the step climb to FL400, the FMS has decided that a gradual change is necessary over the next few hours ... which it thinks will only take just a couple of minutes! Can we get step climb and offset joining/leaving properly coded for this long haul airliner. please?

This used to happen to me ... but since 1.0.7 came out pressing the master caution button DOES silence the alarm.

Just switched away to another page on FMS 2 then back to F PLN. That gave a more sensible updated T/D time but it was still out of sequence with the previous and next waypoints.

MSFS 2020, version 1.0.7 Top of descent time obviously showing incorrectly in FMS Flight Plan, not agreeing with what's shown on PERF page and not fitting in with waypoint times before and after. In this case, the time shown is one minute after predicted landing!

MSFS2020 1.0.7 When entering and leaving an offset segment, the plane can head off in all sorts of directions rather than altering course by the set amount (30 deg default) to the new path.

MSFS2020 1.0.7 The step climbs entered into the FMS aren't properly inserted into the flight plan. In the example shown in the pics, the step climb from F390 to F400 at JOOPY then strangely shows FL389 next to S/C then FL390 at the next waypoint (miles away) before FL400 at the following waypoint.

Yes, same problem ... annoying to have to look down at the Clear button on the pedestal. If it works for me, the jumping outside would be a simpler workaround!

The total number of passengers agrees with what was expected from Simbrief. However, the cabin crew always find that the number of passengers in the four compartments doesn't agree with that number, usually with 3 extra stowaways! (16+20+91+91 = 218) Hopefully an easy fix?

A350 MSFS2020. For today's flight I inserted two step climbs. Upon reaching the first I decided the plane was not ready to climb. Message "Step climb deleted" subsequently seen. But it was the second step climb that was deleted from the list, not the first at the waypoint already passed. Surely incorrect behaviour?

(MSFS 2020) Update suggested that this was fixed, but swapping active and SEC1 then swapping back led to original full flight plan being lost ... start again!

Programming the end waypoint for an offset segment of a flight is usually "interesting" in the FMS, with different waypoint then displayed in the box to the one either selected or "typed" in. At the end of an offset to the right (by 2 miles for example), the plane turns left to get back on track but then continues left in a full circle! Has happened multiple times!

... has usually been fine but the attached screenshot shows nonsensical time for T/D on today's flight with T/D at 20:54, long after expected landing at 20:36 !