Huge fps increase with mt

[Pikachu]

That's the reason I wanted mt support for years!

 

DxDiag.txt

Edited March 11, 2023 by Pikachu

[jackdaw]

CPU 4790k intel in the quick mission F18 on ramp, getting 65fps with dcs.exe, dcsmt getting 100fps looking at the same spot while stationery on the ground.

[Shibbyland]

Can somebody help me understand what the information in the FPS box (top left) means. I think I'm possibly limited by my GPU.

The performance improvement for me hasn't been quite so dramatic, still periods of large FPS drops over trees for example but I think it's improved at altitude. Hard to say until I start running some missions.

In any case the information presented to me will be something along the lines of "FPS: 71 T: 52.361 GPU BOUND (theor. FPS 150)". I understand FPS but it's the GPU BOUND and theoretical FPS I don't understand.

[Sprool]

GPU bound means the GPU is limiting the frame rate, not the CPU, and I'm guessing theoretical frame rate would be the max fps if your gpu wassnt holding back the system

[Pikachu]

21 minutes ago, Sprool said:

GPU bound means the GPU is limiting the frame rate, not the CPU, and I'm guessing theoretical frame rate would be the max fps if your gpu wassnt holding back the system

1st I use vsync, hence the checkmark in the box labeled VSYNC* and 60 fps on LG W3000H working at 60Hz refresh rate. So ACTUALLY the monitor is now holding back the system.

2nd From sub 30 fps on an i7 990X CPU from 2011 to 60 fps is pretty nice to me for zero [insert any currency whatsoever].

[Top Jockey]

9 hours ago, jackdaw said:

CPU 4790k intel in the quick mission F18 on ramp, getting 65fps with dcs.exe, dcsmt getting 100fps looking at the same spot while stationery on the ground.

 

Hello,

Glad to know it, i have the same CPU.

 

Did you took any additional steps, as deleting FXO and metashaders folders, or anything ?

How did you measured performance ?

Thank you.

[jackdaw]

in the post, just used the quick mission, ready on ramp, then whilst stationary looked at the same position with and without MT

each time i update clear FXO and meashaders folder, update then to a clean up and repair