Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Fenix update V2.2.0.403

Featured Replies

2.2.0.403 A new update is now available via the Fenix Installer, this has a couple of optimisations that nets us a bit of high-priority CPU time, we hope that this may help some affected with the oscillations free up a bit of headroom and therefore alleviate the issue, let us know if it helps please! Additionally, some fixes to GPS data, and for those flying in the US - switching STARs should now be a bit easier 🙂 Finally, FLX has learned how to behave itself a little better, so improvements all over the airplane really! Enjoy 🙂 @everyone Avionics and Systems

  • Optimised internal scheduling of display rendering
  • Added cargo distribution to loadsheet
  • Added AOC FREE TEXT
  • Added AOC ATIS request via VATSIM and IVAO
  • Added new source of GPS ephemeris data - updated NAVSTAR tracking algorithm with more current data, fully prepared for full GNSS constellation (Galileo/Beidou/etc) when the real A320 is able
  • Improved internal W&B code to better support sharklets and ACTs
  • Improved conditions for auto-tuning ILS
  • Fixed approach transition altitude not being based on the entered QNH
  • Fixed values like 0.11 being rounded in the RNP field
  • Fixed STAR not being reloaded or cleared after changing runway
  • Fixed aircraft freezing during rare circumstances when using the ACARS printer
  • Fixed S speed being impossibly low at around 45 T gross weight
  • Fixed SayIntentions ACARS not connecting if a Hoppie code wasn’t entered
  • Fixed CLOSEST AIRPORTS not showing an EFOB
  • Fixed “HUNDRED ABOVE” and “MINIMUMS” playing when an MDA/BARO was entered on the ground
  • Fixed ACARS client not correctly respecting “invalid login code” responses
  • Fixed ALPHA FLOOR engaging on approach when below 100 ft RA
  • Fixed SPD LIM not showing with a dual SFCC failure
  • Fixed certain speeds showing when they shouldn’t with a dual SFCC failure
  • Fixed cross track error not showing on the ground
  • Fixed ECP ALL button logic (it shouldn’t “remember” the last selected page)
  • Fixed formatting issues of the ATC unit on DCDU
  • Fixed FUEL X FEED OPEN light appearing when the valve isn’t fully open
  • Fixed tailstrike protection chevron not being amber
  • Fixed physical BARO MODE switch becoming out of sync when linked
  • Fixed COM3 playing at 100% volume
  • Fixed HF2 transmit indicator lighting up when HF1 was active
  • Removed MAX FLT TIME limitation on yellow hydraulic low level (HYD RSVR ISOL VALVE INS)

Art and Sound

  • Fixed A319 & A321 safety card showing A320
  • Fixed flap rods in A319 and A320
  • Fixed overhead bin missing polys on high density cabin
  • Fixed odd coloured paint on the wing of the A319
  • Fixed ATC model not being said correctly in-game (incorrect localisation key)

EFB

  • Improved cargo distribution to target an optimal CG
  • Improved takeoff performance based on airport elevation
  • Fixed EFB being blank on start-up if the previous session was quit with the EFB “sleeping”

Flight and Engine Models Here we did a bit of work to the FADEC when it comes to FLX computations, some may have noticed a discrepency between the FADEC’s assigned thrust rating and what was actually achieved before - this has now been resolved by a thorough rework of the FADEC, but also with it’s associated data sources. Additional to this, as a bonus of giving something a rework - you get to improve certain other aspects too. You may now observe the FADEC rating subtly changing as you roll down the runway during takeoff, this is normal - the FADEC is continously computing the appropriate thrust output and therefore slighty varying EPR/N1 - this is now reflected across the range, but we’re still tweaking the IAEs a little.

  • Replies 38
  • Views 9.2k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • David Roch
    David Roch

    Fenix customer support is simply brilliant. Difficult to do better! The recipe is simple: conscientiousness, altruism and a lot of love for their product. Thanks folks !

  • BostonJeremy77
    BostonJeremy77

    Thank you for continuing support and updates. One of the best developers in business right now. Phenomenal. Will always support you guys. 

  • Just now, Oct 10 2024 **__2.2.0.421__** @everyone  Hello all, we come bearing the gift of a new engine! The CFM engine we initially selected for the A321 was the CFM56-5B2, but after mu

great stuff. thanks 

 
 
 
 
 
  913456

Fenix customer support is simply brilliant. Difficult to do better!
The recipe is simple: conscientiousness, altruism and a lot of love for their product.
Thanks folks !

