HW/Performance issue related to VR, help needed

Hi all,

I posted similar problem before, but still need some help.

Having been fiddling around for a while with different settings with the hope to improve VR performance, it ended up no joy. So I believe the problem must be elsewhere.

This thing is weird. I seriously need some professional advice.

I'm not a computer expert, neither a noob. Having said that, here's my core HW configuration:

CPU: i7-6700 @ 3.4GHz

RAM: 24GB (8x2 + 4x2, 2133MHz)

MB: Intel z170 (it is a Dell MB as part of my XPS8910)

Graphic: GeForce RTX 2080 Ti (Gigabyte, 11G VRAM)

Intel HD 530 (Integrated)

SSD: SATA SSD (OS) + NVMe (Game and page file)

Monitor: Dell S2415H(1920 x 1080) x 2

VR: Samsung Odyssey+ (WMR + SteamVR)

PSU: CoolerMaster MWE Gold 750w

Now, the problem is, when in DCS, regardless of graphic settings, the FPS is around 10-30 for most of the time. I'm not saying settings doesn't affect FPS, but it never stable close to or above 40. It varies significantly in different scenes within that range, feels like the computer is stressed to handle its task.

However, the weird thing is: when I look into the load of CPU, RAM or GPU, none of them are stressed.

All the CPU cores are at 37-64%, RAM is at around 16G (about 70%), GPU is at 60%. See the attachment which I captured right after I quit from a mission in DCS.

A couple of things I noticed though:

1. Bus Interface usage is very low. However, checking in GPU-Z shows that the card is working at PCIe x 16 3.0@ x 16 3.0. So looks all good.

2. VRAM was fully used at around 98% when in game. However, given the Bus Interface usage is very low, it seems to me that it might be just the GPU intentionally maximizing VRAM usage rather than being stressed.

3. Reliable Voltage Limit and Operational Voltage Limit were constantly set to 1 when in game. (as shown in CPUID HWMonitor). However, research on internet shows me that that's normal.

4. RAM is at 2133MHz, I know this speed isn't high. However, I saw people having good DCS performance using same RAM speed.

I feel something, something is dragging the system performance! But I just can't find out what it is!!!

What are your settings?

Do you have motion reprojection enabled for steam VR?

Edit the file "C:\Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings"

