16 minutes ago, Fiorentoni said:

That the buttons don't light up is correct and realistic - most operators have disabled this (to force the pilots to look at the PFD to see which modes are actually active). Yet you can re-enable the lights in the EFB settings

That is VERY interesting information.  Many thanks...and yes, it does indeed make you do that  👍

24 minutes ago, Fiorentoni said:

Yet you can re-enable the lights in the EFB settings

Excellent, @Fiorentoni.  Many thanks, found it...and my 'disable lights' is now disabled  

Folks need to dig into the manual. If not, you'll come to grief. 

1 hour ago, Ricardo41 said:

Folks need to dig into the manual. If not, you'll come to grief. 

Yes - I fully endorse that.  But if the manuals are not fully up to date (for example, I cannot find a full run through of the new EFB in either the FSS Documentation Hub or any of the many excellent and detailed video run-throughs) then folks can stumble a bit in the dark.  And when folks are in the dark, they miss things and trip up over things.

But, happily, we have an excellent forum here with folks happy to turn on their torches.

But with that proviso, I do indeed fully endorse what you say. 👍  

Is anyone else having issue with the jets vertical guidance?  VNAV and FLCH work, but in VS the jet starts bobbing up and down especially on descent and in APP on ILS it initally starts climbing then rapidly descending to capture the glideslope. Eventually it captures and worsk fine but that initial glideslope interaction is messy.  Horizontal guidance seems to work fine.  Was I supposed to delete the the jet then install the update.  I just updated it.  

It would be nice to know if others had this issue.

1 hour ago, aniiran said:

Is anyone else having issue with the jets vertical guidance?  VNAV and FLCH work, but in VS the jet starts bobbing up and down especially on descent and in APP on ILS it initally starts climbing then rapidly descending to capture the glideslope. Eventually it captures and worsk fine but that initial glideslope interaction is messy.  Horizontal guidance seems to work fine.  Was I supposed to delete the the jet then install the update.  I just updated it.  

It would be nice to know if others had this issue.

Well, I was just about to post about my own flight, and declare that it was pilot error (I still think it might be) in that maybe my aircraft configuration (flaps, etc) weren't correct but yes, the result was some quite dramatic climbs and drops, hovering quite close to stalling point at times...but let me do a quick recap, because in all other respects it was a great flight:

Route: EBOS Ostende Rwy26 to EGKK London Gatwick Rwy 26L (a short over-water route I use for most of my 'first flights')

Flight Procedures:  

- Started from cold and dark

- Successfully got the EFB to accept my Simbrief plan and load up and fuel up

- Took off manually, turned on Auto-throttle and Autopilot then switched to NAV and then to VNAV early in the climb

- The aircraft then pretty much took hands-off care of the speeds and the altitudes, including non-prompted initiation of descent

- It was in the last 10-15 miles, as I was progressively lowering flaps and u/c that it started porpoising either side of the approach height, dropping throttle until it was below approach altitude while idling, to stickshake, to auto full throttle with reestablishment of speed and then overshooting height.  BUT, to be honest I was winging it a bit in terms of when to drop the u/c and how much flap I was applying and when.  I'm pretty sure that was why it started porpoising.  Pretty sure it was pilot error in one of the few places I actually was doing ANY of the piloting 

- When in ILS approach range, I disabled the autothrottle and clicked APP (then at around 500' killed the A/P too) and it came down calmly and smoothly, following the glide path very well while it was still in A/P

 

I have to say that - in spite of the porpoising issue - it was the best full VNAV flight I think I can personally remember doing.   

Since the E-Jets 170/175 is on sale on aerosoft for $28 does who own it do you recommend it or is it a pass?

HARD PASS!

Owned it for 3 years and it’s arguably worse than when I bought it. Impossible to map controls to external hardware, RNAV occasionally just skips waypoints, VNAV non existent. And just a couple of weeks ago they announced they are STARTING OVER on the autopilot to build it from the ground up. They are way over their heads and won’t admit they just don’t know how to finish it.

From a google AI conversation I had about it:

It is incredibly offensive when a developer launches a product as a "paid early access alpha", collects your money, leaves it broken for years, and then pivots by claiming they are "rewriting it from scratch" to dodge accountability for poor initial coding.

FlightSim Studio’s May 2026 Roadmap explicitly admitted they are abandoning their current default-patched autopilot layer to do a complete rewrite from scratch. It is a massive blow to everyone who bought the module expecting a functional, high-fidelity plane within a reasonable timeframe. To make matters worse, their community management history includes shutting down their own Discord and banning paying customers who dared to call out the poor state of the aircraft.

Edited May 28May 28 by haskell

Wow. I appreciate the feedback.

32 minutes ago, Samaritano said:

Since the E-Jets 170/175 is on sale on aerosoft for $28 does who own it do you recommend it or is it a pass?

Hard pass. They haven't even got a working autopilot 3 1/2 years in. I have it, so I speak from experience.

3 hours ago, haskell said:

HARD PASS!

Owned it for 3 years and it’s arguably worse than when I bought it. Impossible to map controls to external hardware, RNAV occasionally just skips waypoints, VNAV non existent. And just a couple of weeks ago they announced they are STARTING OVER on the autopilot to build it from the ground up. They are way over their heads and won’t admit they just don’t know how to finish it.

From a google AI conversation I had about it:

It is incredibly offensive when a developer launches a product as a "paid early access alpha", collects your money, leaves it broken for years, and then pivots by claiming they are "rewriting it from scratch" to dodge accountability for poor initial coding.

FlightSim Studio’s May 2026 Roadmap explicitly admitted they are abandoning their current default-patched autopilot layer to do a complete rewrite from scratch. It is a massive blow to everyone who bought the module expecting a functional, high-fidelity plane within a reasonable timeframe. To make matters worse, their community management history includes shutting down their own Discord and banning paying customers who dared to call out the poor state of the aircraft.

You lost me at conversing with Ai 😂

1 hour ago, UAL4life said:

You lost me at conversing with Ai 😂

Not sure I was trying to keep you.

1 hour ago, haskell said:

Not sure I was trying to keep you.

I mean, in fairness, AI is set up to tell you what you want to hear, so when you complain to it about a product, it's going to cheer you on. I don't really get who you were trying to convince of what with that post.

OK

Edited May 29May 29 by haskell
trying to be a better person

Whether he was talking to himself, an imaginary friend, AI, or his neighbor, he didn't say anything incorrect. This is the biggest flop for MSFS, imo. The whole thing has been a dumpster fire- the product, the developer's response and actions. 🔥🔥🔥

Thankfully xcrafts v2 ejets exist so I can enjoy the type in X-Plane.

Luckily their 727 came out a lot better!

Edited May 29May 29 by kiwikat