How to lower the .1% Frametime?

[The_Nephilim]

Hey Guys,

I recently seen in fpsVR I can see my 1% and .1% FRametimes. I had noticed the .1% was rather high and I am trying to reduce it under 16.6ms. I am currently around 17.6ms so I am close, I was just wondering if this is even possible to do?

Having lowered it from about 26.5ms I am close now but it still has eluded me.. I am wondering since DCS Seems to always have that random spike if it would even be possible in DCS to lower the .1% FT down under 16.6ms?

 

I was wondering what setting would affect that FT the most if anybody knows? I have lowered the main FT too 6.7ms but the .1% seems problematic.. I was going to try and reduce the resolution in the VR Headset and see what happens I was just looking for some suggestions on what else I could try here?  thank you.

Edited 17 hours ago by The_Nephilim

[Hiob]

disable the power service (and every other background process you can live without).

The .1 lows are mostly caused by interrupt calls from other processes.

The power service is one of the big offenders and easy to live without with.

I suppose you have disabled the AV already.

[sleighzy]

Attach your DCS log file in case it highlights any issues. I'd also recommend using https://github.com/fredemmott/XRFrameTools vs. fpsVR to test this out. You can export the results to a CSV file and then for the frame timings it will show other things happening at the same time which may identify the cause of the increase in those.

[The_Nephilim]

yes I had AV disabled when running but not when testing will do that as well. and here is my DCS Log and I will try to run that program you suggested sleighzy..

I had exported the log file as a csv file and I needed office to open it up, is this the correct way and here is he file incase anybody wanted to have a look as I know nothing here??

 

 

 

dcs.log

DCS 2025-09-25 22-23-55.9751838 UTC.csv

Edited 14 hours ago by The_Nephilim
added file

[sleighzy]

4 hours ago, The_Nephilim said:

yes I had AV disabled when running but not when testing will do that as well. and here is my DCS Log and I will try to run that program you suggested sleighzy..

I had exported the log file as a csv file and I needed office to open it up, is this the correct way and here is he file incase anybody wanted to have a look as I know nothing here??

 

 

 

dcs.log 208.8 kB · 3 downloads

DCS 2025-09-25 22-23-55.9751838 UTC.csv 365.45 kB · 1 download

Mostly looks fine. There are a couple of blips, but I'm assuming that the dcs log file and the CSV file are for two different runs? Was curious if showed up in log for matching timestamps. I've attached a couple of screenshots from blips. The blips coincide with high App CPU timings as well. I noticed you're running Through The Inferno for this, so possibly it's just loading a bunch of stuff in, or scripts, at the time which are triggering this.

I see you're running both Quad-Views-Foveated and the OpenXR Toolkit. Do you have Turbo mode enabled in either of those? Turbo mode will throw off frame timings (it'd skew the numbers in this csv report as well). Quad-Views-Foveated has it on by default...except for SteamVR which you're currently using.

Overall though looked ok. How's the "feel" in general when you play? I wouldn't get too hung up on a blip (.1% frametime if this is what it's based on) if the game is smooth and you're just chasing a number which is an outlier (especially if due to to something like TTI).

 

EDIT: I don't use fpsVR so can't comment as to what it displays to you, or how it calculates it's numbers.
 

Edited 10 hours ago by sleighzy

[Hiob]

On the danger of repeating myself, if the average performance is ok and you are just concerned with .1% performance (maybe perceived as micro stutter), try to improve CPU latency by getting rid of IRC hogs like the power service. 

Excessive mouse polling rates can also have bad influence on the issue. (If you are using a fance "gaming" mouse + Software.

Other common culprits: RGB Software, Proprietary Apps from Razor, Logitech etc., Hardare Monitoring like HWinfo, Aquasuit....etc....

All the above stuff is pesting the CPU scheduler ALL the time with interrupt requests for updates and calls. Eventually the CPU has to divert cycles from important tasks like rendering to answer them.....

If you have occasional perceivable hickups, that is most likely caused by asset loading or scripts in the mission. Very little to nothing can be done about that.

 

 

Edited 3 hours ago by Hiob