23 minutes ago, captainbluesky said:

ok EGLL at stand 512, default scenery as do not own inibuilds, no traffic.

Windowed

Built in windows FPS 23, Dev mode FPS 12

Full screen

Built in windows FPS 47, Dev mode FPS 23

You have a problem with gpu vram, need to lower texture resolution, most likely. Also your render scale is through the roof, check that also...

Your settings are messed up somewhere, probably you have the render scale slider mistakenly set to 200? Check your screenshots, you use 1440p as monitor resolution, but your sim gets rendered in a whopping 3942x2218 resolution. Way more a 4070 can take. And furthermore, your post is even higher, 5120x2880. Both resolutions are HIGHER than 4K...

So back to field 1: post your settings of MSFS and inside nVIDIA Control Panel showing the page for Microsoft Flight Simulator please. Something is seriously off here.

You mentioned using "Preset E" within Nvidia Inspector.  I have noticed that once you set these presets, even if you disable them it still seems to keep MSFS at the high render scale.  You may want to go into MSFS General Settings and check the Render Scale slider.  Putting it at 100 may still be giving you a higher-than-expected resolution...THAT is probably why you're seeing such a low frame rate.  This is evidenced by your screenshots which show a very high render scale.

I haven't figured out why MSFS is doing this.  It could be a config file that needs manual adjustment.  I too have experimented with DLSS and the Presets...and ever since then I've had to really watch that render scale slider if I decide to go to TAA again.

1 hour ago, captainbluesky said:

ok EGLL at stand 512, default scenery as do not own inibuilds, no traffic.

Windowed

Built in windows FPS 23, Dev mode FPS 12

Full screen

Built in windows FPS 47, Dev mode FPS 23

You should definitely be seeing significantly better frame rates with your specs. Something is off and assuming it’s not a hardware issue then it can only be that your graphics settings have gone a bit crazy.

34 minutes ago, AnkH said:

Your settings are messed up somewhere, probably you have the render scale slider mistakenly set to 200? Check your screenshots, you use 1440p as monitor resolution, but your sim gets rendered in a whopping 3942x2218 resolution. Way more a 4070 can take. And furthermore, your post is even higher, 5120x2880. Both resolutions are HIGHER than 4K...

So back to field 1: post your settings of MSFS and inside nVIDIA Control Panel showing the page for Microsoft Flight Simulator please. Something is seriously off here.

Yes exactly.   I bet if he goes into MSFS Settings, General Settings, Render Scale slider, it will be way way higher than 4K

1 hour ago, AnkH said:

Your settings are messed up somewhere, probably you have the render scale slider mistakenly set to 200? Check your screenshots, you use 1440p as monitor resolution, but your sim gets rendered in a whopping 3942x2218 resolution. Way more a 4070 can take. And furthermore, your post is even higher, 5120x2880. Both resolutions are HIGHER than 4K...

So back to field 1: post your settings of MSFS and inside nVIDIA Control Panel showing the page for Microsoft Flight Simulator please. Something is seriously off here.

 

ok please see the images below. I could not see render scale setting when in DLSS so switched it to TAA so we can see it - see 5th image below it is set to 50.

 

 

 

 

 

 

 

 

 

 

 

Ok, some comments from me (disclaimer:  I am far, far from an expert on these matters...).  I note the difference between your native resolution (possibly 2560 x 1440) vs. your actual (2560 x 1377) which is due to the NI settings or DSR Factors.    Your Windowed vs. Full Screen problem may be related to this difference.   I don't see DSR Factors in your NVCP screenshots and so I'm assuming it's set in your NI settings. 

You're losing a few frames with Glass Cockpit Refresh Rate on Ultra.

Your fixed TLOD of 200 is hurting you too.   I don't know how well that scenery is optimized, but I'm not sure you need that much TLOD on final approach in big iron.  There is an app called AutoFPS that you might want to look into, although as I said, I would take a look at the resolution you're making the card push out.

Perhaps @Cpt_Piett might have some better insight into the DLSS / NI implications...

