Hi flyers

I have an AMD 7800 X3D processor, Gigabyte 4070 Super 12gb graphics card and GSkill 32gb 6000Hz Ram.

The images below show me in the Fenix A320 approaching FSDreamTeam Euroairport Basel Mulhouse with ultra settings at 2560 x 1440 using DLSS ultra quality, DLSS 3.7.0, Preset E in Nvidia inspector, RAR enabled etc. Achieving 23 frames per second.

I do not understand why the CPU is only showing 17% utilisation. My GPU, VRAM and RAM utilisation %s are high.

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?

I’m pretty sure one thing the Fenix allows you to do is hand back Glass Screen generation from GPU to CPU.

-B

Edited May 5, 20242 yr by btacon

Because your GPU is doing all the work in that scene, it's almost fully utilized and there's nothing for your CPU to do. You can turn down GPU heavy effects, to push more work over to your CPU.

I would be looking at individual core utilisation, not overall CPU usage. IIRC, the aerodynamic modelling and aircraft systems are primarily done on one core, while the rest of the cores are used to load in scenery.

s0cks is right.  If you look at individual core usage, one or two of them will be much higher than 17%.  That 17% you're seeing is the average of all of the cores.  So if a couple of cores are low it skews the overall % down.

I'm assuming that 23 fps you're showing is the base rate before Frame Gen, so you're getting a much more usable 46 fps on approach.  At least I hope 23fps is the pre-frame-gen fps!  Anyway I do not have that scenery to test that exact scenario.  I wonder what your TLOD is during that approach?

CPU Utilization is for productivity not gaming. They will figure it out one day but most will experience crashes. Seb said this almost 4 years ago they attempd to off load main cores from the the sim and it crashed every time.

 

Edited May 6, 20242 yr by JBDB-MD80

As stated above. 17% is an average across all cores. MSFS is not a multi-threaded application and cannot make effective use of all cores. So while most cores are sitting idle, it is working one core to the max. Something we are all hoping gets addressed in MSFS2024. 

1 minute ago, RaptyrOne said:

As stated above. 17% is an average across all cores. MSFS is not a multi-threaded application and cannot make effective use of all cores. So while most cores are sitting idle, it is working one core to the max. Something we are all hoping gets addressed in MSFS2024. 

Correct.👍🏻 

This FPS number is very low, no matter what those percentages say. Can we have a look on the settings? I for sure do not have only 23 FPS in such a scenario. I furthermore hope those 23 FPS are BEFORE frame generation...

2 hours ago, AnkH said:

This FPS number is very low, no matter what those percentages say. Can we have a look on the settings? I for sure do not have only 23 FPS in such a scenario. I furthermore hope those 23 FPS are BEFORE frame generation...

Thank you all for your replies so far. I am learning a lot from these forums on frames per second and 'pixel chasing'.

Ank - I think I just identified the problem after your comment, checking my settings and then trying full screen vs windowed mode. If I enable full screen I get c. 23 fps. However if I put the sim into windowed mode I get c. 45 fps which is much better with my hardware set up. Frame generation is on in both scenarios. My monitor is Gsync 144Hz.

I am not sure either what I have not done or what I need to do in the sim or Nvidia inspector (and/or Nvidia control panel) to get 45 fps in this scenario in full screen? Suggestions welcome.

In terms of my settings should I upload screenshots of both my sim graphics settings and Nvidia inspector settings?

Ok, then it might even be a readout issue: is your program that displays the FPS capable of capturing the frame generated FPS? What does the MSFS internal FPS counter tell you? 45 FPS seems still rather low though...

56 minutes ago, AnkH said:

Ok, then it might even be a readout issue: is your program that displays the FPS capable of capturing the frame generated FPS? What does the MSFS internal FPS counter tell you? 45 FPS seems still rather low though...

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

 

 

 

 

 

 

6 minutes 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

 

 

 

 

 

 

1. Both those counters show frame rate before frame generation. 

2. I would not expect windowed/full-screen to make the big difference you’re seeing.

3. In absolute numbers, your frame rate looks low, looking at your specs compared with what’s on your screen (you don’t seem to be showing any of the major performance killers like a major hub airport, nearby big city, lots of air and other traffic).

4. Just to establish a baseline, maybe try starting a flight at EGLL stand 512, no traffic, and report back what performance you’re seeing while you’re still at the gate? Even better if you have the inibuilds EGLL.

7 hours ago, RaptyrOne said:

As stated above. 17% is an average across all cores. MSFS is not a multi-threaded application and cannot make effective use of all cores. So while most cores are sitting idle, it is working one core to the max. Something we are all hoping gets addressed in MSFS2024.

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. It is like an orchestra; you can't just add another instrument without changing the music score and while violins can share the work amongst them, the soprano part can only be sung by a single person. Adding a 2nd soprano would not get you the same result and they might fight each other instead of work together.
At the same time, you can have only one conductor (the Main Thread) who needs to be able to instruct all the players and hear the result. You cannot just keep expanding the orchestra with more players/singers/instruments because if his workload becomes too high the concert gets limited by the Main Thread.

28 minutes ago, tfm said:

1. Both those counters show frame rate before frame generation. 

2. I would not expect windowed/full-screen to make the big difference you’re seeing.

3. In absolute numbers, your frame rate looks low, looking at your specs compared with what’s on your screen (you don’t seem to be showing any of the major performance killers like a major hub airport, nearby big city, lots of air and other traffic).

4. Just to establish a baseline, maybe try starting a flight at EGLL stand 512, no traffic, and report back what performance you’re seeing while you’re still at the gate? Even better if you have the inibuilds EGLL.

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