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

Edited January 31Jan 31 by MadDog

7 hours ago, MadDog said:

This is the first of nine really good tutorial

Really good tutorial. Thanks for posting!

I'm going to give it one more try this evening and, if I can't stop it going suicidal in the climb-phase, will revert to the non-experimental version with my MUCH better understanding of how the autopilot and related works on this aircraft and, if that is no good either, will probably leave it alone until either the next update or maybe an updated video by Capt Nabs (which are great but, by his own admission, has to work around non-realistic issues of last year's non-experimental version.)

I really like the aircraft itself and the FFS rendition of it

I really like the automated take off

I really like the full vnav control from top of climb down to landing

I can't do with my 90% failure rate in the climb phase even when following all of the suggested protocols and settings

Edited January 31Jan 31 by AJZip2

And an update and a bit of good news:  

The autopilot button lights don't light up (I'm pretty sure they didn't in the pre-experimental either - does everyone else have lights lit up when, eg, NAV or A/T or AP etc buttons are pressed on the E170 or E190?).  It's inconvenient but on the main glass screen most of those buttons will change something on the screen (TO / LNAV / Pink Cross etc) so you can see they have been engaged.  But I'm pretty sure that nothing flashes up anywhere else when you switch FD on or off.  Well, as it's just been updated, this afternoon I booted up my Stream Deck...and the FD light on the Stream Deck was on from boot up!!  So all this time, I've been turning the FD OFF and not ON!!

So, now with the FD correctly switched, I tried another flight.  And it was a LOT better.  No more vertical climbs and dives.  And it almost looked like it was going to follow the flight plan in the MCDU!  Well - it did up until cruise height...and then, after 10-15 miles, it started very gently climbing or descending away from the designated heights.  So still not achieved a successful flight (16 tries now) but so, so close... 

I’m definitely doing something wrong with my take off prep. Go nowhere at rotate and need another 40kts or so to actually depart. 
 

My flow;

Prep in simbrief. 
import flight in E190 EFB. 
import route in E190 MCDU

Enter weather details and runway in EFB and click calculate. 
 

Go to perf in MCDU and press import (or whatever it says). 

23 minutes ago, jsbdave said:

I’m definitely doing something wrong with my take off prep. Go nowhere at rotate and need another 40kts or so to actually depart. 
 

My flow;

Prep in simbrief. 
import flight in E190 EFB. 
import route in E190 MCDU

Enter weather details and runway in EFB and click calculate. 
 

Go to perf in MCDU and press import (or whatever it says). 

Did you trim your aircraft to value the MCDU is telling you?

10 minutes ago, Robin29 said:

Did you trim your aircraft to value the MCDU is telling you?

I do 👍

Done it!!!!

Flight 18.  So yes, 17 failures but at last...at last I've finally sussed the procedures and - with the help of the Stream Deck to guide me which autopilot buttons were on and which were off, and the enormous help of the folks here, I've just done a complete flight successfully in the FSS EMB175!!!!  🤸‍♀️🤸‍♀️ 

The major turning point was the list of do's and don'ts that @MaGer1965 brought to my attention and the updating of my Stream Deck with the latest E-Jet pack from Flight Panels to be able to see what buttons were active and what weren't (ref the indicator lights in the sim not operating), which revealed that I kept turning the FD 'Off' when I thought I was turning it 'On'.

Do I remember in the initial info that FSS put up relating to the Experimental Version that they don't want any issues found by users being raised/logged on their Discord?  If so, I hope they are aware of the indicator lights not working which really does give some problems (for me, 16 flights of problems) - and also the positioning of the VR mouse, which is shockingly bad with you having to point and click on at the row of numbers or letters on the MCDU above or below the ones you are trying to click...for some clicks but not all (which is even worse). 

Edited January 31Jan 31 by AJZip2

I only use the 175 regularly, I have the 170, 190 and 195, but the us stopped using 19Xs so I fly it a lot less. My v10.31 E175 install has worked perfect on 3 flights now TUS-PHX, DFW-OKC and SLC-BZN.  I flew it for 1.5 hrs. practicing take offs and transitions to departure.  Did-some touch and gos, shot a few ils approaches. I'm quite chuffed with what progress has finally been made. 

No WASM crashes for me but I have only ever had one WASM crash in MSFS and that was on the ini A350 when it first came out. I have 64GB ram though so that might have something to do with it. 

I'm so glad they fixed all the wierd cockpit reflective surface issues that were present in the stable version. 

16 hours ago, AJZip2 said:

And an update and a bit of good news:  

The autopilot button lights don't light up (I'm pretty sure they didn't in the pre-experimental either - does everyone else have lights lit up when, eg, NAV or A/T or AP etc buttons are pressed on the E170 or E190?).  It's inconvenient but on the main glass screen most of those buttons will change something on the screen (TO / LNAV / Pink Cross etc) so you can see they have been engaged.  But I'm pretty sure that nothing flashes up anywhere else when you switch FD on or off.  Well, as it's just been updated, this afternoon I booted up my Stream Deck...and the FD light on the Stream Deck was on from boot up!!  So all this time, I've been turning the FD OFF and not ON!!

So, now with the FD correctly switched, I tried another flight.  And it was a LOT better.  No more vertical climbs and dives.  And it almost looked like it was going to follow the flight plan in the MCDU!  Well - it did up until cruise height...and then, after 10-15 miles, it started very gently climbing or descending away from the designated heights.  So still not achieved a successful flight (16 tries now) but so, so close... 

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 daylight?

46 minutes ago, petz_e said:

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 daylight?

I'll check again.  Thanks for the thought 👍

1 hour ago, petz_e said:

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 daylight?

Well, you live and learn.  In the settings on the EFB is 'Disable Glareshield LED's'  and it was defaulted to ON.  I had no idea that this referred to the button lights.  Turned it to OFF and, hey presto, I now have the green LEDs for all of the Autopilot buttons!!!  

But I then noticed that the FD button (which was the one causing all of the problems) doesn't actually have an LED! 

I'm sure there must be a way somewhere or somehow - is there anything anywhere in the instruments or displays that indicate that the FD is on or off on the Embraer?  My trusty Stream Deck can register it but, at the moment, I can't see anything that changes in the cockpit or displays if I turn it on or off (except the tendency for the plane to try to crash).  

Many thanks @petz_e  - and gold star, smiley face if you know the answer to the FD too  

4 hours ago, AJZip2 said:

is there anything anywhere in the instruments or displays that indicate that the FD is on or off on the Embraer? 

wouldn't it be obvious because it either shows in the Primary display or not?

6 hours ago, AJZip2 said:

Well, you live and learn.  In the settings on the EFB is 'Disable Glareshield LED's'  and it was defaulted to ON.  I had no idea that this referred to the button lights.  Turned it to OFF and, hey presto, I now have the green LEDs for all of the Autopilot buttons!!!  

But I then noticed that the FD button (which was the one causing all of the problems) doesn't actually have an LED! 

I'm sure there must be a way somewhere or somehow - is there anything anywhere in the instruments or displays that indicate that the FD is on or off on the Embraer?  My trusty Stream Deck can register it but, at the moment, I can't see anything that changes in the cockpit or displays if I turn it on or off (except the tendency for the plane to try to crash).  

Many thanks @petz_e  - and gold star, smiley face if you know the answer to the FD too  

comes disabled because its Embraer logic to make pilots pay attention to the glareshield than buttons but companies have the option for on/off .... if you watch a few takeoff videos, you'll see this reflected inside the cockpit

FMS is still not to handle in VR. Also with the newest update. The Clickspots are still way off. Very frustrating....