For what it’s worth, I’d certainly recommend updating.
Ton of problems?? There was only 1 big issue for some (including me), and that was extreme cpu-load. It was immediately adressed within a day with the .200 version.
I really don’t see any significant issue being mentioned multiple times. Not here, and not on their Discord.
3 Likes
It’s on the Fenix A320 app, On the left side there are two checkboxes you can check. I believe it is the top one - something like Use Alternate Renderer (and if you hover over it, it explains that for systems with iGPU, it will utilize the iGPU to render the displays thereby unloading some work from the main GPU)
3 Likes
Yes, that was a gamechanger for me too. I was a bit sceptical right after the update, it performed even worse than before but when they released the xx.200 build and I changed the rendering to the iGPU, it was like a different plane. Now it’s comparable to the PMDG performance on my machine, no more avoiding bigger airports with Fenix A320. A great update. And what’s best… is that more candies are coming out of Fenix factory in the very near future…
3 Likes
I’ve tried a number of fixes for .200, but I’m still getting blank screens and a major pause/stutter every two seconds–which is CPU related. So far, Fenix can’t figure it out–near top-end system.
How can I revert back to v1?
Thanks
Download previous version from website. Uninstall V2 in Windows Settings. Reinstall downloaded previous version. Recalibrate throttle and flaps in mcdu>config controls.
Recalibrating throttle and flaps takes a minute. It’s very quick and easy to do.
There is also a read me on this on their site and Discord.
1 Like
Just tested with iGPU and dedicated GPU on my PC, the weird thing is text quality in MCDU with iGPU is blurry and much worse than iGPU display from V1.
With iGPU (Altenative Display Renderer)
With dedicated GPU (unchecked both options)
1 Like
You’re right. Out of curiosity I tried it and I have the same results. It’s crisper on GPU. And to my surprise the performance was about the same according to the FPS counter (I wish there was a benchmark integrated into the MSFS). So I’ll try to keep it with the GPU from now on, thanks!
Aha that´s the difference!
I noticed that smaller text on the MCDU can get reeeeeeeally blurry in combination with AMD FSR.
With both iGPU und FSR active the text can get really thicc and very blurry (sometimes it is becomes difficult or impossible to distinguish letters like 0 with 9 or 8 or B) on a resolution 2560x1440.
But the framerate is almost 10 or 15fps more with iGPU on, and without AMD-FSR the visual difference is minimal so I keep my precious Vega11 rendering the displays 
FSR especially on performance or balanced settings is way worse than iGPU on.
iGPU adds a ton of performance with the cost of a hint more blurryness in the MCDU text.
This is how it should look like in real life, very thin (text seem to be almost two pixels thin) and crisp sharp
Pretty sure that’s EIS1 though in those Baltic video so be careful with direct comparisons.
Been having issues loading the fenix lately. I usually start cold and dark at a gate. I can see the red beacon flashing in the outside view before entering the plane and already know something is wrong. The EFB is unusable, the batteries can’t be switched on it is basically in an odd state. Signed in and out of the fenix app, as recommended, doesn’t help. Trying to load it again causes an orange colored hangar and the A320 has no gear. Even the sim menu doesn’t work anymore. Feels like the fenix doesn’t like something in the community folder but i have no clue what, there is nothing fenix related in there other than the original fenix files. The only thing that got updated a lot lately is the pms 750 but i need that.
I hope you did not - just like me - forget to enable the iGPU in the BIOS settings. I did see an increase of FPS using Alternative Renderer, although not as dramatic as others posted (around 3-5 fps, so 10% increase on my system).
If you want to make sure iGPU is working use MSI Afterburner. It will show you separate stats for iGPU and the main card.
With ALTERNATIVE RENDERER turned OFF iGPU usage is 0%. With ALTERNATIVE RENDERER turned ON the usage oscillates around 10%, in my case. Depends how many displays are in view.
Hm, on my mainboard the setting for graphics is IDG, PEG or automatic.
IDG integrated graphics, PEG pci express graphics, and automatic whatever is connected to the monitor activates the graphics device.
There is no real “on” or “off” for the Vega 11 but using PEG might switch it off.
And you are right Baltic Aviation using those LOVELY EIS1 cockpits from the Knight Rider and MacGyver era 
Here is an EIS2 example for the MCDU letters, that´s like the GameBoy Color version:
And the screen has some awesome distortions like the Fallout PipBoy, it seems to be a cathode screen in these devices (and not a dot-matrix like I thought) so I am going to ask the Fenix team if they can implement these cool cathode screen distortions to the MCDU.
But again I have noticed a difference… the MCDU in this video seems to be way more colourful than the Fenix video.
Not sure about every page but I remember for example the wind speeds, or transition altiutude all having white lettering and not blue.
Also the waypoints are all in white and not in green…
So the Fenix is probably an EIS1 MCDU?
For those noticing that go to Fenix’s discord and search for “blurry displays”. There is a thread about it where Aamir points where and what to change, in the first messages. It’s solved by editing a line in a small file with notepad. After that both options will look the same in sharpnesses.
maybe I’m very stupid, but I can’t find the thread you mention on Fenix’s discord. can you give us a link please?
Hello mate,
Can be this…?
1 Like
Could be this thread?
screen delay issue after update
Aamir — 11.08.2023 04.05
step 1
c:\ProgramData\Fenix\FenixSim A320\fenixConfig.xml
find this
step 2
open it in notepad++
step 3
set display scale to 1 for max quality
close, save, profit.
Then
“set the xml to read-only in order to prevent it from setting the scaling to 0.6667 after a restart”
2 Likes
But the realism suffers.
A320 displays have a resolution of 768x768 and the display size is 158mmx158mm, making it around 123.4 PPI.
If the resolution is changed in the config it is no longer an authentic A320 CEO EIS2 display 
Better don´t use AMD FSR or Nvidia DLSS.
1 Like