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.

FSS Updates the EMB 175 and 195 again Experimental

Featured Replies

Hmmm.  Kinda wish they'd fix some of the things that got "broke" in the experimental version, such as the ECS, Electrics, and Hydraulics system pages - not to mention the button mapping on the FMS CDU in VR - before spending another 4 weeks just working on holds....  As it stands, i'm going to give 0.10.31 one try, but i'm expecting i'll probably be rolling back to the stable version.  The FMS on the stable version is simpler, yes, but the overall experience is just better, at least in my opinion.

Buzz Benz

  • Replies 81
  • Views 9.5k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Discord user BarbarossaLord posted the following guide for the experimental version, which indeed helped me a lot:   'Got it — let me boil Matt’s whole rant down into a clean, correct, step-

  • This is the first of nine really good tutorial videos on how to fly the aircraft... and they're pretty short and sweet.

  • I might be wrong but isn‘t the E-Jets line like the CRJ where IRL the lights don‘t light up during daylight? There should be a setting in the EFB where you can force the lights to light up, even in da

I'll have another go with it later today but I've just had a short lnav-controlled flight with it and, so far, it has performed pretty well in MSFS2024. 

I will try a vnav flight next but, at the moment, the only thing of note is that the main control panel button slit lights - always on the very dim side at the best of times - didn't appear to be lit at all when the buttons were engaged.  It maybe simple a 'lights' switch I haven't switched on so I will investigate further before noting it as a bug. 

That said, the buttons themselves all seemed to function properly with good response, for example when turning autopilot/heading/alt/speed on and off in flight.  I took off in manual mode, then switched to Autopilot with manual height overrides in places, then changed the route 'en-route' to see if that tripped it up (it didn't) and then finally landed with a very nicely controlled ILS landing.

And it is - and always was even when stuff didn't work properly - a very nice aircraft to fly.

So, so far so good...   

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

Hmmm...unless I am doing something very wrong (which is entirely possible) VNav basically doesn't work, but more surprising LNav also seems inconsistent.  I got halfway through a flight but then found it impossible to start descending - even though my flight plan showed it should, the nice vertical position screen showed it should but it wasn't having it even though I triggered start of descent.  So I tried to manually command the autopilot - but it wouldn't have that either.   I had to abort the flight.

Pity - it seemed to be going OK until then.  Not sure how much time I'm going to spend on this model in this version - there are much better options to spend the same amount of time on at the moment.  I may just sit it out and watch for further updates or workarounds. 

Edited by AJZip2

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

Discord user BarbarossaLord posted the following guide for the experimental version, which indeed helped me a lot:

 

'Got it — let me boil Matt’s whole rant down into a clean, correct, step-by-step Embraer takeoff & climb recipe, without the Discord chaos 😄
This is Embraer logic (E-Jet, esp. MSFS implementations), not Boeing/Airbus muscle memory.

Core idea (before the checklist)
    •    TO mode is the ONLY vertical mode you use for takeoff
    •    You do NOT arm VNAV on the ground (you can’t, really)
    •    FLCH is the “acceleration / climb management” mode, not a “takeoff mode”
    •    If you touch FLCH too early, the aircraft will level or even pitch down to chase speed → “descending into certain death”

Perfect Embraer Takeoff & Climb – Button Order That Actually Works

1️⃣ At the gate (setup)
    •    TRS (Thrust Rating Selector): set to TO
    •    FMS: takeoff speeds set (V1 / VR / V2)
    •    Initial altitude: set in MCP (per ATC SID clearance)
    •    LNAV: optional to arm on the ground (this is fine)
    •    VNAV: do not try to arm it
    •    A/T: not armed yet

👉 At this stage, no vertical mode is armed

2️⃣ On the runway (before rolling)
    •    Arm A/T
    •    Verify:
    •    FD ON
    •    Pitch guidance visible

3️⃣ Takeoff roll
    •    Advance thrust
    •    Aircraft enters TO mode automatically

📌 What TO mode does
    •    Commands V2 + ~20
    •    Controls pitch directly
    •    This is not FLCH, not VNAV, not VS

➡️ Hands off the vertical modes

4️⃣ Liftoff → initial climb
    •    Rotate normally
    •    Follow FD
    •    Aircraft remains in TO mode

🧠 This is where many people panic and press FLCH — don’t

5️⃣ 400 ft AGL
    •    LNAV becomes active (if armed)
    •    Still TO mode vertically

6️⃣ Acceleration altitude (usually ~1000 ft AGL)

⚠️ This is the critical moment

Now you do exactly this:

➡️ Press FLCH

📌 What happens:
    •    TO mode is cancelled
    •    Aircraft transitions to second-segment climb
    •    It allows acceleration toward VFS / clean speed
    •    Pitch may shallow — this is normal

This is why pressing FLCH too early is deadly:
    •    FLCH prioritizes speed over climb
    •    If you’re slow and low, it will pitch down aggressively

7️⃣ Passing acceleration / clean-up
    •    Retract flaps on schedule
    •    Aircraft continues climbing in FLCH
    •    Thrust remains climb thrust

8️⃣ Above ~3000 ft AGL

Now you have options:

Option A (most realistic / safest)
    •    Stay in FLCH
    •    Let it manage climb via speed

Option B
    •    Switch to VNAV / PTH (if available & stable)

Option C
    •    Use V/S if you want absolute control

Why people were “descending into death”?

Because they:
    •    Pressed FLCH before acceleration altitude
    •    Or tried to “arm VNAV” on the ground
    •    Or assumed FLCH = climb mode (it isn’t — it’s a speed mode)

FLCH will sacrifice pitch to get the selected speed.
Near the ground, that’s lethal if mistimed.

TL;DR – One-line memory hook

Take off in TO → don’t touch vertical modes → FLCH only at accel altitude'

 

Addendum:  Discord user 'Matt' is a realworld E-Jets pilot and part of the more than 50-member E-Jets pilot team that advises FSS on development.

It looks like some 'experts' are making a complete fool of themselves again on YouTube.

Edited by MaGer1965

'It is better to be silent and be thought a fool than to speak and remove all doubt.'

Well, I definitely didn't do it like that  😀

I'll give it another go later today 👍  Many thanks for the post @MaGer1965 

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

Great advice above.  The plane does have some issues but a lot of issues I see reported seem to come from flying this like an Airbus or Boeing instead of an Embraer.  And in many cases the differences are just subtle enough to result in a big gotcha moment.

Dave

Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU

Just a heads-up: Manualslib has E-Jet rw manuals....

Edited by MaGer1965

'It is better to be silent and be thought a fool than to speak and remove all doubt.'

13 hours ago, MaGer1965 said:

Discord user BarbarossaLord posted the following guide for the experimental version, which indeed helped me a lot:

 

 

It looks like some 'experts' are making a complete fool of themselves again on YouTube.

I can't find the oprignal post on discord but indeed very helpful. I always had the feeling it shouldn't be approached with a Airbus or Boeing logic, even by the most seasoned airbus driver...

14 minutes ago, bigifooti said:

I can't find the oprignal post on discord

Most likely only to be seen by registered FSS E-Jets customers...😉

I just checked: Post is still there. Link is correct.

 

Edited by MaGer1965

'It is better to be silent and be thought a fool than to speak and remove all doubt.'

20 minutes ago, MaGer1965 said:

Most likely only to be seen by registered FSS E-Jets customers...😉

I just checked: Post is still there. Link is correct.

 

ok, didn't know that was a thing, activation gives an error i'll figure it out on discord. 

 

3 minutes ago, bigifooti said:

ok, didn't know that was a thing, activation gives an error

 

This is from the public FSS discord page, last entry:

spacer.png

'It is better to be silent and be thought a fool than to speak and remove all doubt.'

Well - it's been an afternoon of highs and lows...literally 😀

Once we got reconnected to the sim after the fairly widespread 'outage', I set up a flight from Ostende/Bruges in Belgium to London Gatwick in UK, made sure that all of the weights/v speeds/ flight plans/ etc, etc were in properly and then got your excellent notes out, @MaGer1965  

The take-off and climb were still a 'little bit' confusing.  I wasn't sure that the TO mode had actually kicked in -even though I got the cross hairs on the main screen as described - because, once off the ground, there was significant/severe yo-yo-ing of the aircraft from heading towards vertical, to then stalling to near vertical dive (I let it do its own thing knowing that any touch of the controls would probably mess the autopilot up).  The auto-throttle had been set but I wasn't sure it was operating properly.  Above the 1000' stated height I then engaged FLCH (actually at 3000') but that also didn't seem to be doing what I expected - but then I clicked the A/T button again and this time it started climbing steeply, and quickly - but now in a more 'determined' manner...towards a height much, much higher than in my flight plan!!  But it seemed at last to be in some sort of control! 

