Ironic…? AP cut off via joystick button worked for me from day 1 of the (EA) release. Not sure what you mean…
I’m not, the binding AUTOPILOT OFF that is used by any other planes is not disconnecting AP on experimental since I bough the plane (instead it switches the AP side CPT/FO and vice versa), I have to click the button in the cockpit with my mouse to do so.
I don’t know the exact name right now but try the “AP/Flight Director toggle” or something like this; when pressed while AP is active the AP cuts out but FD stays on. I have a separate key for the FD toggle. Works in every aircraft, IIRC
Or in other words: use another keybind, it is actually ont an issue.
The FSS E-Jets are currently discounted at the Aerosoft shop. The CRJ V2 is also currently available at a reduced price in the Contrail shop.
Which aircraft is the better choice right now?
I believe the last update for the CRJ V2 was nearly a year ago, and I wonder if there will even be any future updates from the developer, Hans Hartmann?
The FSS E-Jets are still in beta, but there are constant updates. Once the beta phase ends, it will surely turn out to be a great aircraft, right?
I’m looking for a smaller regional jet for city-hopping and shorter flights within Europe…
Thanks!
Well there’s a V2 E-Jets coming afterwards too (at an extra cost), but that might be a while yet. Just something to keep in mind though.
Both are fine regional jets, the CRJ has a manual throttle that needs managing especially on final. Both have had their own sagas. CRJ is quite old now, but was moved to V2 fairly recently. I don’t fly it much, but that’s more to do with currently having too many good aircraft to fly. There’s also the F70/100 too which are great.
To think back when it first came out as the first ever study level msfs plane and wow…
Definitely broke up the monotonous A320 flying with various fictional liveries 
Yes it was either one or the other for the longest time. Then PMDG showed up with the 737NG.
Thanks, but as it’s fixed now no need to 
I’m liking the new ‘send to mcdu’ features in the EFB. It’s been missing and will likely help a lot of users as well as speeding up the mcdu performance setup time.
The fact that they pushed the notification before making sure all three versions’ .10.45 is available is not a great sign (on Aerosoft I’m still getting the previous stable for pax 190/195)
Praying that the big problems from last experimental at least got fixed, guess it’s the 175 that will be the test plane for it
Edit: okay nobody else replied so no point making a separate post, first impression: it no longer makes me want to stop flying, a genuine improvement even if there are still some funny bugs and less funny bugs
Like, the flight plan in MCDU is empty until taking off, so any discontinuity checking/constraints changes can only happen in the air. Looked into the updated documentation to see if I’m wrong, and they use RTE instead of FPL for their example images 
A few other buttons in there also either don’t work even if they should, or lead to a wrong destination (the PERF family is especially bad about it)
The wild pitching is somewhat under control, but still happens; I’ve decided to try a hold at an altitude, and it revealed another MCDU bug(?) where what I typed into the leg time did in no way agree with what was written (“1” became “1.4 min”, “1.5” turned into “1.9 min” and so on).
The hold itself was… not very good - it was at high speed, and I did get the warning for it, but still both the lateral and vertical tracking quickly went off the rails. See the graphs below:
(horizontal bars = 1000ft)
The intention was a FL290@280kt (ended up slower), 1:30 right-turn 84 degree inbound. The execution… As seen above, I took pity on it and commanded descent once the oscillating was hitting 1200+ fpm - except PTH was finicky (maybe due to TOD being within the hold?) so I had to switch to green FLCH.
Also, I’m not sure if this isn’t user error/by design but I don’t think the plane should so aggressively pursue PTH when I’m already below it and picking VFLCH to descent. You can see it on the right end: I reactivated VNAV thinking I’d get VFLCH, and the plane begun to climb to capture the path left a good thousand or so feet above, forcing me to go back to green.
The Direct-To page isn’t there, but the plane isn’t dealing with them as badly as it did before, though I haven’t yet put it in a position to overspeed while chasing the path. The vertical tracking into localizer capture is also heavily improved over last time.
I may sound like I’m complaining, but this version is definitely something I finally will want to fly again, once the 190/195 is available. I am happy with what I see, but I also hope the team knows they really need to keep going if they don’t want to miss the third December deadline, because there are still many improvements needed.
Things that work as intended, but annoyed me: good that the GSX integration now outright says “don’t use the GSX menu, use the EFB’s GSX option” - especially now that GSX itself can be used from the tablet - but I wish the order of things was a bit different, that fuel wasn’t the last thing to be loaded only after the boarding was completed. Also, obligatory mention every update that my standard bindings like “increase/decrease heading bug”, “set autopilot disengage” still don’t have events assigned to them. The hitbox for the hundreds/thousands switch on the alt knob is also a bit hard to hit.
Oh, the dome light was fixed, I already wrote that it’s still decorative but was pleasantly surprised; I guess that sums up my experience with this update pretty well.
Feedback on latest version (v0.10.45) after another flight or two.
- In FMS I can’t delete alt constraints. (I previously was able to)
- When I have Flaps 1 in manifest calc, the T/O config check seem to expect flaps 2
- Map range zoom dial does 1x zoom while zooming in but 2x zoom per mouse scroll movement while zooming out
- I’ve had one aircraft hang/freeze (sim fine but aircraft just completely frozen/unresponsive/no moving) after using the FMC to change a STAR (maybe a wasm crash but now with no orange screen?)
I’ve noticed that on the PERF page, I have some speed that is set (like 0.75M for CLIMB) but the plane seems to use another speed (0.76M in my case) and I don’t know where it comes from.
Same with descent speed.
Stable and so beta version my was updated automatically im not sure what version then has installed us me, but it was not working fine so i mistake that’s the are, beta version…
I made 2 flights with the new stable version ((v0.10.45). The autopilot is a mess after taking off and the ILS is not working at all during the approach mode. Is anyone having the same or Im doing something wrong?
I have had the AP do very strange things any time during flight with the latest version. Goes into a dive, makes random turns, etc, with no good reason.
Is it only the 170/175 that is updated?
Don’t see any 0.10.45 in Aerosoft for the 190s. Yes I uninstalled it.
And is the FSS discord (still) lacking any discussion channels?
Welcome channel says to registrer product - Registrer E-jets series. Not working.
Then above that it says “open a ticket in #support to register yor product”…does that give access to more channels?
Sigh…
It’s looking very nice! Sounds are great! Textures are wonderful! It’s a real beauty!
Just flew two flights tonight without issues at all. Terrific work by FSS after this brutally long process.
After TO, bring down the throttle a bit, then engage AT.
For AP, make sure you trim the plane to neutral so it’s just maintaining the gentle climb. Then engage AP. Otherwise, if you just go with the TO trim, trying to engage AP is a bucking bronco and AP won’t engage.
Regarding the AP doing strange things, so far, I haven’t had that in the newest version. Triple check your flight plan for discontinuities and errors.
I’ve had no ILS problems at all, but the key is to arm APP notably earlier than for some other planes (when you arm it right before the capture waypoint). Not the case here. I usually arm APP half way between the capture waypoint and the one before. Again, then no issues so far.
After so, so long, it’s finally nice to have this plane functioning well.
Regarding their Discord, I joined so long ago I don’t remember how it works, but sounds like you need the registration or license to access, which is reasonable.
Here was the E-Jet workflow a user posted to the FSS Discord:
FROM DISCORD
"Perfect Embraer Takeoff & Climb – Button Order That Actually Works
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
⸻
On the runway (before rolling)
• Arm A/T
• Verify:
• FD ON
• Pitch guidance visible
⸻
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
⸻
Liftoff → initial climb
• Rotate normally
• Follow FD
• Aircraft remains in TO mode
This is where many people panic and press FLCH — don’t
⸻
400 ft AGL
• LNAV becomes active (if armed)
• Still TO mode vertically
⸻
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
⸻
Passing acceleration / clean-up
• Retract flaps on schedule
• Aircraft continues climbing in FLCH
• Thrust remains climb thrust
⸻
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)"