V4.5 : what has happened to Locked framerate ?

[GSalden 4,656]

It doesn’t matter if all sliders are set to the left and Locked framerate at 10 , core 0 ( main thread ) has  100% load.

Using Unlimited shows a 92%  load with very high settings and 95+  fos, while with Vsync on ( 25 hertz / 2 4K displays in NVSurround with Distortion correction ) load drops to 67%.

As Uimited + Vsync still show some jumping up fps ( 50/100/ back to 25 ) , in V4.4 I also used Locked at 30 to avoid that.

When doing that with V4.5 because of the Locked framerate too there is this 100% load .

Therefore I started to test with my 2 pc’s and found out that with Locked framerate , regardless of the settings , the main core shows a load of 100% which causes micro stutters ..

[Bert Pieke 7,584]

This was the case with V4.4. as well as best I recall.

[GSalden 4,656]

With V4.4 I used Uimited + Vsync + Locked at 26. Load 67-95% depending on the scenery .

I use HardwareMonitor for this.

A look ahead buffer should not cause this...

Imho this is a bug but before posting this at the LM forum I wanted to know first how you guys experience this ..

[mpo910 2,112]

14 minutes ago, GSalden said:

With V4.4 I used Uimited + Vsync + Locked at 26. Load 67-95% depending on the scenery .

I use HardwareMonitor for this.

A look ahead buffer should not cause this...

Imho this is a bug but before posting this at the LM forum I wanted to know first how you guys experience this ..

Hi Gerard. I can confirm this. I´m using the latest P3D Build (4.5 incl. HF), Unlimited, VSync and in NCP set 30hz on my 4K monitor. Locked Framerate at 23, 25, 29, 30 or whatever I set, doesn´t reduce the load on my 8700k OC to 5.1 GhZ. Also switching to VR doesn´t change anything (I did not expect this behavior but thought it might be interesting that VR/no VR doens´t influence anything). 

 

BR Marcus

Edited May 16, 2019 by mpo910

[JoeFackel 760]

Do you use an AM setting (i think i recall you do)?

Remove it, just for a test. Since 4.4 i see an kind of smoother experience without pushing P3D to cores.

[glider1 90]

There isn't anything wrong with fully loading the first core from what I understand. Core 0 is mainly just offloading jobs to the other cores and you want it to be fully busy doing that. Microstutters are possibly not because core zero is fully utilized, but that something in the system is interrupting core zero from doing its job  (so therefore use affinity mask). Locking frames shouldn't reduce core zero's purpose of offloading jobs to the other cores. If core zero is not fully loaded, that is actually a bad sign because it means that the CPU is generally under utilised because core 0 can't find jobs to allocate (when it always should). 100% load in task manager doesn't even mean that the core is fully utilized. Only the core temperature tells you what the actual load of the core really is. The only way to overload core zero is if you are using too many cores for it to allocate jobs or there is another setting that is too over zealous like LOD where core zero can't keep up with the job scheduling load any more because there is too much scenery being pushed out from the CPU to the GPU.

I could be wrong but this is my understanding after a long time of reading SteveW.

Best wishes with this. It is complicated and I could be wrong.

[GSalden 4,656]

You are correct ; I use an AM. But also without AM this Locked franerate bug is there...

BTW : as I use a 14 core 7940X I oy use the 8 fastest cores for Fs and the others for multiple addons. 

[GSalden 4,656]

With the main core continuesly at 100% , also in easy scenery , you will experience stutters when flying over detailed scenery and a large AG has to be loaded ( eg : True Earth series )

[AnkH 2,261]

I am on 4.5, hotfix not yet installed and I never monitor the CPU load. All I can say: I use an AM entry that restricts P3D to the "real" cores only (I have HT active) and .bat files that move all addons off core0 and I do not see microstutters or something like that with a frame limit of 30. As soon as I remove the AM or put "unlimited", I have a stutterfest.

[itsjase 52]

There was information about this in another thread a while back.

Something about calculating look ahead frames and keeping it loaded to prevent any throttling which could induce stutters

[westman 257]

Did a test with my 9900k , have a saved testflight in P3D V4.5 HF1 . tested only cpu usage same gpu 2080TI same settings in P3D at 4.8ghz 100% at 5.5ghz approx 90% 

9900k is working best for now, have x299 and 2x cpus 7920X 12cores and 7980XE 18cores both do 5.0ghz HToff

Edited May 16, 2019 by westman

[JoeFackel 760]

3 minutes ago, westman said:

Did a test with my 9900k , have a saved testflight in P3D V4.5 HF1 . tested only cpu usage same gpu 2080TI same settings in P3D at 4.8ghz 100% at 5.5ghz approx 90% 

5.5? Congrats, can't get mine beyond 5.1 ATM

[westman 257]

7 minutes ago, JoeFackel said:

5.5? Congrats, can't get mine beyond 5.1 ATM

its a binned chip, not from siliconlottery , on AIO cooling 360rad HToff

Edited May 16, 2019 by westman

[gboz 157]

2 hours ago, glider1 said:

There isn't anything wrong with fully loading the first core from what I understand.

Have my doubts about that. Don't no about V4.5 or V4.4 but with V4.3  there are a few combinations of refresh rate, VSync and frame rate that peg the CPU at 100% all the time, even with the sim paused. CPU temp is higher and performance (smoothness) is worse than other combinations giving a lower CPU usage and a logical drop in CPU usage when paused. Of course any combination can go to 100% given the right situation but if you are the only plane in a blue sky featureless desert and the sim is still running 100% paused you have to wonder what's going on.

gb.

Edited May 16, 2019 by gboz

[GSalden 4,656]

Steve W is going to test this and will let me know. I will post the conclusion then in this thread...