"driver_Holographic_Experimental" : {
       // Motion reprojection doubles framerate through motion vector extrapolation 
       //     motionvector = force application to always run at half framerate with motion vector reprojection
       //     auto         = automatically use motion reprojection when the application can not maintain native framerate
       "motionReprojectionMode" : "auto",

With SteamVR set to 100% resolution, I use this for my DCS VR options config (located at %userprofile%\Saved Games\DCS\Config\options.lua) :

options = {
["VR"] = {
	["box_mouse_cursor"] = true,
	["custom_IPD"] = 63.5,
	["custom_IPD_enable"] = false,
	["enable"] = true,
	["hand_controllers"] = false,
	["pixel_density"] = 1.4,
	["prefer_built_in_audio"] = true,
	["use_mouse"] = true,
},
["difficulty"] = {
	["RBDAI"] = true,
	["aircraftMode"] = true,
	["avionicsLanguage"] = "native",
	["birds"] = 0,
	["cockpitStatusBarAllowed"] = false,
	["cockpitVisualRM"] = false,
	["compassTape"] = true,
	["controlsIndicator"] = true,
	["easyCommunication"] = false,
	["easyFlight"] = false,
	["easyRadar"] = false,
	["externalViews"] = true,
	["fuel"] = false,
	["geffect"] = "realistic",
	["hideStick"] = false,
	["iconsTheme"] = "nato",
	["immortal"] = false,
	["labels"] = 2,
	["map"] = true,
	["miniHUD"] = false,
	["optionsView"] = "optview_all",
	["padlock"] = false,
	["permitCrash"] = false,
	["radio"] = false,
	["reports"] = true,
	["setGlobal"] = true,
	["spectatorExternalViews"] = true,
	["tips"] = true,
	["units"] = "imperial",
	["userMarks"] = true,
	["userSnapView"] = true,
	["weapons"] = false,
},
["format"] = 1,
["graphics"] = {
	["DOF"] = 0,
	["LensEffects"] = 2,
	["MSAA"] = 1,
	["SSAA"] = 0,
	["SSAO"] = 0,
	["anisotropy"] = 4,
	["aspect"] = 2.3888888888889,
	["chimneySmokeDensity"] = 0,
	["civTraffic"] = "low",
	["clouds"] = 1,
	["clutterMaxDistance"] = 430,
	["cockpitGI"] = 0,
	["disableAero"] = false,
	["effects"] = 3,
	["flatTerrainShadows"] = 2,
	["forestDistanceFactor"] = 0.5,
	["fullScreen"] = true,
	["heatBlr"] = 1,
	["height"] = 1440,
	["lights"] = 2,
	["motionBlur"] = 0,
	["multiMonitorSetup"] = "1camera",
	["outputGamma"] = 2.2,
	["preloadRadius"] = 150000,
	["rainDroplets"] = true,
	["scaleGui"] = false,
	["shadowTree"] = false,
	["shadows"] = 1,
	["sync"] = false,
	["terrainTextures"] = "max",
	["textures"] = 2,
	["treesVisibility"] = 6000,
	["useDeferredShading"] = 1,
	["visibRange"] = "High",
	["water"] = 1,
	["width"] = 3440,
},
["miscellaneous"] = {
	["Coordinate_Display"] = "Lat Long",
	["F2_view_effects"] = 1,
	["TrackIR_external_views"] = true,
	["accidental_failures"] = false,
	["autologin"] = true,
	["chat_window_at_start"] = true,
	["collect_stat"] = false,
	["f10_awacs"] = true,
	["f11_free_camera"] = true,
	["f5_nearest_ac"] = true,
	["force_feedback_enabled"] = false,
	["headmove"] = false,
	["show_pilot_body"] = true,
	["synchronize_controls"] = true,
},
["plugins"] = {
	["CaptoGlove"] = {
		["armBending"] = 60,
		["enable"] = false,
	},
	["F-14B"] = {
		["JESTER_Camera"] = true,
		["JESTER_HeadMenu"] = true,
		["JESTER_LandingCallouts"] = true,
		["JESTER_SwitchToPSTT"] = true,
		["RadioMenuPttOptions"] = 0,
	},
	["Su-25T"] = {
		["CPLocalList"] = "default",
	},
	["TF-51D"] = {
		["CPLocalList"] = "default",
		["assistance"] = 100,
		["autoRudder"] = false,
	},
	["VAICOM"] = {
		["VAICOMClientIP"] = "127.0.0.1",
		["VAICOMDebugModeEnabled"] = false,
	},
},
["sound"] = {
	["GBreathEffect"] = true,
	["cockpit"] = 100,
	["gui"] = 100,
	["headphones"] = 100,
	["headphones_on_external_views"] = true,
	["hear_in_helmet"] = true,
	["music"] = 100,
	["radioSpeech"] = true,
	["subtitles"] = true,
	["volume"] = 100,
	["world"] = 100,
},
["views"] = {
	["cockpit"] = {
		["avionics"] = 1,
		["mirrors"] = false,
		["reflections"] = false,
	},
},
}

I have a 1080ti and a 5GHz 8700k with 32GB of DDR4 C14 3200 and get a solid 45FPS with the Odyssey+. I have MFAA set to ON in the Nvidia control panel for DCS.

Hi, I was looking at your specs and noticed you have the Intel Intergrated card listed is that also enabled along with the nVidia card?? you should have the intel card disabled..

Also it would help if your overclocked the CPU a bit.. I also noticed the memory is 2133, was the the set speed on your RAM when you purchased it??

Most memory like if it said on there 3000mhz it would need the XMP Profile enabled in BIOS but it the stock speed it 2133 never mind the XMP PRofile..

What are your settings?

 

Do you have motion reprojection enabled for steam VR?

 

Edit the file "C:\Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings"

 

"driver_Holographic_Experimental" : {
       // Motion reprojection doubles framerate through motion vector extrapolation 
       //     motionvector = force application to always run at half framerate with motion vector reprojection
       //     auto         = automatically use motion reprojection when the application can not maintain native framerate
       "motionReprojectionMode" : "auto",

 

With SteamVR set to 100% resolution, I use this for my DCS VR options config (located at %userprofile%\Saved Games\DCS\Config\options.lua) :

 

options = {
["VR"] = {
	["box_mouse_cursor"] = true,
	["custom_IPD"] = 63.5,
	["custom_IPD_enable"] = false,
	["enable"] = true,
	["hand_controllers"] = false,
	["pixel_density"] = 1.4,
	["prefer_built_in_audio"] = true,
	["use_mouse"] = true,
},
["difficulty"] = {
	["RBDAI"] = true,
	["aircraftMode"] = true,
	["avionicsLanguage"] = "native",
	["birds"] = 0,
	["cockpitStatusBarAllowed"] = false,
	["cockpitVisualRM"] = false,
	["compassTape"] = true,
	["controlsIndicator"] = true,
	["easyCommunication"] = false,
	["easyFlight"] = false,
	["easyRadar"] = false,
	["externalViews"] = true,
	["fuel"] = false,
	["geffect"] = "realistic",
	["hideStick"] = false,
	["iconsTheme"] = "nato",
	["immortal"] = false,
	["labels"] = 2,
	["map"] = true,
	["miniHUD"] = false,
	["optionsView"] = "optview_all",
	["padlock"] = false,
	["permitCrash"] = false,
	["radio"] = false,
	["reports"] = true,
	["setGlobal"] = true,
	["spectatorExternalViews"] = true,
	["tips"] = true,
	["units"] = "imperial",
	["userMarks"] = true,
	["userSnapView"] = true,
	["weapons"] = false,
},
["format"] = 1,
["graphics"] = {
	["DOF"] = 0,
	["LensEffects"] = 2,
	["MSAA"] = 1,
	["SSAA"] = 0,
	["SSAO"] = 0,
	["anisotropy"] = 4,
	["aspect"] = 2.3888888888889,
	["chimneySmokeDensity"] = 0,
	["civTraffic"] = "low",
	["clouds"] = 1,
	["clutterMaxDistance"] = 430,
	["cockpitGI"] = 0,
	["disableAero"] = false,
	["effects"] = 3,
	["flatTerrainShadows"] = 2,
	["forestDistanceFactor"] = 0.5,
	["fullScreen"] = true,
	["heatBlr"] = 1,
	["height"] = 1440,
	["lights"] = 2,
	["motionBlur"] = 0,
	["multiMonitorSetup"] = "1camera",
	["outputGamma"] = 2.2,
	["preloadRadius"] = 150000,
	["rainDroplets"] = true,
	["scaleGui"] = false,
	["shadowTree"] = false,
	["shadows"] = 1,
	["sync"] = false,
	["terrainTextures"] = "max",
	["textures"] = 2,
	["treesVisibility"] = 6000,
	["useDeferredShading"] = 1,
	["visibRange"] = "High",
	["water"] = 1,
	["width"] = 3440,
},
["miscellaneous"] = {
	["Coordinate_Display"] = "Lat Long",
	["F2_view_effects"] = 1,
	["TrackIR_external_views"] = true,
	["accidental_failures"] = false,
	["autologin"] = true,
	["chat_window_at_start"] = true,
	["collect_stat"] = false,
	["f10_awacs"] = true,
	["f11_free_camera"] = true,
	["f5_nearest_ac"] = true,
	["force_feedback_enabled"] = false,
	["headmove"] = false,
	["show_pilot_body"] = true,
	["synchronize_controls"] = true,
},
["plugins"] = {
	["CaptoGlove"] = {
		["armBending"] = 60,
		["enable"] = false,
	},
	["F-14B"] = {
		["JESTER_Camera"] = true,
		["JESTER_HeadMenu"] = true,
		["JESTER_LandingCallouts"] = true,
		["JESTER_SwitchToPSTT"] = true,
		["RadioMenuPttOptions"] = 0,
	},
	["Su-25T"] = {
		["CPLocalList"] = "default",
	},
	["TF-51D"] = {
		["CPLocalList"] = "default",
		["assistance"] = 100,
		["autoRudder"] = false,
	},
	["VAICOM"] = {
		["VAICOMClientIP"] = "127.0.0.1",
		["VAICOMDebugModeEnabled"] = false,
	},
},
["sound"] = {
	["GBreathEffect"] = true,
	["cockpit"] = 100,
	["gui"] = 100,
	["headphones"] = 100,
	["headphones_on_external_views"] = true,
	["hear_in_helmet"] = true,
	["music"] = 100,
	["radioSpeech"] = true,
	["subtitles"] = true,
	["volume"] = 100,
	["world"] = 100,
},
["views"] = {
	["cockpit"] = {
		["avionics"] = 1,
		["mirrors"] = false,
		["reflections"] = false,
	},
},
}

 

I have a 1080ti and a 5GHz 8700k with 32GB of DDR4 C14 3200 and get a solid 45FPS with the Odyssey+. I have MFAA set to ON in the Nvidia control panel for DCS.

My settings are quite similar to yours. I also tried the motion reprojection. It only caps the FPS at the menu screen at 45 from 90. Nothing changed in game...

I think the problem has little to nothing to do with the settings. Reason is that if any HW is stressed, e.g. GPU load reaches 100%, we can change the settings to relive that stress and therefore improve the overall performance, e.g. FPS. But the issue here is that it seems none of the HW is under pressure. The explanation can only be: 1) on the software side (either VR or DCS) there's some bad logic causing unnecessary waiting, wasting the Render Cycle while also doing nothing; or 2) there is some HW bottleneck which haven't been found yet......

Hi, I was looking at your specs and noticed you have the Intel Intergrated card listed is that also enabled along with the nVidia card?? you should have the intel card disabled..

Yes, I use it to drive my second monitor, so the second screen wouldn't cost any resource on the main graphic card. Can you provide further insight in terms of why enabling/disabling that could impact the VR performance? Is there some mechanism behind?

Also it would help if your overclocked the CPU a bit..

I wished... but my i7 6700 and the Dell MB doesn't support that... Regardless that limitation, as I described before, I don't think CPU is now the bottleneck as none of the 8 cores are over 70% throughout the game. If they were at 90%+, I can see overclocking works, but unfortunately, that's not the case.

I also noticed the memory is 2133, was the the set speed on your RAM when you purchased it??

 

 

Most memory like if it said on there 3000mhz it would need the XMP Profile enabled in BIOS but it the stock speed it 2133 never mind the XMP PRofile..

Yes, that's the set speed. XMP is enabled as CPU-Z shows me...

My settings are quite similar to yours. I also tried the motion reprojection. It only caps the FPS at the menu screen at 45 from 90. Nothing changed in game...

 

I think the problem has little to nothing to do with the settings. Reason is that if any HW is stressed, e.g. GPU load reaches 100%, we can change the settings to relive that stress and therefore improve the overall performance, e.g. FPS. But the issue here is that it seems none of the HW is under pressure. The explanation can only be: 1) on the software side (either VR or DCS) there's some bad logic causing unnecessary waiting, wasting the Render Cycle while also doing nothing; or 2) there is some HW bottleneck which haven't been found yet......

