I have only experienced a freeze once after a flight with GSX Pax into EDDF.  I think it was just too much VRAM.  It was post-runway exit so I didn't care.  The Fenix has been at the top of the bar for me in terms of overall visuals and experience, sans flare/float on landing.  The floating I get interferes with me too often that it has reduced my usage.  I hope this is improved for the next update.  Other than that, I have no bugs or issues with it.

Hi ,

I made some shorts flight test, here there are my preliminary conclusions: 
using DX11 instead of DX12 with latest nvidia driver 560.70 seems to solve the issue 
Rolling back nvidia driver (I choose 552.12 of last aprile) also seems to solve the issue also with DX12

so the freeze has nothing to do with popping out the panels nor with GSX , it mostly seems a nvidia driver fault . With latest nvidia don’t know why we can’t use Fenix with DX12 anymore 

3 hours ago, maddoc said:

Hi ,

I made some shorts flight test, here there are my preliminary conclusions: 
using DX11 instead of DX12 with latest nvidia driver 560.70 seems to solve the issue 
Rolling back nvidia driver (I choose 552.12 of last aprile) also seems to solve the issue also with DX12

so the freeze has nothing to do with popping out the panels nor with GSX , it mostly seems a nvidia driver fault . With latest nvidia don’t know why we can’t use Fenix with DX12 anymore 

I do not concur with your preliminary conclusions.

My Fenix A320 V2 works absolutely fine with the 560.70 nVidia driver and DX12 - no problems whatsover, and I have made numerous flights with the Fenix A320 over the last week.

If, I open MSFS popup panel manager (latest version from flightsim.to) and select the configuration that I have previously used for the Fenix A320 V1, the flight sim freezes, and I have to close down MSFS using the task manager.

As previously mentioned, the MSFS popup panel manager still works absolutely fine with my PMDG 737 and 777.

So to me, the problem does not lie with either the nVidia driver (560.70) or DX12.

I am still convinced that the popup panel manager is the cause of the freezes that I have, and am still experiencing, when using MSFS Popup panel manager with the Fenix A320.

Edited August 5, 20241 yr by SquadronLeader

16 hours ago, SquadronLeader said:

I do not concur with your preliminary conclusions.

My Fenix A320 V2 works absolutely fine with the 560.70 nVidia driver and DX12 - no problems whatsover, and I have made numerous flights with the Fenix A320 over the last week.

If, I open MSFS popup panel manager (latest version from flightsim.to) and select the configuration that I have previously used for the Fenix A320 V1, the flight sim freezes, and I have to close down MSFS using the task manager.

As previously mentioned, the MSFS popup panel manager still works absolutely fine with my PMDG 737 and 777.

So to me, the problem does not lie with either the nVidia driver (560.70) or DX12.

I am still convinced that the popup panel manager is the cause of the freezes that I have, and am still experiencing, when using MSFS Popup panel manager with the Fenix A320.

Did you try a to make a new fresh clean configuration for Fenix in panel Pop out manager?

so why rolling back nvidia driver I can use last release of panel Pop out manager without any freeze while with nvidia driver 560.70 I can use it only with DX11 ?

Edited August 6, 20241 yr by maddoc

On 8/6/2024 at 7:29 AM, maddoc said:

Did you try a to make a new fresh clean configuration for Fenix in panel Pop out manager?

so why rolling back nvidia driver I can use last release of panel Pop out manager without any freeze while with nvidia driver 560.70 I can use it only with DX11 ?

I stand corrected.

I decided to roll back to nvidia driver 560.70 as you suggested, and the Fenix A320 V2 works fine with the popup panel manager with that driver. I am however using DX12 and have no problem with that.

Thanks for the tip, and hopefully nvidia will address this in future driver releases.

I have this same freezing problem with both the Fenix A320 and the TFDI MD-11.

I thought the problem was fixed but still same problems

Edited September 16, 20241 yr by rob0203

I think I have a FIX!!!

In the Fenix menu outside the sim:

Enable: Use alternative display renderer

Disable: Display VSYNC

Running now with latest drivers!

Edited September 23, 20241 yr by rob0203

Maybe only disabling VSYNC in the Fenix is enough did not test that

Hello, since the .359 update i put the captain tablet in sleep mode and now i can turn on again, has this happened to anyone else?