Fenix Update Released

[cavaricooper 2,490]

Rob-

Aim for the TDZ- the white rectangles past the Piano Keys. Enjoy Fifi! 
 

C

[sniper31 510]

Well, I have just installed the latest Fenix update, and I now I am having problems getting my flight plan to upload into the FMGC. It loads into the tablet fine from Simbrief, but every time I try and upload into the FMGC it says "Invalid Flt import" or something along those lines. I have never seen this problem since I have had the Fenix, and I have been a customer since it was first released. I installed the update and then rebooted my PC before running MSFS. I cannot figure this out. Running the version previous to this latest update, I did not experience this. 

Edited August 23 by sniper31

[WestAir 2,432]

11 minutes ago, bobcat999 said:

Which runway markings should we be aiming for to touch with the main gear?

Aim for the two large ones. You can land before or after those, but you have to land before running out of rectangular markings (the last skinny ones), or with runway lighting, before the end of the lights affixed over the markings.

If you're floating when you run out of lights or markings, go around. Though this is for 121 operations; In your GA aircraft you can land however you see fit, so long as it's safe.

[rob0203 678]

10 minutes ago, sniper31 said:

Well, I have just installed the latest Fenix update, and I now I am having problems getting my flight plan to upload into the FMGC. It loads into the tablet fine from Simbrief, but every time I try and upload into the FMGC it says "Invalid Flt import" or something along those lines. I have never seen this problem since I have had the Fenix, and I have been a customer since it was first released. I installed the update and then rebooted my PC before running MSFS. I cannot figure this out. Running the version previous to this latest update, I did not experience this. 

If you have lat / long in your flight plan it won’t load. Like 62N090W 

https://forums.flightsimulator.com/t/fenix-a320-unable-to-import-simbrief-flightplan-with-latlong-coordintes/539395

Edited August 23 by rob0203

[Tom_L 478]

8 hours ago, threegreen said:

What's the reason for the automatic nose down inputs anyway?

To my understanding it is to give the pilot the feel of a natural flare. As  aft- and forward sidestick inputs during the flight phase command g-load, it would feel different and require a different landing technique than in a conventional, non-FBW airplane. So they implemented flare mode at 30 ft. AGL, which basically lowers the nose, forcing the pilot to counteract that by pulling the stick in order to maintain the flight path. In Flare mode this input is directly transposed to the elevators by the flight computers. That mimics the behaviour of a non-FBW aircraft so that it feels natural for pilots.

Edited August 23 by Tom_L

[carlanthony24 310]

11 minutes ago, sniper31 said:

Well, I have just installed the latest Fenix update, and I now I am having problems getting my flight plan to upload into the FMGC. It loads into the tablet fine from Simbrief, but every time I try and upload into the FMGC it says "Invalid Flt import" or something along those lines. I have never seen this problem since I have had the Fenix, and I have been a customer since it was first released. I installed the update and then rebooted my PC before running MSFS. I cannot figure this out. Running the version previous to this latest update, I did not experience this. 

It could just be somewhere in the route it disagrees with so might have to input manually or find a different one.

[sniper31 510]

19 minutes ago, rob0203 said:

If you have lat / long in your flight plan it won’t load. Like 62N090W 

I will check this it. That might be the issue.

15 minutes ago, carlanthony24 said:

It could just be somewhere in the route it disagrees with so might have to input manually or find a different one.

Well, I would think of that except I have flown this same route back and forth yesterday and the day before in the 737 without any problems (it's CYVR to KLAX and return). I am going to check the route for LAT/LON as @rob0203 suggested. Report back in a few.

Edited August 23 by sniper31
EDIT: So, there is a LAT/LON waypoint in the flightplan. I will have to remove it and see if it will now load into the FMGC.

[Maxis 1,702]

Anyone have any issues with energy management and respecting constraints on the STAR/Approach ? I did a quick hop in the new version last night and struggled a bit with energy management.

The route was

RJAA/16R N0445F360 TETRA8 ENPAR Y16 TEPEX Y88 SUGAL Y20 KAMMY Y202 AMURO DEMIO RJOA/10 with the approach being RNP Z RWY 10.  Aircraft busted through the initial fix and most of the approach speed constraints pretty much there was a bit of a mini emergency going on trying to get the speed down when i should have been well within the speed constraints by the time i arrived at the Initial fix. First time i ever got caught out like that in the Fenix. 

I know that i should have been ready to intervene well beforehand in a situation like that but there was no prior indication there was something amiss (no add drag notice) until it was way too late on the approach. Or maybe this specific STAR did not have any/many speed constraints to control speeds before the initial fix. Was going so fast i couldn't even get the gears down.. everything was in managed mode up until the approach.

Edited August 23 by Maxis

[RALF9636 1,659]

1 hour ago, bobcat999 said:

 Which runway markings should we be aiming for to touch with the main gear?

In addition to what has already been said, I always find it helpful to have in mind that you should cross the threshold at 50ft AGL.

If you follow MSFS' dysfunctional PAPI or ILS you will rather be at 100ft or above over the threshold.

 

Edited August 23 by RALF9636

[Bobsk8 11,887]

28 minutes ago, RALF9636 said:

In addition to what has already been said, I always find it helpful to have in mind that you should cross the threshold at 50ft AGL.

If you follow MSFS' dysfunctional PAPI or ILS you will rather be at 100ft or above over the threshold.

 

I agree, for both the 737 and A 320, at very short final, I make sure I am a bit below the glideslope-PAPI. All my landings are fine. 

[sniper31 510]

3 hours ago, rob0203 said:

If you have lat / long in your flight plan it won’t load. Like 62N090W 

So confirmed, this turned out to be the issue. All is good now. Thanks!

[rob0203 678]

7 hours ago, sniper31 said:

So confirmed, this turned out to be the issue. All is good now. Thanks!

See here. You just need to use a different format and then it will work:

https://kb.fenixsim.com/invalid-f-pln-uplink-message-when-importing-from-simbrief

[Jeeper 73]

23 hours ago, DAD said:

did you check this https://kb.fenixsim.com/aircraft-hasnt-loaded-in-correctly or https://kb.fenixsim.com/everything-is-off-and-unresponsive-excluding-the-efb depending on your individual case?

Thanks for replying. I tried the suggestions but no joy. The plane is responsive, as in the tablet, buttons, and switches all work fine, it's only that the ND, PFD and other screens show nothing. They are not black though. The brightness knobs are changing the brightness of the screen, there is simply nothing displayed on any of them.

[jcomm 5,461]

Blackbox711 video:

FENIX Update Version 214 - Flaps 3 Drag and Flare Improvements - YouTube

I believe it's more or less shared by all of the rw pilots - 737 NG, A320 Pilot and BlackBox 711 - that indeed there are still discrepancies regarding the flare mode, and FLAP3 drag.

It's WIP I think, and B2 will probably bring better results.

Looking inside the aircraft flight dynamics file reveals a rather "poor" set of parameters, which suggests that this model was created with systems + Normal Law in the main focus. Alternate Law and even worst Direct Law are certainly week points of the present simulation.

Wonder if Fenix is considering updating the FM still during the MFS 2020 cycle to cope with those modes ?

Edited August 24 by jcomm

[Mejjo 33]

Is anybody still getting high cpu usage from the fenix app?

I am on the latest update.

Many thanks.