Status Update
Our E-Jets version with the brand-new custom FMS has been in testing for almost three months now - and a lot has happened since then. Today we want to give you a quick look behind the scenes and a peek at what’s coming next.
To give you an idea of the project’s scale, here are some quick facts from the last three months:
- More than 88 different testers have been flying the new version.
- Around 2,000 flight sessions recorded — that’s about 22 flights per day!
- 64 unique issue reports from testers were logged.
- 350 code changes were made — roughly 4 updates per day!
A huge thank-you to all our testers who have been incredibly active and dedicated.
Where do we stand now?
First of all — the aircraft is fully flyable in normal operation! All major FMS pages set-up, LNAV is working well (even with crazy 50kt crosswinds over the UK lately!), and VNAV is already implemented.
One of the biggest challenges was integrating Navigraph navdata, which caused a few regression bugs. For example, we had to rebuild the entire ILS approach logic from scratch - but it’s now rock solid.
Thanks to detailed testing, we’ve also fixed many issues with SIDs and STARs, especially tricky cases like “Course to Altitude” waypoints and other non-standard procedures.
Even the Direct-To function is working quite well now, with just a few small quirks left.
Here is some tester feedback from our latest build:
So what’s missing before you can try it?
Mainly the vertical autopilot modes, that makes the airplane following the vertical paths.
Until now, we’ve been using the default MSFS autopilot, which worked fine - but with the new CFMS, we had to completely rebuild the LNAV part from scratch. That’s already done.
The vertical modes, however, aren’t fully finished yet, which means the autopilot sometimes doesn’t behave correctly — especially during RNAV approaches, where precision is key.
What’s next?
We’ll soon invite another 100 testers, so keep an eye on your emails. If you don’t get one within 7 days, please don’t be disappointed - just keep reading!
If the autopilot is stable by December, we plan to release an experimental version to everyone.
This version will still have some limitations - for example, certain sounds (like the TO CONFIG check) won’t work yet because we’re still porting the sound logic from JavaScript to WASM. The performance calculator in the EFB also isn’t available yet since it was tied to the old MCDU system. Still, this build is already way more fun to fly than the old version.
When will v1.0 arrive?
There’s still a lot to do beyond what’s mentioned — So we can’t give you a release date.
What matters most to us is that you all get a much better version as soon as possible - no matter what we end up calling it.