You need to run something like GPUz or MSI Afterburner and watch the GPU load. It should hit 100%. If it doesn't, your bottleneck is CPU.

Since I've got a faster CPU than you, but a lesser GPU and still maintain at least 45FPS, it's logical to conclude that if you do have a bottleneck it's there. However, being that CPU limited at such a high resolution is HIGHLY improbable.

Make sure steam is set to 100% and not 200% and that MSAA isn't any higher than 2x and that shadows and mirrors are disabled. Those are the biggest FPS killers. Also I wouldn't bump PD higher than 1.4 or 1.5.

If none of this works, it may be time to do a clean Windows 10 install and start over.

You need to run something like GPUz or MSI Afterburner and watch the GPU load. It should hit 100%. If it doesn't, your bottleneck is CPU.

I used them both. Observation resulted the same... None of the CPU cores or GPU are stressed...

I hope it is not because something broken in my Win10 as my computer is doing great in basically any other games on my drive, that includes all Blizzard games and Destiny 2. All of them can run on maximum graphic settings without any stress...

Another thing to mention, not sure whether it might link to the problem or not. My computer used to be limited by CPU in DCS VR a while ago. One of the 8 cores was actually get stressed at about 80-90% while all the others were at about 40-50%. But after I tried Process Lasso and uninstalled it, I never saw that again, all the CPU cores are working at identical load. The DCS performance however hasn't been impact by that both with or without Process Lasso.