- PC Hardware: AMD Ryzen 9 9950X3D //  Asus ROG Crosshair X870E HERO //  2x32Gb Corsair Dominator Titanium DDR5 6000MT/s CL30 //  ASUS ROG Strix GeForce RTX 4090 OC Edition // 4Tb Corsair NVMe M.2 MP600  //  Corsair 1600W PSU
Samsung Odyssey Arc 55" curved 165 Hz monitor.
- Simulator Hardware: VIRPIL Constellation Alpha Prime + VIRPIL VPC Universal Control Panel - #3 + MOZA AY210 Force Feedback Yoke + WINWING URSA MINOR 32 Throttle & PAC Metal + WINWING SKYWALKER Metal Rudder Pedals + WINWING Airbus FCU & EFIS + WINWING Boeing 3N PAP + WINWING MCDU-32 + WINWING PFP-4 + WINWING PFP 3-N + WINWING PFP-7. 

   

 

 

13 minutes ago, David Roch said:

Fenix customer support is simply brilliant. Difficult to do better!
The recipe is simple: conscientiousness, altruism and a lot of love for their product.
Thanks folks !

They are simply the best. Never complained about the SDK, or whats given to them on a platter and dug down and made a solid product.

FlightSim First Officer program will not work after Fenix update.   Bummer

 

 

 

42 minutes ago, Bobsk8 said:

FlightSim First Officer program will not work after Fenix update.   Bummer

It does for me, no problems here..

Thank you for continuing support and updates. One of the best developers in business right now. Phenomenal. Will always support you guys. 

Do you guys noticed it have a problem managing energy ? 

What i mean is i constantly need speedbreaks below FL100, up to the point i need to go flaps 1 and sometimes even until i go flaps 2. 

MSFS2020, 24, Fenix A320,  Ryzen 9 9950X3D, ASUS TUF RTX 5090 ,G.SKILL 64GB 6000MHz CL28

8 hours ago, roi1862 said:

Do you guys noticed it have a problem managing energy ? 

What i mean is i constantly need speedbreaks below FL100, up to the point i need to go flaps 1 and sometimes even until i go flaps 2. 

which of the A's? 319, 320 or 321? And do you mean during approach? I learned they behave differently in slowing down during approach. 

Phil Leaven

i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"

38 minutes ago, DAD said:

which of the A's? 319, 320 or 321? And do you mean during approach? I learned they behave differently in slowing down during approach. 

I own only the A320. Its very hard to slow down in particular below FL100. The 'more drag" message is almost constant on any approach. 

MSFS2020, 24, Fenix A320,  Ryzen 9 9950X3D, ASUS TUF RTX 5090 ,G.SKILL 64GB 6000MHz CL28

9 hours ago, roi1862 said:

Do you guys noticed it have a problem managing energy ? 

What i mean is i constantly need speedbreaks below FL100, up to the point i need to go flaps 1 and sometimes even until i go flaps 2. 

Yeah the aircraft just doesn't calculate enough time to slow down as well as descend. You can test this by removing all speed and altitude constraints so it can calculate an absolute optimum path. Then use basic rule of thumb of 1000ft altitude to lose x 3 + distance required to slow down to give what distance you should be away for given altitude and you will find that the path calculated by the fenix is just too steep. There is not enough distance to go down and slow down, so pretty much always will need the speedbrakes.

5 minutes ago, abennett said:

Yeah the aircraft just doesn't calculate enough time to slow down as well as descend. You can test this by removing all speed and altitude constraints so it can calculate an absolute optimum path. Then use basic rule of thumb of 1000ft altitude to lose x 3 + distance required to slow down to give what distance you should be away for given altitude and you will find that the path calculated by the fenix is just too steep. There is not enough distance to go down and slow down, so pretty much always will need the speedbrakes.

Yes. Thats pretty much describe it perfectly ! 

MSFS2020, 24, Fenix A320,  Ryzen 9 9950X3D, ASUS TUF RTX 5090 ,G.SKILL 64GB 6000MHz CL28

10 hours ago, roi1862 said:

Do you guys noticed it have a problem managing energy ? 

What i mean is i constantly need speedbreaks below FL100, up to the point i need to go flaps 1 and sometimes even until i go flaps 2. 

I flew RJTT to RJFF along the routing below in the updated A320-CFM model

RJTT/34R N0461F380 DCT TIARA DCT GUSRO Y20 KIRIN HAWKSE RJFF/34

No issues. I think i got one request for more drag but apart from that nothing indicating a substantial issue. Is the aircraft slippery? .. i would say yes but not anything unmanageable. Will do other flights today and see i guess.

AMD Ryzen 9800X3D/ Asus ROG Strix B650E F Gaming WiFi / Asrock Taichi 9070XT / 32GB G.Skill Trident Z5 Neo DDR5 6000 / 2x ADATA XPG 8200 Pro NVME / Arctic Liquid Freezer II 280 / Seasonic Vertex 1000w PSU / Lian Li LanCool II Mesh Performance / Asus VG34VQL3A / Topping E70 Velvet DAC & L70 Amp /Sennheiser HD660s2

Thrustmaster Boeing Yoke + TCA Sidestick + TFRP Rudders

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.