Sr.

What's the headroom line mean? Running WMR @ 60Hz... In game flying over Batumi I get: fps 61.0 CPU headroom +22% (6.8ms) App CPU: 7597 App GPU: 12082

Yep, Windows Security. Here in particular. Good way to test would be to shut it off and see if it occurs.

Check your AV folder/application exclusions/permissions? It's literally the only I ever use a controller for

Can't say specifically as to open kneeboard, but I just drilled down through the registry as he posted. He does say that it is for removing stale/uninstalled instances. Which for my error was the issue... I had uninstalled VR NeckSafer then noticed the WMR Runtime entries tab was emptier than I remembered.

My system used to do this fairly often, even before OpenXR. To avoid it, II make sure there are no other windows present (minimized) on the desktop while DCS is launching. Also, once I launch DCS and the ED screen shows, I will give it a single click with the mouse. Beyond that, any other time it's occurred and I didn't catch it before sitting down in the seat, I would simply grab one of the G2 controller, turn in on, point it's cursor at the screen, press the menu button, push it again to exit, then shut off the controller... which somehow restored the mouse pointer.

Interesting. I may have to give it another shot.

Do tell... I returned one last year out of frustration.

I run mine at 100%/Full and it looks awesome. Granted, I run mine at 60Hz no (noticeable) flicker.

Just caught another OpenComposite update. Anyone know if there's a change log?

Right there with ya.

From all the hours I've spent messing back and forth, Only using something like Rivatuner or Radeon Chill to the lock fps, or better still, run the G2 in 60Hz. (no MR needed)

Update...I am no longer relying on this "loop", I simply do not fold it open when removing or putting on the headset.

That was my next guess... the cable. If yours was a gen 1 cable (without the handy on/off button), I would call about getting the "offered" replacement. Short of that, I still have my Gen one (brand new). I had just received IT as a replacement when my first cable went bad, due to bending at the point of attachment. Then I saw they were offering the gen 2 cable as a free replacement. Told me I could just keep the other. If you want to cover shipping, it's yours brother. Still works perfectly, I only ever plugged it in to check it. Here's my original thread on the topic. The number I have listed there should get you to an actual human being.

Try opening the settings under WMR portal, go to display, frame rate and switch it to 60Hz, let it do a restart of the app... if all is well, switch it back. Might also try resetting the environment while there.

Can someone explain "CPU headroom" as it displays in OXR tools? Just curious really. Running WMR @ 60Hz... In game flying over Batumi I get: fps 61.0 CPU headroom +22% (6.8ms) App CPU: 7597 App GPU: 12082

I'm stumped. https://www.tomshardware.com/news/amd-issues-fix-and-workaround-for-ftpm-stuttering-issues

hmm any cooling issues?

Only thing that jumps out immediately is MSAA. Even at 60Hz (for me) any amount of MSAA causes stuttering. The flickering on cloud edges. Well... that's more a DCS shortcoming. Especially where clouds meet hill/mountain surfaces. Also, you posted earlier "AMD doesn't have XMP but using their version DOCP and its set to 3200mhz" Is this a limitation of your motherboard? I have AMD and currently running 3200 RAM with XMP profile to 3600. (Asrock MB)

Thanks! That got it.

@edmuss Noticed this trying to troubleshoot VR Necksafer app. Is this normal now... seems like there used to be more lines listed here?

If you're using repro in OXR, make sure that "Anti-shake" is set to 0% Good call on the RGB garbage... another culprit is the Alienware command center app. I only have a AW monitor and if it's running, DCS/VR is a **** show. If you haven't already, try running the G2 at 60Hz under the WMR settings page. Most hate it because of flicker. I'm one of the lucky few who don't "see" the flicker. With that, I run no repro, and stay pegged at 60fps with pretty high DCS settings. Looks incredible on my end.

DCS settings: Try Terrain detail; low Water detail; low/med On the VR tab, make sure pixel density is no higher than 1.0 Vis range: medium No MSAA This is a good resource for other things to check/tweak. Which driver you running on the 6900XT?

Definitely Unity and UE... maybe Vulkan (speaking of Vulkan...) I just remember reading through the article wishing ED would do it if it was that "simple." I may have it confused with FSR/FSR2 though.

Just FYI... there's a History viewer built in to FpsVR that gives a good list and graph of stats between session. Can't recall where Steam stores it but, it was call fps History Viewer.exe. May have to be enabled via the onscreen (HMD) menu.

I honestly can't understand the hesitance to do so. I've read multiple devs state it took a couple hours. Tops.