I installed the BFU this morning and it looks great.  However I seem to have one bizarre issue I have not had before.  My nose gear steering is all messed up.  Because my PC gets used my multiple people in the household and used for multiple people purposes I am forced to have a somewhat basic setup.  No rudder pedals just an old school CH Flight Stick that actually works well and the keyboard.  I rely on the keyboard functions for some functions and its set to default.  So the 0 and Enter keys on the numerical keypad control the nose gear steering and the 5 key is supposed to center the nose gear.  Since the BFU update trying to control the plane on the ground is almost impossible.  Hit the 0 or Enter Keys and the nose gear just keeps on turning sharper and sharper until it hits the locks.  If you mess with it you can sort of get it to stop but the nose gear will be off center.  Its almost impossible getting the nose gear to center whereas before pressing the 5 Key centered it.  This how most planes in MSFS are and how previous versions of the Fenix A320 worked.  I think its set as default for a fancy tiller setup but not everybody has that.  Might need an option under Controls for simple nose gear steering.  This is in FS2020!

       

2 hours ago, CaptainQ8 said:

First of all I have to say that the immersion Level is just insane. So thx to the devs. Besides that I have one observation which I want to discuss. I am not a real airline pilot and never flew the real thing but i have flown countless hours on the Toliss fleet, FSLabs and a also a few rides in a fully fledged Full Motion Simulator.

I know the fly by wire systems but still there should be some little inertia after you let go of the stick. Toliss, FSLabs have that. The Fenix feels to me still really snappy and locks in without the feeling of inertia. This small Moment of inertia is very subtle and certainly not a deal breaker but still.
 

Before the BFU this behaviour in flight model out was also mentioned by blackbox711 (former A320 captain). I have the feeling that little inertia is still missing. So what’s the opinion ? Is it just me or are you noticing this also?

It is an interesting and infinite topic, really. I will share from my context about our work, but I am obviously a biased entity, so please take that into account with what I say and consider it on that basis - hence why I will also not draw any direct comparisons amongst the other products you mention. I will be clear to say also that I'm not entirely familiar with how those products handle, I used FSL back in the P3D heydays, years ago and remember a fairly minimal amount. These days I keep my window of reference outside of any other products to remove any bias - ultimately our goal is to build an Airbus A320 - the ground source truth for us lies in the real aircraft and actual data in that sense, but there is more to just the data, of course.

To start with, the math on these aircraft is actually both reasonably well defined, and fairly easily available to view. Yes, the actual inherent specifics are not - but as a generalisation, looking into various research papers you can find on google, you'll find the authors of Airbus' fly by wire systems, and other researchers, describing down to the math how these things function. With that in mind, as far as the roll axis goes, imo, in the real world a roll axis that continues rolling after the sidestick is neutralized to the point that you can actually perceive it is not ideal at all. This is imprecise - in this case the airplane isn't going where you ask it, it's going near where you asked it and continuing to roll after you've asked it to stop. This imprecision is not something I can say I have noticed in the data when directly comparing roll rate to sidestick deflection - the airplane's commanded roll and the sidestick is actually quite remarkably overlapped - yes there are certainly damping factors, but it still overlaps tightly. This makes sense to me given the entire loop, that is, input to output - and it makes sense to me BECAUSE of the input. Look at it closely and study it a bit and you sort of begin to understand where the problem is - the absolute most fundamental part of the entire control loop _is_ the control input, to me at least, and in light of that the sidestick on the A320 is really quite impressively mechanically engineered. https://youtu.be/rHzl34Kjj9o?t=123 < check that out - it's a real sidestick - and note how it recenters. Gives you a gist of the damping on this thing. There are also some interesting tidbits that will lend you an idea of quite how thought through the design of the sidestick damping mechanicals actually are - for example, even roll is asymmetric on a hardware level, forget about pitch vs. roll - the roll tension springs for inboard deflection vs. outboard deflection are different because your arm is naturally stronger in one direction vs. the other, so the resistance is slightly stronger in one direction. 

