I have a strange issue where it takes a bit for my frame rate to reach its peak. For the first few minutes it will fluctuate rapidly between 10-25 or so. I can see my GPU core usage also fluctuate up and down significantly during this time…usually between 15% - 80%.

Sometimes re-entering VR solves the problem, but not always. Sometimes exiting to the main menu and starting a new flight fixes the problem, but not always. I find the more consistent solution is to just…wait. Eventually my GPU core usage steadies at 90-100% and in turn, my framerate shoots up to a consistent 30+

This is with a G2 headset, 3080, 3700x. Running 80% FSR, 125% OpenXR, 100% In game.  I have Max performance and 60 fps lock set in NVCP.

Me too.  Sometimes I'm at 8 fps for two minutes, then suddenly up to 37-39 fps and on with the show.  Wonder what's going on for the two minutes? although I suspect it has something to do with using Ingamepanels for Little NavMap in VR.

 

In my case the problem it is motion reprojection, you switch it off and steady frames then. A pity, there is some problem with it.

And I am having W11 freezes since some weeks, and I have to switch off all the PC and restart, and now constantly after some minutes after departure, other time after one hour etc., I do not know what more to test and try. Sometimes starting the Xbox Bluetooth gamepad after the FS2020 did apparently solve the problem sometimes some days ago.

 

The WHEA error it is the most common but most of time only W11 freeze and do no post any BSD, the error that can´t read memory showed up today too.

Edited April 28, 20224 yr by peloto

19 hours ago, peloto said:

And I am having W11 freezes since some weeks, and I have to switch off all the PC with brute force maintaining pushed the power button, and restart.

When running MSFS only.

 

Yesterday I could end a flight with the Headwind A330-900 SU8 version afters some days without successful, the sequence of starting was,

-Start MFSF

-After it searches for updates switch on Bluetooth and Xbox gamepad, I am in a PC.

-After you are with the flight loaded in VC switch on WMR and then VR in MSFS.

 

Edit: I had one BSD now without MSFS, I think it is something too of W11 managing memory as I read it has problem of lekeage and corruption and go you to know what more. W10 and MSFS had its problems too....

 

Plus ASUS ROG BIOS?, I am with no OC, and with OC the same.

Edited April 29, 20224 yr by peloto

I noticed this since the first time VR was launched for MSFS. It never went away so far.

It is kind of annoying having to wait and having sometimes to restart the VR application multiple times before the frames finally are acceptable.

19 minutes ago, Farlis said:

I noticed this since the first time VR was launched for MSFS. It never went away so far.

It is kind of annoying having to wait and having sometimes to restart the VR application multiple times before the frames finally are acceptable.

Plus ASUS ROG BIOS?, I am with no OC, and with OC the same. This is disappointing, frustrating, dispiritedness and dismooding.

On 4/29/2022 at 11:39 AM, peloto said:

Plus ASUS ROG BIOS?, I am with no OC, and with OC the same. This is disappointing, frustrating, dispiritedness and dismooding.

Problem solved, if you have got two monitors, one with the iGPU and the other with the GPU, disable in BIOS in Graphic settings the RC6 (Render standby), probably the iGPU after some time bored only with VR freeze all the PC and then it shutdown it suddenly after some seconds.

I discover first that disabling the iGPU I could make a flight without any worries and sequences etc., and then tried with that option and not disabling the iGPU and only have to fly with one monitor.

This low FPS for a couple of minutes seems to be a new "feature" of MSFS SU9 and is something to do with MSFS accessing the logbook repetitively during this low FPS period. Until this is fixed (Asobo is aware of it and is investigating), all you simply have to do is wait until FPS is restored. No need to switch in and out of VR and this makes no difference to how long it takes FPS to recover.