And then the doorbell rang and I had to leave it just running. 😠

When I got back to it, to my surprise, the aircraft was still in the air.  In fact, it was now over the UK.  I had a look at the Plan View screen - and it was still on course - and it was now down from 29000' to 4000'.  As we approached Gatwick and it - yes automatically! - slowed, I progressively added flap and then undercarriage...and, hands off, it landed itself!!!!!

 

I am amazed at the degree of autopiloting going on in this aircraft.  I am now certain that I will be able to sort what I did wrong on the climb. 

I am also VERY relieved - in my numerous flights in real life as a passenger in this aircraft type - that there wasn't a time the steward came into the cabin with the 'The pilot and co-pilot are both incapacitated...can anyone fly a plane?'  And I stand up, in the absence of anyone else, and say, 'Well - I fly computer simulators quite a lot.'  I can see the headlines now - 'Airliner hits small town at high speed.  Nothing left of either!'   

  

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

On 1/27/2026 at 6:56 AM, Twenty6 said:

WASM crashes have not let me actually take a flight with v0.10.31.

NavData still doesn't want to update the cycle unless you have the Ultimate subscription at Navigraph. Which I don't, or want.

Simbrief integration not working into the FMS. Although you can load a Simbrief flightplan into the EFB and load fuel into the plane.

It does look good just standing there as long as you don't touch anything. <sigh> 

FSS seems to have a real issue with WASM crashes across products - I haven't really been able to complete a flight in the 727 either, consistently WASM will crash sometimes before takeoff. Shame to hear it's happening so much with the EJets too, have been steadily reporting these as I encounter them but they don't seem to have or be pursuing a fix...

I picked up the E190 today after being tempted to do so for ages. 
 

Only done a single flight from EGPF to EGLC so far but I really liked what I experienced. 
 

Sone points though, and these may be, probably are, user error:

Issues getting airborne at the V speeds. This could be me. I was using Simbrief then the EFD to calculate them, presuming this would auto populate the FMC. Not sure it did - couldn’t rotate until about 30kts after Rotate was called.

 

VNAV went a bit nuts during the ODLEG transition and just randomly started describing. Similarly, the capture of the glide slope from below commanded a firm nose down attitude that I needed to manually intervene to prevent a CFIT.

 

Still enjoyed it though. More tomorrow!

 

1 hour ago, AJZip2 said:

got your excellent notes out, @MaGer1965  

I'm just the messenger. All tips are from the named posters / pilots. It really pays off to read - and to rely on those who really are in the know...

Edited by MaGer1965

'It is better to be silent and be thought a fool than to speak and remove all doubt.'

Create an account or sign in to comment

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.