Anyway, your suspect on a broken OS is still legit, though I would exhaust all the other possible fixes before making that distress call.

imho, the CPU bottlenecks.

70% on all cores is where such things happen..

imho, the CPU bottlenecks.

 

70% on all cores is where such things happen..

While somewhat counterintuitive, I have to agree. In this case I don't think the CPU is able to push enough data to the GPU to bottleneck even in VR.

imho cpu temps are hot

HW/Performance issue related to VR, help needed

i’d be worried if project lasso was uninstalled but your operating system process scheduler is still modified to average out all work across all cores.

that doesn’t sound good.

imho, the CPU bottlenecks.

 

70% on all cores is where such things happen..

Though I suspect that as well, none of the CPU cores was close to 70%, seems there’s still room.

Sent from my iPhone using Tapatalk

While somewhat counterintuitive, I have to agree. In this case I don't think the CPU is able to push enough data to the GPU to bottleneck even in VR.

I feel it could be the case, but why statistics show differently that there’s actually a lot room left...

Sent from my iPhone using Tapatalk

i’d be worried if project lasso was uninstalled but your operating system process scheduler is still modified to average out all work across all cores.

 

that doesn’t sound good.

Yea, I know. Looked at their website, they said no modifications would left after uninstalling, but what I saw suggested differently...

