Since updating the Fenix A320 to the last version (214) I’m experiencing the following issue:
When reaching the thrust reduction altitude, the plane does not react anymore when moving the throttle to the “climb” detent. The indication in the PFD keeps flashing. In addition, the ND freezes and the plane cannot be controlled anymore in a proper way.
!!! This happens only when there is an activated flight plan and all weight and speed data have been entered in the MCDU !!! This is independent from downloading a plan from Simbrief or manual data entry.
!!! It happens regardless whether the AP has been engaged or not !!!
!!! It does not happen in selected mode!!!
Of course I completely and properly de-installed and re-installed the A320 without solving the problem.
I have been in contact with the FENIX support and all possible throttle problems could be excluded. The problem anyway occurs only with the FENIX A320. All other planes work fine (e.g. FBW, Asobo A320neo, ToLiss in Xplane11).
The FENIX support has escalated the problem to developers, but there is no reaction anymore for a while. Guess they have more important issues to solve (new version…)
Is anybody else experiencing the same issue? Any idea what the problem could be and how it could be overcome?
No issues here, that update came out quite sometime ago so I would suspect if it was a common issue we would have heard about it.
Did you update overtop of the original aircraft or did you completely remove the Fenix first and perform a clean installation (which was recommended by Fenix).
Also, have you tried with an empty community folder to rule out any add-on conflicts?
Just took off from MKJP in the Fenix A320, no issues as per usual.
I did a clean re-installation several times with complete de-installation, search for any remaining files and emptying the community folder. No success.
The issue is apparently linked to something in connection to the thrust reduction altitude. When I lower the thrust to ‘climb’ before reaching this altitude (1500ft), the PFD shoes a green ‘climb’ as usual. Upon reaching 1500 feet, ND + PFD freeze, the plane itself keeps moving.
ND and PFD unfreeze upon deactivation of the AP, moving the throttle to Idle and back to TOGA and reactivation of the AP. The route is still in the MCDU, but not active and without altitudes.
In summary it appears it is just reaching the thrust reduction altitude which is irritating the system.
As written already the FENIX is the one and only plane which shows a problem. All other add-ons work fine, such as the Flybywire A320 and the Asobo A320neo. Also the ToLiss A321 in Xplane11 is ok.
I appears that I have won in the lottery and hit a FENIX bug which shows up only in specific circumstances, whatever that might be. Unfortunately that means for me that I can write of this purchase…
Sometimes reset Fenix license may help with fresh new installation. Download package again and install without reset license might keep old config, cache or roaming data… hidden somewhere you never know.
Thank you very much for your hint. I performed the proposed licence reset, searched again for any remaining fenix or fnx files, emptied the community folder and downloaded + installed again the Fenix software.
Unfortunately this did not overcome the issue. The Fenix behaviour is unchanged.
I have no problem at all with the Fenix A320.
I fly it regularly and never had any issue. Today I flew 2x3h leg from Keflavik to Amsterdam and back and I had no problems at all and wasn’t able to replicate your problem.
Are you moving the throttle in the cockpit manually or are you using a sidestick controller ? If you use a sidestick e.g thrustmaster, make sure you calibrate it correctly using the MCDU.
For a long time I also had no problem with the Fenix A320. The issue started a few days after installing the latest release 214. Before I still used version 1.
I’m using a sidestick controller. But it is certainly not causing any problem. I checked this already in cooperation with the Fenix support.
Exactly same problem on my side. I did clean reinstall, works again for 1 time (maybe lucky) and now freezing again when changing mode to FLEX to climb just after takeoff, all screens freeze.
Always using V1.5.(…).214 since seveval weeks, and got problem only since yesterday.
I got too a difficult to get my block FUEL after click on PLANNING. Is it your case @captainheinz533 ?
In my case, the problem seems to occurs only if I got a problem to get my block FUEL predict.
On 5 test takeoff this afternoon :
Fly 1 : didn’t get block FUEL after click on PLANNING → put it manually from the briefing, screens freeze when FLX to CL.
Restaring MSFS.
Fly 2 : didn’t get block FUEL after click on PLANNING → put it manually from the briefing, screens freeze when FLX to CL.
Restaring computer.
Fly 3 : get block FUEL immediatly after click on PLANNING takeoff OK !
Fly 3 : get block FUEL immediatly after click on PLANNING takeoff OK !
Fly 3 : get block FUEL immediatly after click on PLANNING takeoff OK !
Using airbus controller quadrant + only VR Quest mode + FlyBywire (problem occurs on VATSIM too).
The issue is solved for me. Starting from your findings I noted now that the problem occurs, when not ALL MCDU data fields are filled properly. As soon all (!) fields are filled, everything is fine. When not, freezing occurs on Flex–>Climb at reduction altitude.
The indicator for proper data entry is the appearance of flight altitudes in the MCDU FLP page.
In my case, it was for instance an empty cost index field that caused a problem.
