I am also wondering how is the VR performance after the update! I still didn’t update mine…
First Up, wow! Big thank you for all your work!
Did a complete clean up and deinstall of the previous version. Downloaded the latest version and installed it. Did a restart of the pc. Loaded the plane, did all settings . Restarted a flight and now I’m in my first flight, which is smooth as hell.
I‘m using TrackIR, no micro stutters , even while fast panning around . These new little sound additions, awesome!
No ctd caused by Fenix. I had one, but it’s from the simulator and know on other planes too (was while I’m popping out PFD and ND on second monitor)
Efb runs so much faster, feels right now!
And those crisp displays and fonts. ![]()
Did some more checks after updating to the latest version (with latest patch):
The Fenix A320 is comparable now to the PMDG737 and the FBW A320neo on my system (i5-10600K/3070/32GB). It is slightly below those 2 in terms of FPS when loading cold and dark at a gate at EGLL. In the announcement for v1.5 made, the FPS should have become even better than the 737. That is not the case on my system.
However, it is really good enough for me now to enjoy smooth flights, so I am a happy customer really appreciating the effort taken by Fenix to improve their product whilst there was no obligation whatsoever to do so!
Well, 5 - not sure that counts as a “ton”, and one of those is a note about SU13, and 2 are about further optimisation that can be done. Only the first and fourth could really be classed as bugs. So, yeah, 2.
See instructions in this post - last bullet
Did you enter wind data into the DESCENT WIND MCDU page? Managed Descent gets unreliable quickly once larger components of headwind or, worse, tailwind are in play. Even eyeballing a wind correction is enough to improve Managed calculation to avoid those pesky MORE DRAG messages.
I am excited how fast thy came up with this patch.
For me the “rendering with iGPU” was a massive improvement in VR.
I now have a far better experience in VR after the GPU Frametime went down again and I have a smooth performance.
With the new Displays I can finally use DLSS in VR and read all fonts.
Performance wise I am very happy now.
Cant wait to see Block2 and the new EFB. I have hopes they will finaly separate refueling and boarding and by fully GSX compatible out of the box. A small detail (that can even already achieved with the great external tool “feix2gsx”), but still.
I thought they were going to introduce incremental updates with V2. The last hotfix is still a full installation file.
Hi
Anyone works the Squak code input screen?
On pedestal at new uodate of fenix… still testing… but no squak code to put on
I can confirm, that the squawk code is not working or at least not the display.
By the way does anyone already got a new simbrief profile for the A320 ? The old one is with 162 pax and I need a new one with 180 pax.
You have to use CLR to delete existing digits before you can put new ones.
Performance seems to be way better, excited for what else is to come. Thankyou!
I did have an issue importing my flight plan into the FMS though. It imports in to the iPad and I can run the INIT through the AOC menu. In the actually FMS when I select to import the flight it’s saying ‘INVALID FLT-PLN’ or something similar.
A bug or a one off?
I had this issue in V1 when flight plan included oceanic waypoints. This plane uses different coordinate format to what Simbrief generates. Not sure if this was fixed in V2.
If you didn’t have oceanic waypoints in your flight plan maybe AIRAC does not match. 2308 was released yesterday.
on the fenix discord is a section for simbrief profile. THere you will find the link to the updated profile.
Ok! Another good change
It was a simple domestic flight. Both the Fenix and Navigraph are the latest versions.
Sounds like it could be a bug then.
Hi again
Testing last version 1.5.1.200 ,using tobii Eye tracker 5 , 4k dlss3 ,all good for now
What software is the voice we hear?
The squawk code entering works fine. Just press CLR twice and it will clear the current value and then you can enter your new squawk code. I understood that’s how it works IRL.
Self loading cargo new version