However, I think it did an Ok job. I tried reinstall it last night and force DCS to run on one single core. That core was immediately maxed out, DCS FPS dropped from 20 to single digit (on a populated Stannis).

Re-enabling it on all the cores brought FPS back to 20.

Sent from my iPhone using Tapatalk

imo cpu temps are hot

The chassis is a bit stressed after I throw in the new beefy graphic card and replacing for a slightly bigger PSU.

Will CPU throttle itself on high temperature? Is some 70 degrees enough to trigger that?

It haven’t shown any degradation over hours of lengthy use in DCS VR though...

Sent from my iPhone using Tapatalk

yes cpu can throttle itself but it depends on the cpu, I remember how it happened in gtav when the fps dropped dramatically when the cpu exceeded 70 °

yes cpu can throttle itself but it depends on the cpu, I remember how it happened in gtav when the fps dropped dramatically when the cpu exceeded 70 °

Thanks, but how do I tell whether that’s actually happening? Any figure that I should look at?

Sent from my iPhone using Tapatalk

Thanks, but how do I tell whether that’s actually happening? Any figure that I should look at?

 

 

Sent from my iPhone using Tapatalk

If the GPU is not hitting 100% utilization, it has to be CPU bound.

That's all you really need to look at.

My 1080ti is around 89-99% GPU in DCS VR at any given time.

