weird, before the updates everything was perfect for me but now its unusable in VR 
Hello guys
Before the update I had no big issues with this wonderful plane, after it, I have lots of failures, I tried to repair them as the Fenix webpage suggests, click CLR button and it removes the failures, but it didn’t work, at least for me, I post the page here in case it can help you: https://kb.fenixsim.com/failures-in-the-fenix-simulations-airbus-a320.
The only solution I found was to select the maintenance mode, but my Goodness, it takes ages to repair the failure, like 30 minutes each one, it seems they went to shop the pieces. I understand they want to make it as real as possible, and these things can be useful for others, not for me, what I want is to fly, no to be dealing with failures and more failures , or wasting my time waiting for the plne to be reapired.
1 Like
For me, it’s not just displays freezing, but the entirety of the aircraft systems breaking down and no longer working. Oddly, it’s not limited to specific flight phases, but to any possible input in the FMGS. Had it crash while trying to enter fill out INIT A, INIT B, PERF, PROG pages. Usually it stops working when I try to enter the altitude in INIT A.
Tried reinstalling the addon as well as running it inside an otherwise empty Community folder, all to no avail.
1 Like
Hopefully this gets fixed, couldn’t fly since last update.
Is anyone else getting CTD’s during descent having paused at TOD for while? Has happened on my last two flights now!
Hope so too, until then the Fenix is shelved again.
Which is kind of sad, because i bought it on launch weekend and the main reason i practical never flew it much was the really bad performance.
And now it gets improved and the flight model gets fixed and i still cant fly it. 
1 Like
Why shelving it, the Fenix flies perfectly. 
When the flight path is too steep the autopilot just cannot follow the inserted altitudes of the waypoints flight path (of course it will try, but it will not sink more than 1500ft per minute or so because of a safety limitation, that´s why the MCDU precalculates that the Airbus will not be on the preplanned altitude of the next waypoint because of the autopilot descent rate limitation.)
I have this problem very often when Flight Planner - Flight Plan Database only gives me a few waypoints and a very steep descent down from 39.000 ft, and therefore changing the waypoint altitude manually (or manually inserting a waypoint to begin the top of descent more early) is necessary, and everything is fine again.
A smooth descending Airbus is a happy Airbus.
Can the Fenix A320 be ground started (failed APU scenario) , or is this not modelled ?
I don’t get CTD or displays freeze, but every other time the Fenix EFB is blocked at the start, being black with only the Fenix logo and not responding to anything. At the same time, all other systems work fine.
The absence of APU is not a “NO GO” cause.
The procedure to start the aircraft without APU is provided by the FCOM/FCTM and is modeled by Fenix on the A320.
See this video:
Any updates from Fenix on a remote MCDU for touchscreen use? Or if they are planning an A321?
But the Juneau Airport SID is a no-go
Absolutely LOVE that SID. And I don´t fully understand why we survived this SID - probably because only two flight guests only 5 tons of fuel and cargo room only half-full…
Luckily only Mulder and Scully were today´s flight guests, that´s why we survived the Juneau SID
Landing on PAKT airport.
The flaring of the new flight model is perfect in CAT3. I would only cats trust to land my Fenix!
I wonder why Mulder and Scully are not sitting next to each other… The Fenix Airbus clearly needs a BBJ/charter flight function for the passenger cabin. (And of course I would love to see a BBJ cabin too - with gaming room!)
That would be sooooo cool - but unfortunately I read no intentions or even hints that they plan to upgrade the Fenix to the whole A319 / A320 / and A321 freighter family, not now not in the late future.
Anyone else not getting the volumetric lighting in VR?
I do have this problem of not being able to control the aircraft too. It all started after the latest update.
Unable to fly after. It’s uncontrollable as in MCDU not accepting any input. Reinstall done twice and empty Community Folder method to sort things out made. I hope Fenix technical engineers read this thread tho lol.
Something thoughts to try:
Did unplug your controller online and replug them again? Did you switch them to the default profile? Did you delete rolling cache?
Did you rename the community folder to community.old and restart?
There is a fenix related folder somewhere in c:\Users\YourUserName\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\ . Delete that after uninstalling the fenix and reinstall the plane.
Hopefully this maybe helps
Thank you for the information
Only now i discovered that this aircraft runs way better on dx12 i am now getting 40 to 50 fps on the ground with fsltl and is buttery smooth. While on dx11 i get 25 to 35 and full of stutters.
Same problem here . Any fix ?
Same for me. Not going back to DX11.
Please the fix the com3 124.850 bug which automatically tunes to salinas atis loop. Turning off com3 doesn’t fix it. You can even turn off com2 and no fix . And u can even change the freq and no fix . Please fix this thank u