Qcumber

Thanks for the heads up. I'll avoid upgrading.

I have been looking at factors which affect VR performance. You can have a relatively stable FPS but still have stutter if your CPU and/or GPU render times are borderline for maintaining the headset refresh rate. For example if you run at 72Hz the max render time is 13.89ms. If your average render time is about 13ms, the min and max times might vary from about 10ms to 15ms. Anything that goes above 13.89ms will result in dropped frames. You can have a significant number of dropped games but without any noticable change in average FPS. This can manifest as microstutter. If you are technically minded you could try my guide here and see what your render times look like. Compare different tacks, one where you see stutter and one were you don't and see if there is any difference. Or just run a track with XRFrameTools and send me the log and I'll do the rest. Edit: scratch that. I forgot you are using a monitor. However some of these principles will still apply.

Are you trying to stress your CPU, GPU or both? Settings like shadows, AA etc will stress your GPU. Lots of objects will stress your CPU. Any of the "cold start" or "take off" instant actions in the Marianas map will seriously tax both CPU and GPU. The F4 is a good one to try if you have this, or the F-14. Just run each one for a minute and save the tracks then you can repeat them with different settings.

A 5080? It's depends where you live. In the UK availability is not too bad if you keep a close eye on local stocks. It might be worth using a price check bot.

Sorry. Just looking at this again. I had misunderstood. Yes, it does look like the more accurate results are with prefer "framerate over latency" is ON. I presume you are running at 90Hz with reprojection? It would worth repeating to see if the results are consistent. Is this a very demanding track? It looks like you have a lot of missed frames even with reprojection. Do you get any stutter?

Interesting results. That is a huge difference in GPU latency. It might be an error in the capture. If I enable Turbo mode it gives weird results: https://github.com/fredemmott/XRFrameTools?tab=readme-ov-file#supported-measurements

I am getting some amazing performance in VR at 90 Hz with the 9800x3d and 5080 combination. I'll try to post some performance tests and a video at the weekend.

Thanks. I am glad it's useful but it still needs some work. Not yet but funnily enough I was thinking about this today. Not sure as such but if I understand correctly XRFrametools shows quite a large variations in FPS for each frame. I am guessing that these are captured based on an amalgamation of frametimes (!?). I should ask Fred Emmott about this. Maybe it would be useful to calculate FPS averages over 10 or so frames. It is some I am working but need to make sure I am doing this correctly. It might be useful to create some standards to test across different systems. We can't account for variations in PC builds but we can look at relative performance on each build. I was thinking about 3 tracks. A light one, an intermediate one and a heavy one. It's probably best that I post the specific suggestions in my other thread relating to methods. The FE does not come with a support bracket and the official information is that you do not need one. However there is noticeable "sag" so I installed a bracket just in case. The three pin connector is a PITA. I ended up ordering a new power cable as i only had two that would fit the bill. I initially had to daisy chain one of them. All OK now though.

Have you tried using the meta link app instead of VD?

Anyone remember this? Nostalgia while we waited for the Germany map.

UPDATE 13 April 2025 The spreadsheet has been updated as follows: Maximum latency now 50 ms for CPU and GPU charts' FPS count CPU render and GPU render over time added. Vertical lines added to represent 90, 72, 45 and 36 FPS respectively (the last 2 relate to reprojection at 90Hz and 72Hz). [The updated file is in the first post] The charts now look like this:

To follow on from speed-of-heat, and with regards your headset, could you please post details of you VD settings? Ideally a screen shot of the in-game overlay so we can see your latencies ect. What do your CPU and GPU frametimes look like? Are you using QVFR?

I'll update it later so that it has up to 50 ms then set all the charts to the max value. Then it will be standardized for reprojection frametimes too. I probably won't get chance until this evening UK time though.

You could send me a recorded track then I can try running it on my PC. See if I get the same issues.

I wonder what the 5060ti 16Gb will look like in DCS. Might be a consideration instead of the 5070.

Yes. Just go into the chart and increase the data range for that sample. I think I have included up to 50ms. If no then I can always update the blank spreadsheet and repost it.

The GPU frame times are longer than 20 ms so they were not showing. I have extended the chart to 30ms. I've updated the SS for you. What DCS settings are you using and what is the module/map/track? ColdViPer benchmark.xlsx

What is the module and map? If you send me the track I can try running it and see if I get the same issues.

I'm not sure. It could be. Try running a track without it.

Thanks. I have had a look at this. These are plots of your frame times and FPS. Firstly your GPU performance. The mean latency is 10.8 ms which is well below what you need to maintain 72 fps. However there is a demanding part of the track which pushes the latencies higher than 13.88 ms resulting in about 10% missed frames (everything right of the black dotted line). This may not be noticeable in average FPS count but can be seen as stutters. Next the CPU frametimes. As I said earlier App CPU is normally very low. Below are plots from both App CPU and Render CPU times and the total CPU time. The App CPU time is consistently grouping around 13ms. The render CPU time is all over the place between 5 and 16 ms. Combined this gives a mean CPU time of 21 ms which is very high. Finally a chart showing the latencies and FPS over the whole track. I have edited out the start and end as these artifacts presumably as you started and stopped the recording. The GPU render times are good for the first 20s or so (around 10-11 ms so well below the magic 13.88 needed to maintain 72 FPS (horizontal black dashed line)). App CPU time is around 13 ms. As I said above this is normally low (1-3 ms). It is the time needed for DCS to process the information before it can be rendered and sent to the GPU. The middle of the track appears to be very heavy on both your GPU and CPU as there are periodic spikes in both GPU and CPU frametimes and corresponding drops in framerates. This suggests to me that your hardware cannot handle the DCS settings. So what next? I would suggest reducing DCS settings to as basic as possible and run a track with a simple module over a non populated part of Caucasus above 10000 feet. Keep clouds to a minimum. This should then show if it is a limitation of your hardware or if is something else.

Are you using link cable? If so then the max bitrate is 960 mbps. Try increasing to this and see if it works OK on your system. I think setting to 0 is default but I can't remember what that is. I presume that you mean Open XR Toolkit? Open XR is the API through which DCS and the Meta app communicate.

Just try disabling Turbo in QVFR and OXRTK for now. You can still then record the stats.

I really hope they do. With a possible extension across the Netherlands to the east of England. That would make long range missions to Berlin possible.

Yes. Good point regarding QVFR. This could have Turbo enabled which would mess with OXRTK stats. I am using the latest NVIDIA driver with the 5080 with no issues. From what I have read, most issues with 50xx GPUs are related to early versions of the 572 driver. Or using 40xx or 30xx GPUs.

You need to get a direct download. Here is the thread I started with Fred on GitHub. Hopefully that link will work ok. Just use this version for the log conversion not the capture. https://github.com/fredemmott/XRFrameTools/issues/34#issuecomment-2737326559 XRFrameTools is still in "alpha" but hopefully there will be an update soon so that this issue is fixed.