Unclear to me what CPU% is measuring. For VR, I think render time is a more helpful measurement. Check out the NVIDIA FCAT VR performance tool https://www.geforce.com/whats-new/guides/fcat-vr-download-and-how-to-guide.

Among other things, the guide is a great read.

See if you can monitor both your CPU and your GPU render times. Both have to be 11ms to run 90fps and 22ms to run 45fps. I'll bet it's your CPU.

Not all of your settings affect the GPU alone. Vis range, trees and shadows have an effect on CPU, and cutting back on those will help.

Hardware-wise, it gets complicated. Personally I think a good motherboard was a good investment (for me anyway), "overclocking" RAM (which in my case just meant running the RAM at its rated speed) helped me a lot and if you're lucky you might be able to get a meaningful overclock on your CPU too.

DCS is fun but hang on to your wallet.

ETA: I guess your CPU will burst at 4.0GHz? That's not bad but it ain't gonna allow you to run much more than flat shadows or vis range more than medium and I'd put the tree slider about in the middle too. Won't be as pretty but the game will be playable. Good news is, you can crank up anisotropic filtering all you want. With that HMD you don't need much if any supersampling/PD, I'd crank the MSAA if I had your rig

Unclear to me what CPU% is measuring. For VR, I think render time is a more helpful measurement. Check out the NVIDIA FCAT VR performance tool https://www.geforce.com/whats-new/guides/fcat-vr-download-and-how-to-guide.

 

Among other things, the guide is a great read.

 

See if you can monitor both your CPU and your GPU render times. Both have to be 11ms to run 90fps and 22ms to run 45fps. I'll bet it's your CPU.

 

Not all of your settings affect the GPU alone. Vis range, trees and shadows have an effect on CPU, and cutting back on those will help.

 

Hardware-wise, it gets complicated. Personally I think a good motherboard was a good investment (for me anyway), "overclocking" RAM (which in my case just meant running the RAM at its rated speed) helped me a lot and if you're lucky you might be able to get a meaningful overclock on your CPU too.

 

DCS is fun but hang on to your wallet.

 

ETA: I guess your CPU will burst at 4.0GHz? That's not bad but it ain't gonna allow you to run much more than flat shadows or vis range more than medium and I'd put the tree slider about in the middle too. Won't be as pretty but the game will be playable. Good news is, you can crank up anisotropic filtering all you want. With that HMD you don't need much if any supersampling/PD, I'd crank the MSAA if I had your rig

Thanks for the awesome advice. Not sure if it works with WMR, but I certainly will give it a try as much as I can to find the problem.

The CPU does have a boosting feature, I can’t control it though. Dell’s MB greyed overclocking option. But will try your suggested settings and see if that helps.

Sent from my iPhone using Tapatalk

I am also stuck with the 45 fps limit on my machine. Can you recommend a tool for viewing CPU render times?

I am also stuck with the 45 fps limit on my machine. Can you recommend a tool for viewing CPU render times?

Did you enable motion reprojection? If so, unless your hitting a solid 90 FPS, motion reprojection will keep you at 45.

I dont have a "MixedRealityVRDriver" folder. I have a "SteamVR" folder instead. Although I can find a "default.vrsettings" file, it has no entry for motion reprojection. Might be because I installed steamVr quite long ago. So I would guess motion reprojection is off then?!

I am having similar issues. You are definitely CPU bound.

see this post here: https://forums.eagle.ru/showpost.php?p=3879256&postcount=10

Unclear to me what CPU% is measuring. For VR, I think render time is a more helpful measurement. Check out the NVIDIA FCAT VR performance tool https://www.geforce.com/whats-new/guides/fcat-vr-download-and-how-to-guide.

 

Among other things, the guide is a great read.

 

