[A319, A320, A321] Fenix High-Fidelity Aircraft

Yesterday I was flying the Fenix on VATSIM and I was told to fly direct PA751 for ILS32. Those waypoints require you to program the RNP approach in order to access them in the FMC. However I couldn’t find the RNP approach in the FMC despite the fact that there is one (according to Navigraph). I’ve also had some instances where I only had STAR4C instead of STAR5C in the FMC. Usually these are identical so it doesn’t matter but it always leaves me feeling that it wasn’t a successful flight.

What do I need to do in order to update the database?

Do you have a navigraph subscription?
If so, then you need the navigraph navdata center app
In this app, make sure.not only to update the sim database but the fenix database as well.

1 Like

I do.

Oh wow, I didn’t know that Navigraph was connected to the Fenix. It’s amazing how hard it is to be a flight simmer lol. But thanks!

2 Likes

I’ve been measuring runways in my spare time

Seem to often be landing shorter than the Arrival Perf calculator suggests and being able to take an earlier exit than expected without much effort.

I’m measuring from the threshold (not displaced threshold or touchdown zone) as that’s where it shows the measurement from on the Arrival Perf :woman_shrugging:t2:

Airbus bush pilot flying in the most harsh Antarctic environment.
Excavations brought rare classified material to daylight and had to be flown out to a lab immediately.

3 Likes

I wonder if Arrival Perf works properly? Usually my actual braking distance is half the distance calculated in Arrival Perf.

Yes, often at least 300-400m less if not more unless I’m calculating something wrong.

Is anyone else experiencing abrupt rolls/banks and also V-approach/ILS-GS pitch angle changes with V2? It was much smoother with the latest versions of V1 but now it seems like we are back to the initial release of Fenix where AP rolls/banks and vertical pitch changes (when catching G/S or V-Nav appr.) are very sudden/abrupt! Hope they fix this.

Yes, in fact my last landing in LFPG was shameful (but survibable).

I always found the Fenix much harder to land than the FBW, which is just much more stable and predictable.

V1 was bad, V2 is a bit better, but still difficult and unstable, particularly in pitch and speed (I land manually, including throttles, but the AP also looks over-agressive). I don´t understand how it can loose speed so fast in an otherwise perfectly stabilized approach in good weather (no wind gusts). Dam, It even doesn´t loose speed that fast when I want it too, during descent, and then in short final, 20 knots bled out out of nowhere in two seconds (no wind gusts, no change in pitch, flaps or gear config).

And better not to talk about roll stability. I had to change the suggested “all linear” sensitivity setting in my thrustmaster A320 joke, because this thing would roll faster than a F22, and make landings almost impossible.

I know real pilots tested this flight model, so I just don´t know what´s going on, or what I´m doing wrong (certaintly, I don´t have theese issues with the FBW)…

I think most of what you said will be ok with practice. They do need to improve the flight model/dynamics. But my issue is mostly with AP related roll/banks and pitch angle change which is very abrupt in most cases and with v-nav sometime you go on a nose dive! Hope this is addressed sooner than later. In this sense V2 is performing significantly worse than V1 as AP was pretty smooth and good in V1.

How is my beloved Fenix doing? This week might be the week we get the first IAE screenshot.

Imagine how good these turbines will look like.

1 Like

I would rather love to see satcom antennas and sharklets than another engine variant :slight_smile:

2 Likes

Well we get a whole new external model, an updated cockpit/interior model, and a whole new external engine model. Not bad for free. The new engine model is the really exciting bit, should finally resolve the differences from realistic behaviour that are caused by trying to use Asobo’s engine model.

And we get sharklets next year anyway.

5 Likes

Anyone else get a lag / stutter / pause when touching down on landing? It happens every time for me, and only right when the wheels make contact with the ground. Otherwise the performance is great since the last update. But this landing touchdown stutter / pause for a micro second is driving me crazy.

when i enter for instance a speed/altitude restriction in the mcdu flightplan page for some reason since the update i automaticly switch to another page then the flightplan? when i then click on the flighplan page again it goes back to the last corrected entry and then i can finalise the plan…Very annouing when fi you want to land at a airport with a long aproach like LA fi.

I didnt experience this before the update.

ANother problem that sometimes occur is after the startup i get an alarm. CLick it away, every visable fault is gone, but the alarm is still going. (it doesnt occur often, but most of the time it’s a cargo heat alarm?)

That´s the cargo meat alarm. It goes off when the meat is perfectly done.


Bring on the IAE’s!!

See this post on landing/touchdown effects and how to find and to remove them.

I’m just hoping the full V2 will finally bring performance improvements.

2 Likes

Those files look like Asobo files and not specific to the fenix. I only have this issue in the Fenix. Literally every other aircraft is just fine on touchdown.