I am using iGPU for rendering the Fenix displays and you can see the improvement in the picture.
If you are using GPU for rendering the displays (i.e. the option “Use Alternative Display Renderer” is UNchecked in the Fenix app), editing the file fenixConfig.xml doesn’t help. In that case the parameter “displayScale” is most likely already 1.
I am not using DLSS or FSR.
Hello guys, it is my first flight in the new version of the fenix and unfortunately i am having some issues in VR. Once i enter VR (i am using a Pimax Crystal) the autopilot wont react to my input as well as the MCDU (or FMC). Is this a known issue? i am not sure if it has to do with the Pimax? or with Fenix? is there a workaround?
I see absolutely no increase in performance with v2, arguably even a little (very little) worse performance. Tried both with “alternative” checked and not.
In v1 I would set the option to use my GPU. I’m not sure what that same config is in v2 but I tried all the options. Checking “alternative” is a couple FPS better than not, and I find on my 7950x3d actually if I do NOT check it, then there is more CPU load which spills over into the parked CCD.
But tl;dr for me is with v1 in my test scenario I am pretty much locked at 60fps staying green the whole time, where as with v2 at best I’m 60fps wit an occasional drop into red with 57-60fps
Definitely not seeing this massive increase reported by the devs.
Yes, my performance is also worse, though there is a patch coming soon which should help some users who are seeing worse performance.
Don’t use VR controllers. Everything works when using a mouse.
I am not using the controllers, only the mouse. I guess you have no issue at all right?
It also works with VR controllers, I fly it all the time, though with controllers you have to setup some custom bindings (not Fenix specific) or you’ll pull your hair out until you give up.
Perhaps you can be more specific, what do you mean AP won’t react. Maybe start with MCDU since that’s easier to test I guess, do you get the interaction cursor over any buttons? Are you on legacy or interactive input method?
Yes, I use mouse in VR and everything works. I saw many people complaining that Fenix (at least V1) does not work very well with VR controllers but as I see it’s not the case.
For example, once I am in VR and I want to change the altitude, the numbers will not change. If I want to set up my flight plan in the MCDU, It won’t react to any input. If I want to change my screen in the primary display to VOR if won’t do anything. The knob itself will move but the screen does not change.
If I step out from VR, all starts working fine…
I am on modern mode. The issue is only with the fenix all other aircraft are working fine.
What headset are you using? It might be a pimax issue but I am lacking more investigation..
May I ask what headset are you using?
I use the G2.
Perhaps try that “Use display synchronization” option in the launcher. It’s possible that in VR your PC is so overloaded/focused on MSFS that the fenix*.exes in the background don’t have time to breath.
Thanks! I haven’t tried this, we will see 
Reverb G2 as well.
I have the same CPU and also experienced worse performance. Try setting the Fenix App to “Remember this is a game” in XBox Game bar, if you have not already done so. This helped and brought about the same performance as V1 on my system.
my only gripe with the latest version is that when starting your flight i get fantastic FPS, better than before, but after i land at any airport my FPS just tanks down to low 20’s from 50 in the beginning…not sure what could be causing this…
That applies to all airplanes I fly, not only Fenix. I always have a much better perfomance on the departure airport.
New update for Fenix today from @Amir
Hey @everyone, a new update is now available via the Fenix App - in this one, from an FM perspective, we’ve further refined the flare phase, taken a smidge of float out during landing, rectified the flap 3 drag situation, and sorted out the nose smashing down on landing instantly. Avionics wise, a few fixes here and there, mostly targeted at polishing VNAV, and fixing certain restrictions being improperly parsed by the aircraft. We’ve also fixed high CPU usage across both Fenix bootstrapper, and the Fenix app itself - thanks to the reports sent in by affected customers, along with nabbing several crash fixes for better stability, and picking off some irritating bugs in the panel state selection process. The art team has thrown in several fixes of their own based on customer feedback, which you can view in the changelog below, and some further sound improvements.
Oh, also, Saturn V mode was disabled during rotation. Sorry bout that. Enjoy 
A320 CFM V1.5.2.214
[SYSTEM]
Adjusted G/A trigger
Fixed high altitude speed constraint reported with LIRF approach
Several crash fixes
Fixed panel state issues with unable to start engines without cycling master levers
Fixed DES engagement from cruise equal to ALT CST, dist to dest must be < 200nm (reported on one of the KPHX arrivals from FL340)
Fixed G/A on wrong flaps conf target
Fixed MANUAL leg’s termination is not used as map ref point in plan mode
Fixed speed/altitude constraints missing criteria
Corrected restricting speed constraints below ECON on DES
Corrected not restricting speed constraints above ECON on DES
Improved ALT* in DES
Made LVLCH in DES mode more aggressive
Reprioritised below profile and overspeed relationship
Fixed occasional inccorect TOD placement over LNAV path
Fixed routing after discontinuity+manual leg when inserting SID/STAR/VIAs
High altitude speed constraints should appear in mach and be satisfied/ignored as such
Unrestrictive speed constraints are ignored, the actual speed displayed on that waypoint including (SPD LIM)
Added +/- is not allowed with speed constraint entry in MCDU → FORMAT ERROR
Allow empty CSTR value
Fixed reversed L/DEV
[FBW & AUTOFLIGHT]
Retuned alpha protection to prevent oscillations
Fixed blending bug in FLARE to GROUND MODE preventing correct blend being applied
Adjusted FLARE MODE to GROUND MODE transition logic
Adjusted FLARE MODE nose down controller with corrected data type
Adjusted FLARE MODE sidestick input Nz feedback
Adjusted spoiler deployment profile
Adjusted elevator input Nz data processing during post-touchdown to fix nose-down smashing
[FLIGHT MODEL]
Adjusted Flap 3 drag values
Adjusted rotation weight/feel for greater weight
[ART & SOUND]
Fixed overly bright cockpit in some scenarios
Added SPEED BRAKE text on pedestal
Fixed wind sound disappearing in cruise (who knew TAS could go above 500)
Cockpit wind noise in high mach cruise improved
Fixed N2 whine and buzzsaw LP bug (engines should sound better in cockpit & cabin now)
Improved initial spool (20-50N1) sounds and balancing
Fixed stereo width on AEVC and cockpit pack samples
Taxiing sounds improved
Nosewheel on runway lights sound improved
Contactors improved (more to come in B2)
Y elec pump volume adjusted
Fuel pumps volume and balance adjusted
//
How are people finding FPS with the Fenix after all these updates?
For me, still about 10fps lower than the PMDG, which is pretty much the same as it was in V1.