So, there is your weight and inertia that pilots are talking about - it's not in the fly by wire - it's here. That smooth return to center, the weight off center, all that good stuff. The fly by wire is just doing as it's told. Now, how each maker chooses to transpose this to desktop joysticks is a different story. I have my reservations about imprecision when attempting to build this into the fly by wire layer as mentioned above - I find it critical to be precise in the application of flight controls. Our approach is charted out in a section that ultimately was cut from the main BFU video, but if you're still interested in this topic after reading my rambling - take a look at this, it's the unlisted cut section - it describes our approach to this: https://www.youtube.com/watch?v=LkgpqFZL5Bc

 

1 hour ago, bigifooti said:

i just clicked update and waited till it was done. The liveries will also require an update. Use the Livery section in the Fenix Installer app (not the old seperate livery app). 

Thanks mate, it worked! For the liveries too.

Flight model feels great on approach. It was very good before, but I definitely notice an improvement after BFU. But the biggest improvement is in the flare. I love it now - no more endless floating. 

I put it up there with the iFly 737 MAX. These two have the best flight model of any airliner in MSFS.

Edited July 31, 2025Jul 31 by RNAVV19R

Here is an update to my nose gear steering issue.  I loaded up the sim for a flight and interestingly the nose gear was working fine this time.  Its a bit slower than most aircraft and the 5 key does center the nose gear but its a bit slow.  So it takes a bit more technique to master than many other aircraft for MSFS.  Its either its operation took my by total surprise or maybe it did not load up properly the first time.

Nice airplane and very much improved.  I think its airplane of the year!  

 

One feature that I was hoping would be included in the BFU was v1/v2 callouts by the PNF.  Why do you think this feature is not being implemented in the Fenix aircraft ?

8 minutes ago, zachlog said:

One feature that I was hoping would be included in the BFU was v1/v2 callouts by the PNF.  Why do you think this feature is not being implemented in the Fenix aircraft ?

Because its most likely low priority and to be honest I would agree. More important things to sort first or get added.

Edited July 31, 2025Jul 31 by carlanthony24

Anyone else having issues with the passengers loading and gsx integration?  Mine never seem to start, fuel loads, baggage loads then the passengers do not.

 

 

Is there any further information on this topic of the changelog?

• Improved livery specific setting loading. Now some settings are always loaded from the livery, and some settings are persistent (work will continue in this area)

Persistency adds a lot of fun, just like the A2A planes, where the switches, fluids and maintenance are logged between simulator sessions. It helps develop a sense of a "real" aircraft when after a few sessions we need to top up the oil, or the oxygen levels, or the chances for a random failure add up to an event...

Congratulations on the release, Fenix Team!!!

I'm ready for the NEO!

41 minutes ago, carlanthony24 said:

Because its most likely low priority and to be honest I would agree. More important things to sort first or get added.

Priority is certainly a key consideration.  It's just that they already have callouts implemented when landing so adding the v1/v2 callouts on takeoff does not sound like a major development effort.  From my standpoint, enhancing the visuals, i.e., watching the PFD, with audible cues is a big help.
Thanks.

55 minutes ago, zachlog said:

Priority is certainly a key consideration.  It's just that they already have callouts implemented when landing so adding the v1/v2 callouts on takeoff does not sound like a major development effort.  From my standpoint, enhancing the visuals, i.e., watching the PFD, with audible cues is a big help.
Thanks.

The callouts on landing come from the aircraft itself. 

They simply don't model pilot callouts. 

3 hours ago, carlanthony24 said:

Because its most likely low priority and to be honest I would agree. More important things to sort first or get added.

Yeah but in the scheme of things, it has to be a pretty easy feature to code and add in.   I think it would be nice to have as well.   

51 minutes ago, 11bee said:

Yeah but in the scheme of things, it has to be a pretty easy feature to code and add in.   I think it would be nice to have as well.   

Most say it should be easy. Frankly I don't have a clue about coding but if it was simply easy enough you would think they would add it or have already done it don't you think? A quick Google says it could be easy but can also be complex. All we know its on the to do list. It would also be nice to have MEL, GPS jamming to name a few. Its like people were saying its easy to just add a sharklet yeah right.

What the hell is a BFU ??

6 minutes ago, Beagle12 said:

What the hell is a BFU ??

It's the acronym for "Big Fenix Update", which is what they named the release that introduced Fenix product compatibility with MSFS 2024 and enhancements applicable to both MSFS 2020 & 2024.