ℹ️ Skipped - page is already crawled
| Filter | Status | Condition | Details |
|---|---|---|---|
| HTTP status | PASS | download_http_code = 200 | HTTP 200 |
| Age cutoff | PASS | download_stamp > now() - 6 MONTH | 0 months ago |
| History drop | PASS | isNull(history_drop_reason) | No drop reason |
| Spam/ban | PASS | fh_dont_index != 1 AND ml_spam_score = 0 | ml_spam_score=0 |
| Canonical | PASS | meta_canonical IS NULL OR = '' OR = src_unparsed | Not set |
| Property | Value |
|---|---|
| URL | https://fenixsim.com/blog/ |
| Last Crawled | 2026-04-11 00:00:17 (57 minutes ago) |
| First Indexed | 2022-03-27 10:17:04 (4 years ago) |
| HTTP Status Code | 200 |
| Meta Title | Fenix Simulations |
| Meta Description | null |
| Meta Canonical | null |
| Boilerpipe Text | Hi everyone, a little dev update for you all on our incoming NEOs and other stuff.
Our NEOs aren’t going to make the end of this year, work is progressing along swimmingly and at good rate - but we’ve done a little bit of project reorganisation internally after some pretty intense and direct feedback from the community and through our ticketing system about the state of a couple of items on our CEO product line.
The poor implementation of VNAV.
The inability to handle a basic level of user state saving due to limitations on our side.
The old ECAM infrastructure leaving long standing latent bugs some of which have hung around like a bad smell for the last couple of years.
Primarily VNAV, and after a very strong showing of passionate community opinion on this topic, we felt the communication to us was pretty clear - and so we opted to reorient a couple of our developers off the NEOs and into lending a hand to prepare new VNAV and the dependant new ECAM infrastructure as a software update, ahead of the NEO release. Some of you may wonder why VNAV is so important, or what was wrong with it in the first place - while we did get it to a place where it was acceptable to some, it is inherently, underneath, some very old and generalised architecture - leading to path construction behaviour that was inconsistent with the A320 as a whole. The way it drew its decelerations (when, where and how) - the way it used and produced perf data, for example EFOB (some of you know this famous bug) - to the principals with which it builds the individual blocks of the vertical path (missing things like pressurisation segments, but also decel placement and logic!) - there’s a lot of important stuff here and it really does add or remove a tonne of character from the airplane’s behaviour in what I personally would consider, at least from the flight management perspective, the most scrutinised part of an airliner flight. Now, as for new VNAV, we've even been able to capture behaviour we've only seen represented in the real aircraft, or in full fidelity level-D simulators. I will talk more about VNAV and what this all really means when we start preparing it for deployment - but I think it’s a very valuable and critical upgrade for not only our CEO, but just serves to make the NEO a much better product too.
The benefit, of course, is all our new infrastructure for both the ECAM and VNAV will be battle tested ahead of their usage on the NEO products, which should mean a much smoother entry into market for the NEOs. It also keeps things a little neater when considering post release support - there’s less chance we get caught with a problem on NEOs and have to fend off dealing with that.
The downside is the basic trade-off between resources and time. From a development perspective, this is a reshuffle; we've always prioritised looking after products you've already paid for, before asking people to part with their money for more, and this trend continues here
The above update has now entered limited internal testing with some SME testers attacking both VNAV and the new ECAM in separate small groups, with a view toward pushing into large scale beta once we’re happy with the results from our SMEs.
The NEOs are in a place where they will be ready to drop into wider testing once we release new VNAV and the new ECAM infrastructure to you all, so don’t panic too hard - we’ve also got some experimental features in dev for that package which we’re quite excited to show and talk to you about.
As for state saving - this involves much more than just synchronising the switch and button positions, and work in this area is moving along well also. We plan to have this in your hands after the VNAV and ECAM infrastructure update.
I don’t think anyone is really happy about having to eat their vegetables before dessert, although calling new VNAV and all this infrastructure work “vegetables” is maybe a touch too far - they’re very real, very tangible, and much needed improvements to the product you all have now.
We’ll do a bit of media around VNAV and ECAM - so look out for that closer to when we deploy the update - then after that we’ll get into the
fun bits
. Thanks for the patience and understanding! |
| Markdown | [Join Discord](https://fenixsim.com/join_discord)
Open main menu
[Home](https://fenixsim.com/)[A320](https://fenixsim.com/a320/)[A319 & A321](https://fenixsim.com/a319-a321/)[Blog](https://fenixsim.com/blog/)[Login](https://fenixsim.com/login/)[Register](https://fenixsim.com/register/)
# Development Update November 2025
### Posted November 29, 2025
![]()
[](https://youtu.be/XCCarfZd8UU)
Hi everyone, a little dev update for you all on our incoming NEOs and other stuff.
Our NEOs aren’t going to make the end of this year, work is progressing along swimmingly and at good rate - but we’ve done a little bit of project reorganisation internally after some pretty intense and direct feedback from the community and through our ticketing system about the state of a couple of items on our CEO product line.
1. The poor implementation of VNAV.
2. The inability to handle a basic level of user state saving due to limitations on our side.
3. The old ECAM infrastructure leaving long standing latent bugs some of which have hung around like a bad smell for the last couple of years.
Primarily VNAV, and after a very strong showing of passionate community opinion on this topic, we felt the communication to us was pretty clear - and so we opted to reorient a couple of our developers off the NEOs and into lending a hand to prepare new VNAV and the dependant new ECAM infrastructure as a software update, ahead of the NEO release. Some of you may wonder why VNAV is so important, or what was wrong with it in the first place - while we did get it to a place where it was acceptable to some, it is inherently, underneath, some very old and generalised architecture - leading to path construction behaviour that was inconsistent with the A320 as a whole. The way it drew its decelerations (when, where and how) - the way it used and produced perf data, for example EFOB (some of you know this famous bug) - to the principals with which it builds the individual blocks of the vertical path (missing things like pressurisation segments, but also decel placement and logic!) - there’s a lot of important stuff here and it really does add or remove a tonne of character from the airplane’s behaviour in what I personally would consider, at least from the flight management perspective, the most scrutinised part of an airliner flight. Now, as for new VNAV, we've even been able to capture behaviour we've only seen represented in the real aircraft, or in full fidelity level-D simulators. I will talk more about VNAV and what this all really means when we start preparing it for deployment - but I think it’s a very valuable and critical upgrade for not only our CEO, but just serves to make the NEO a much better product too.
The benefit, of course, is all our new infrastructure for both the ECAM and VNAV will be battle tested ahead of their usage on the NEO products, which should mean a much smoother entry into market for the NEOs. It also keeps things a little neater when considering post release support - there’s less chance we get caught with a problem on NEOs and have to fend off dealing with that.
The downside is the basic trade-off between resources and time. From a development perspective, this is a reshuffle; we've always prioritised looking after products you've already paid for, before asking people to part with their money for more, and this trend continues here
The above update has now entered limited internal testing with some SME testers attacking both VNAV and the new ECAM in separate small groups, with a view toward pushing into large scale beta once we’re happy with the results from our SMEs.
The NEOs are in a place where they will be ready to drop into wider testing once we release new VNAV and the new ECAM infrastructure to you all, so don’t panic too hard - we’ve also got some experimental features in dev for that package which we’re quite excited to show and talk to you about.
As for state saving - this involves much more than just synchronising the switch and button positions, and work in this area is moving along well also. We plan to have this in your hands after the VNAV and ECAM infrastructure update.
I don’t think anyone is really happy about having to eat their vegetables before dessert, although calling new VNAV and all this infrastructure work “vegetables” is maybe a touch too far - they’re very real, very tangible, and much needed improvements to the product you all have now.
We’ll do a bit of media around VNAV and ECAM - so look out for that closer to when we deploy the update - then after that we’ll get into the [fun bits](https://youtu.be/XCCarfZd8UU). Thanks for the patience and understanding\!
Posts
[Development Update November 2025](https://fenixsim.com/blog/entries/2025-11-29_dev_update/)
[BFU Patch 2](https://fenixsim.com/blog/entries/2025-09-02_bfu_patch2/)
[BFU Patch 1](https://fenixsim.com/blog/entries/2025-08-04_bfu_patch1/)
[Big Fenix Update... Released\!](https://fenixsim.com/blog/entries/2025-07-28_bfu_release/)
[2025 Roadmap](https://fenixsim.com/blog/entries/2025-03-28_roadmap/)
[MSFS 2024 Compatibility](https://fenixsim.com/blog/entries/2024-11-25_msfs_2024_compatibility/)
[Fenix A32X: By The Numbers](https://fenixsim.com/blog/entries/2024-11-15_fenix_a32x_by_the_numbers/)
[The Sharklet Update is Released\!](https://fenixsim.com/blog/entries/2024-11-07_sharket_update_released/)
[It's Shark Week](https://fenixsim.com/blog/entries/2024-11-05_its_shark_week/)
[Fenix A319 & A321 Expansion Released\!](https://fenixsim.com/blog/entries/2024-08-19_a319_and_a321_expansion_released/)
[A319 & A321 Expansion: Liveries & Art Previews](https://fenixsim.com/blog/entries/2024-08-17_expansion_art_and_liveries/)
[An introduction to the Fenix A319 & A321 Expansion](https://fenixsim.com/blog/entries/2024-08-15_introducing_a319_and_a321/)
[Introducing the new Fenix Installer, and an A320 update](https://fenixsim.com/blog/entries/2024-07-26_fenix_installer_and_a320_update/)
[Status Update, Flash Sale, and Software Update\!](https://fenixsim.com/blog/entries/2024-04-15_update_and_sale/)
[Update V2.0.0.392](https://fenixsim.com/blog/entries/2024-03-11_v2b2_update/)
[V2B2 Release, Quick Start Guide and Changelog](https://fenixsim.com/blog/entries/2024-02-28_v2b2_release/)
[V1.5.2.214 Changelog](https://fenixsim.com/blog/entries/2023-08-22_214_update/)
[V2 Block 1: Changelog and Deployment Time](https://fenixsim.com/blog/entries/2023-08-10_v2_changelog/)
[Performance, and some other little bits](https://fenixsim.com/blog/entries/2023-08-05_v2_performance/)
[Beginning V2 Rollout and Future Plans](https://fenixsim.com/blog/entries/2023-08-05_v2_rollout/)
[Fenix A320: Anniversary](https://fenixsim.com/blog/entries/2023-05-19_anniversary/)
[Fenix A320: The End of a Beta](https://fenixsim.com/blog/entries/2022-05-15_end_of_beta/)
[Fenix A320: Destination Beta](https://fenixsim.com/blog/entries/2022-01-31_fenix_a320_destination_beta/)
[Feature Review & Dev Update - 08DEC2021](https://fenixsim.com/blog/entries/2021-12-08_feature_review_dev_update_-_08dec2021/)
[Fenix A320 – Dev Update 08OCT21](https://fenixsim.com/blog/entries/2021-10-08_fenix_a320_dev_update_08oct21/)
[Fenix A320 – Dev Update 17SEP21](https://fenixsim.com/blog/entries/2021-09-17_fenix_a320_dev_update_17sep21/)
[Feature Review: Indicating/Recording](https://fenixsim.com/blog/entries/2021-09-10_feature_review_indicating_recording/)
[Fenix A320 – Dev Update 27AUG21](https://fenixsim.com/blog/entries/2021-08-27_fenix_a320_dev_update_27aug21/)
[Fenix A320 – Dev Update 06AUG21](https://fenixsim.com/blog/entries/2021-08-06_fenix_a320_dev_update_06aug21/)
[Feature Review: HYD/FUEL](https://fenixsim.com/blog/entries/2021-07-23_feature_review_hyd_fuel/)
[Feature Review: MCDU/FMGS](https://fenixsim.com/blog/entries/2021-07-16_feature_review_mcdu_fmgs/)
[The Fenix Simulations Airbus A320](https://fenixsim.com/blog/entries/2021-07-12_the_fenix_simulations_airbus_a320/)
© 2026 FENIXSIM LTD. ALL RIGHTS RESERVED.[PRIVACY NOTICE](https://fenixsim.com/privacy) · [TERMS AND CONDITIONS](https://fenixsim.com/legal)
[Instagram](https://www.instagram.com/fenixsimulations/)
[Facebook](https://www.facebook.com/FenixSimulations)
[Bluesky](https://bsky.app/profile/fenixsim.com) |
| Readable Markdown | [](https://youtu.be/XCCarfZd8UU)
Hi everyone, a little dev update for you all on our incoming NEOs and other stuff.
Our NEOs aren’t going to make the end of this year, work is progressing along swimmingly and at good rate - but we’ve done a little bit of project reorganisation internally after some pretty intense and direct feedback from the community and through our ticketing system about the state of a couple of items on our CEO product line.
1. The poor implementation of VNAV.
2. The inability to handle a basic level of user state saving due to limitations on our side.
3. The old ECAM infrastructure leaving long standing latent bugs some of which have hung around like a bad smell for the last couple of years.
Primarily VNAV, and after a very strong showing of passionate community opinion on this topic, we felt the communication to us was pretty clear - and so we opted to reorient a couple of our developers off the NEOs and into lending a hand to prepare new VNAV and the dependant new ECAM infrastructure as a software update, ahead of the NEO release. Some of you may wonder why VNAV is so important, or what was wrong with it in the first place - while we did get it to a place where it was acceptable to some, it is inherently, underneath, some very old and generalised architecture - leading to path construction behaviour that was inconsistent with the A320 as a whole. The way it drew its decelerations (when, where and how) - the way it used and produced perf data, for example EFOB (some of you know this famous bug) - to the principals with which it builds the individual blocks of the vertical path (missing things like pressurisation segments, but also decel placement and logic!) - there’s a lot of important stuff here and it really does add or remove a tonne of character from the airplane’s behaviour in what I personally would consider, at least from the flight management perspective, the most scrutinised part of an airliner flight. Now, as for new VNAV, we've even been able to capture behaviour we've only seen represented in the real aircraft, or in full fidelity level-D simulators. I will talk more about VNAV and what this all really means when we start preparing it for deployment - but I think it’s a very valuable and critical upgrade for not only our CEO, but just serves to make the NEO a much better product too.
The benefit, of course, is all our new infrastructure for both the ECAM and VNAV will be battle tested ahead of their usage on the NEO products, which should mean a much smoother entry into market for the NEOs. It also keeps things a little neater when considering post release support - there’s less chance we get caught with a problem on NEOs and have to fend off dealing with that.
The downside is the basic trade-off between resources and time. From a development perspective, this is a reshuffle; we've always prioritised looking after products you've already paid for, before asking people to part with their money for more, and this trend continues here
The above update has now entered limited internal testing with some SME testers attacking both VNAV and the new ECAM in separate small groups, with a view toward pushing into large scale beta once we’re happy with the results from our SMEs.
The NEOs are in a place where they will be ready to drop into wider testing once we release new VNAV and the new ECAM infrastructure to you all, so don’t panic too hard - we’ve also got some experimental features in dev for that package which we’re quite excited to show and talk to you about.
As for state saving - this involves much more than just synchronising the switch and button positions, and work in this area is moving along well also. We plan to have this in your hands after the VNAV and ECAM infrastructure update.
I don’t think anyone is really happy about having to eat their vegetables before dessert, although calling new VNAV and all this infrastructure work “vegetables” is maybe a touch too far - they’re very real, very tangible, and much needed improvements to the product you all have now.
We’ll do a bit of media around VNAV and ECAM - so look out for that closer to when we deploy the update - then after that we’ll get into the [fun bits](https://youtu.be/XCCarfZd8UU). Thanks for the patience and understanding\! |
| Shard | 85 (laksa) |
| Root Hash | 8850130616415798085 |
| Unparsed URL | com,fenixsim!/blog/ s443 |