3 hours ago, Bobsk8 said:

She is back as a moderator on their Discord channel. 

She can not change the attitude of that bunch over there. I gave up.

Having mixed results with Block 2 now. Worked out the issue with AP disconnects. But now I have a new problem where I cannot get the a320 to descend in managed mode when at (or before) TOD. Aircraft climbs to cruise altitude with AP engaged just fine. While at cruise altitude, I enter the lower, desired altitude for the IAF with altitude knob, which I press in (arrow up) with the mouse when about 10 nm prior to TOD. The managed mode dot “o” does not appear and the aircraft continues to cruise. I have a support ticket with Fenix for this, but I wonder if any other Avsim pilots have had this experience using the Block 2 a320. Never had this problem with earlier versions. 
Rich

23 minutes ago, rlashier said:

Having mixed results with Block 2 now. Worked out the issue with AP disconnects. But now I have a new problem where I cannot get the a320 to descend in managed mode when at (or before) TOD. Aircraft climbs to cruise altitude with AP engaged just fine. While at cruise altitude, I enter the lower, desired altitude for the IAF with altitude knob, which I press in (arrow up) with the mouse when about 10 nm prior to TOD. The managed mode dot “o” does not appear and the aircraft continues to cruise. I have a support ticket with Fenix for this, but I wonder if any other Avsim pilots have had this experience using the Block 2 a320. Never had this problem with earlier versions. 
Rich

I have had the same problem twice today. 

Just noticed  this  just  now, maybe  it  was  in  the  last  version,  but  when  the  passengers  leave  the  aircraft  they leave  foot  prints  on  the  carpet  of  the  isle  as  they leave.  So far  having  no issues  with  the  new  version  as  of  yet

Edited March 11, 20242 yr by pete_auau

7 hours ago, rlashier said:

Having mixed results with Block 2 now. Worked out the issue with AP disconnects. But now I have a new problem where I cannot get the a320 to descend in managed mode when at (or before) TOD. Aircraft climbs to cruise altitude with AP engaged just fine. While at cruise altitude, I enter the lower, desired altitude for the IAF with altitude knob, which I press in (arrow up) with the mouse when about 10 nm prior to TOD. The managed mode dot “o” does not appear and the aircraft continues to cruise. I have a support ticket with Fenix for this, but I wonder if any other Avsim pilots have had this experience using the Block 2 a320. Never had this problem with earlier versions. 
Rich

1) Were you in NAV mode? It won't work in HDG mode.

2) Was a vertical path (VDEV) shown on the PFD? If not, something was wrong with your vertical path (i.e. it wasn't able to calculate one, likely due to disconnections in the flight plan).

3) Were you 100% in ALT CRZ mode (i.e. did you reach your programmed cruise level)? If you stopped your climb before reaching your programmed cruise level, it cannot do a managed descent.

Edited March 11, 20242 yr by Fiorentoni

For me the Fenix flies perfectly by the book. No problems whatsoever (except for one time the displays woudln't come on and I had to restart MSFS). Judging by the stuff people post on Discord, most problems are actually user errors. This is to be expected, because the A320 is a very complex flying computer and it doesn't like if you do something "out-of-the-box", especially in regards to the managed modes. Some things might have actually been fine on v1, because the system logic wasn't in place yet, so that's also a possible factor. Of course, some things are just bugs, but it's a bit harder to differentiate compared to e.g. the good ol' 737.

14 hours ago, ConstVoid said:

The button on your stick must be set to 'AUTOPILOT OFF', not any other function. If that is done the first press will disconnect the AP and the second will silence the alarm (after a minimum of one cavalry charge I believe),

Finally managed to save it once I set my TCA up from scratch in the settings and now it works as normal. I think there was some kind of conflict as I had copied the settings over from the FBW, something I never do, but I did in a rush the night I downloaded the aircraft for a test flight.

 

38 minutes ago, Fiorentoni said:

For me the Fenix flies perfectly by the book. No problems whatsoever (except for one time the displays woudln't come on and I had to restart MSFS)

Yeah the managed VNAV is very accurate, I was hovering over V/S mode all through my descent last night and I never had to touch in the end until the last few 1000 feet which is normal on the LOGAN2H into Heathrow.

I also had a strange bug when entering the cockpit, all the lights were on and none of the buttons on the overhead panel worked, quick reset into the main menu and back and it was fine.

2 hours ago, El Diablito said:

Yeah the managed VNAV is very accurate

Indeed. Descending at the computed TOD marker has never failed me thus far with V2. 

New Fenix Update is out - Change log at:

https://fenixsim.com/blog/entries/2024-03-11_v2b2_update/

Edited March 11, 20242 yr by Zangoose

15 hours ago, El Diablito said:

My money is on an update tomorrow or Tuesday

not bad

26 minutes ago, Zangoose said:

New Fenix Update is out - Change log at:

https://fenixsim.com/blog/entries/2024-03-11_v2b2_update/

Wow these dudes don't **** around and improve their product without releasing more gimmick for more money. Hats off to them.

Once I'm done with my current flight in another, undisclosed aircraft, I'll jump into the updated Fenix and test the following:

Quote

Tuned alpha protection and recovery (should fix AP not engaging spuriously issue)

Not sure how I can test for this though:

Quote

Improved “zombie MSFS process” resistance

 

Alpha floor with iae during take of flaps 3 you can easily have this protection alive 

I found iae was less power than cfm after lift of, and if you don't aware of that speed decrease strongly 

The Autopilot disconnect and not being able to re-engaged might be a nuisance but it is very easily solved. All those tips about moving all the control around are just over the top. A decisive, quick and short input on the sidestick full forward is totally sufficient.

This is how I resolve it, when it happens and yesterday I even could help a fellow pilot out on VATSIM after I heard him tell ATC that he lost his AP on Approach.