22 minutes ago, Noel said:

Variant and livery?  

a320, I think Sharks and a Delta livery. Boston is the airport I fly out of the most and the only time I had a problem with the AP engaging I had messed up the departure so bad I was drastically underspeed.

The livery isn't going to make a difference.

There is a systems reason it's not engaging the AP. Without a video it's hard to tell.

What SID were you on?

Edited July 2, 2025Jul 2 by BrammyH

In FS2024, the Fenix VC textures don’t appear as clean and sharp compared to how they looked in FS2020. I’ll post a screenshot later to show what I mean.

Also, at night, when turning on the BATs, the EXT 1 and 2 "AVAIL" lights bloom excessively. This might be related to the sim itself, since FS2024 currently doesn’t offer an option to disable bloom.

Edited July 2, 2025Jul 2 by LineDX

I also experienced issue with plane going out of control when I pressed a button on my flight stick, and it turned out that 2024 auto assigned bindings to my controls and I didn't know about. So I had to go through each one and delete what 2024 assigned and now all works as should.

Noel,

Whenever I have issues with the AP engaging after takeoff in the Fenix A320, it is because the runway heading is such that it deviates too much from the first leg of the flight path. The solution is to adjust your heading after takeoff to provide an intercept with the flight path. At that point, the AP should engage. 
I have found this to be the case at KBOS and other airports. If this is the source of your issue, know that this is part of the aircraft systems’ design, and not a bug. 
Rich

4 hours ago, BrammyH said:

a320, I think Sharks and a Delta livery. Boston is the airport I fly out of the most and the only time I had a problem with the AP engaging I had messed up the departure so bad I was drastically underspeed.

The livery isn't going to make a difference.

There is a systems reason it's not engaging the AP. Without a video it's hard to tell.

What SID were you on?

I forget as I don't fly out of Boston very often.  I mentioned the livery because later in a different livery, but different airport no issues.  I've flown this plane maybe 30x or so now and had no issues until this time.

2 minutes ago, Noel said:

I forget as I don't fly out of Boston very often.  I mentioned the livery because later in a different livery, but different airport no issues.  I've flown this plane maybe 30x or so now and had no issues until this time.

Do you remember what runway, and where you were going? I know Boston well enough I can figure out the SID.  Most likely it was PATSS7 or  SSOX7

It was 33L, HYLND7 to CYYZ

1 hour ago, rlashier said:

Noel,

Whenever I have issues with the AP engaging after takeoff in the Fenix A320, it is because the runway heading is such that it deviates too much from the first leg of the flight path. The solution is to adjust your heading after takeoff to provide an intercept with the flight path. At that point, the AP should engage. 
I have found this to be the case at KBOS and other airports. If this is the source of your issue, know that this is part of the aircraft systems’ design, and not a bug. 
Rich

Thanks Rich.  Seems funny here w/ this SID as the first leg doesn't deviate much:

7 hours ago, cooperwarner8 said:

Anyone at all noticed the steering issues on the takeoff/landing roll. When it starts to speed up a bit its very slow to respond to steering inputs and wants to swerve off the runway significantly

I get this as well - Its the only aircraft that is is this twitchy on the ground. I just adjusted the response curve for my rudders to soften the inputs and that largely counteracts the issue.

Thanks for all the responses, I'll check more closely but I don't actually use any mappings in 2024 itself at all actually, everything runs through spad.next and they simply work across both sims, the AP also disconnected mid cruise, I understand the nav intercept relies on somewhat matching heading post takeoff but that's not the issue here.  In any case based on the replies here nobody seems to have bugs really with the Fenix so that's good to have confirmed.

 

 

3 hours ago, KL Oo said:

I get this as well - Its the only aircraft that is is this twitchy on the ground. I just adjusted the response curve for my rudders to soften the inputs and that largely counteracts the issue.

I just played around with it a bit more and I noticed the nose wheel actually doesn't turn on the takeoff, only the rudder. This would explain why its hard to steer straight on the runway and why it's sluggish to move. It does move during taxi.

Is this normal behavior?

1 hour ago, cooperwarner8 said:

I just played around with it a bit more and I noticed the nose wheel actually doesn't turn on the takeoff, only the rudder. This would explain why its hard to steer straight on the runway and why it's sluggish to move. It does move during taxi.

Is this normal behavior?

Yes. The nose wheel doesn't turn on the take off roll..

Fenix works great in 24 and I saw someone mention the Max8 from Ifly.  Yep, that works great too.

Jase

Finally found what was causing this issue, there are some default mappings for the keyboard in 2024 for ailerons and elevators being mapped to the numpad keys, not sure if this was the same in 2020 also, maybe I deleted them but I use those keys for my cameras so of course switching cameras meant manipulating flight surfaces.  It still doesn't make sense fully as this did not happen when actually switching cameras using the numpad, it happens while not doing anything at all, just while AP cruising without touching anything but somehow this was interfering just by the mappings existing, I hope that is but so far the problem has not come back.

 

I bought the Fenix A320 to fly shorter routes until the PMDG 737 is released for 2024.  I spent a lot of time studying how to fly it because I have never flown an Airbus apart from the Inibuilds A350, which I think is fantastic.

Most flights I have some sort of problem like warnings on the front panel, The latest I had today was an overspeed during cruise, this may have been because the throttle moved away from 'CLB' mode.  Anyway I do not enjoy flying this aeroplane due to the many problems I'm having, so have just deleted it from my hard drive.