See if you can monitor both your CPU and your GPU render times. Both have to be 11ms to run 90fps and 22ms to run 45fps. I'll bet it's your CPU.

 

Not all of your settings affect the GPU alone. Vis range, trees and shadows have an effect on CPU, and cutting back on those will help.

 

Hardware-wise, it gets complicated. Personally I think a good motherboard was a good investment (for me anyway), "overclocking" RAM (which in my case just meant running the RAM at its rated speed) helped me a lot and if you're lucky you might be able to get a meaningful overclock on your CPU too.

 

DCS is fun but hang on to your wallet.

 

ETA: I guess your CPU will burst at 4.0GHz? That's not bad but it ain't gonna allow you to run much more than flat shadows or vis range more than medium and I'd put the tree slider about in the middle too. Won't be as pretty but the game will be playable. Good news is, you can crank up anisotropic filtering all you want. With that HMD you don't need much if any supersampling/PD, I'd crank the MSAA if I had your rig

Somehow managed to successfully run FCAT with my WMR. The chart from FCAT Analyzer doesn't help much as I can't find a way to show anything other than the frametime. However, the captured data file looks interesting.

Total GPU render time (ms): is typically around 27-32

Compositor idle time (ms): is typically around 1.2-11. This looks like the time taken by CPU.

Client Frame Interval (ms): is typically around 41-52 while it can also go down to 38 or up to 82

Submit frame (ms): is typically 0.11 - 0.22. That article suggested that "not near-zero indicates driver issue", not sure if this value can be considered near-zero or not...

Frame start (ms) between 2 frames can be around 42-56 (ms), sounds pretty bad, the actual in game FPS at the same time was averaged at about 30. Not sure how that gap between frames translated into this FPS...

Anyway, still confused by the data...... and feels like the problem is more at my GPU side?

I've attached the captured data file as well as a screen shot, appreciate if you can shed some light on this.

Also copy-pasted some content below as well:

Frame Index	 Frame start (ms)	 Render end (ms)	 Warp end (ms)	 HMD sample start (ms)	 Number Times Presented 	 Number Dropped Frames 	 App Miss Count	 Number Mis Presented	 Reprojection Flags	 Scene render GPU time (ms)	 Total GPU render time (ms)	 Compositor GPU render time (ms)	 Compositor CPU render time (ms)	 Compositor idle time (ms)	 Client Frame Interval (ms)	 Present call CPU (ms)	 Wait for present CPU (ms)	 Submit frame (ms)	 New poses ready(ms)	 New frame ready(ms)	 Compositor update start(ms)	 Compositor update end(ms)	 Compositor render start(ms)	 ProcessID	 API version
31182	402213.9436	402241.2736	402241.4877	402174.6313	1	0	0	0	4	27.32998466	27.54406548	0.01408	0.345600009	1.684100032	42.59149933	0.121800005	0.0067	0.195499986	402181.9143	402223.46	402223.5136	402223.5549	402224.7464	25052	0
31183	402262.9523	402291.8839	402292.0984	402224.533	1	0	0	0	4	28.93152046	29.14611244	0.014592	0.283100009	7.881199837	46.62889862	0.115000002	0.0063	0.2333	402227.0389	402272.7399	402272.7616	402272.7899	402273.8292	25052	0
31184	402315.2778	402342.6761	402342.8905	402273.679	1	0	0	0	4	27.39830399	27.61267281	0.014368	0.363599986	11.89529991	43.57130051	0.119999997	0.009000001	0.150000006	402282.215	402324.6607	402324.7136	402324.7371	402326.0592	25052	0
31185	402371.2049	402399.4182	402399.6406	402325.7976	1	0	0	0	4	28.2132473	28.43571281	0.022464002	0.374300033	11.04770088	43.1371994	0.176400006	0.0067	0.168300003	402338.5551	402380.3275	402380.4326	402380.4774	402381.9621	25052	0 

2019-04-17 01-30-22_OpenVR.zip