“DLSS Super Resolution” and “Ultra quality” plus the c5K resolution your earlier screenshots suggest you’re rendering at … somehow MSFS has got the idea that you want to render at c5K resolution which will bring anyone’s PC to its knees. 

My diagnosis: looks like you’ve been drinking too deeply at the well of DLSS voodoo stuff 😉

Maybe undo all the DLSS tinkering stuff, including “presets” and all that nonsense, reset it all back to Nvidia and MSFS defaults for your system and take it from there. 

It’s OK to keep v3.7 of the DLSS drivers - but they improve performance on their own, WITHOUT needing all the extra fiddling around which just promises more than it delivers. 

 

 

On 5/5/2024 at 11:11 PM, captainbluesky said:

Please explain - why is the CPU utilisation % so low and is there any method of increasing this utilisation % on the powerful AMD 7800 X3D processor?

MSFS is still not very optimized for multithreading, and only utilizes a portion of modern CPUs. Even though it does use several cores / threads, a lot of the calculations are done within a single “main thread”. 

I have a 12900KF with a total of 24 threads, with 8 cores overclocked to 5.1GHz. I’m CPU (mainthread) limited most of the time, even though the total CPU load rarely goes above 40%. Hence, lots of untapped resources there that MSFS don’t have access to.

I recently arrived into FlyTampa’s Amsterdam in the Fenix with lots of AI traffic. This was the average CPU usage for the approach:

11 hours ago, Mace said:

Your fixed TLOD of 200 is hurting you too.   I don't know how well that scenery is optimized, but I'm not sure you need that much TLOD on final approach in big iron.

Good Lord yes!  I use DynLOD and by the time I'm 1500 AGL I'm already well below 100.  It just doesn't matter visually at that AGL.

7800X3D here too.  My typical open native frame rate in PMDG and FBW ranges from 45 to 75 taxiing at any airport worldwide no matter how demanding.  I lock it at 44, and I don't use DLSS Frame Generation.  Cores 0 and 1 run between 56% and 80% utilization with an average of around 68%.  The other 6 cores dance between 20 and 55% utilization.  

Of note, I had 9900K and 3080Ti previously and never would see that low a native rate anywhere and that is on a 3440x1440 display, TAA/16x/8xSS, AMD FidFX 100.  Typical then was around 33fps maintainable anywhere in any of my 4 planes with those settings, and again that's now 44fps w/ the 7800X3D, which by the way is about 27% fasting single-thread wise than 9900K, so that fits.

If I were you I would delete the user.opt file, Un- and reinstall your graphics driver and start from there.

 

15 hours ago, orchestra_nl said:

That is not entirely correct. While it is true that MSFS does not use all cores equally, it is multithreaded and more optimised for multiple cores than its predecessors. With the 8-16 cores we have today most are being used too little but it is not easy to divide all the work among all cores.

The fact remains, MSFS is unable to take a modern CPU and utilise it anywhere near 100% like we might see with the GPU. In fact, it can’t even get near 50% of the theoretical compute power on offer from a high end CPU like an i7-14700K. Asobo has said doing so with MSFS2020 would result in instability issues. However, assuming CPU manufacturers continue down a multi-core developmental path, the multi-threaded capabilities for game applications in general will no doubt improve over time. It’s a factor of both hardware and software.

A TLOD of 200 is not the problem. Reducing it will help the CPU of course but something has gone skew with DSR up-scaling. Need to reset this, remove all up scaling. Settings as posted seem ok. What is the Ultra Quality DLSS setting rendering at?

22 hours ago, captainbluesky said:

I am not sure if the built in windows FPS counter I use can capture frame generated FPS.

I have included 2 x screenshots below to show windowed mode FPS and full screen FPS, using both the built in windows FPS counter (i.e. press Windows key and G then select Performance button) and the dev mode FPS counter within MSFS. Not sure what is going on here.

I tried the Nvidia overlay as another FPS comparison but the FPS using the overlay display just displays N/A all the time.

Maybe a freeware FPS counter such as Fraps or similar may shed more light on the 'real'/actual FPS I am getting?

Windowed

Full screen

 

 

 

 

 

 

You are out of VRAM, that is your main problem.