Supmua

DCS originally uses OpenVR (and Oculus runtime) and the default output is still OpenVR. SteamVR supports both OpenVR and OpenXR API.

Yep, hoping the techs will trickle down to the PCVR side. It’s quite cool aiming gun reticle or selecting menu options by just pointing your eyes directly at the target.

Mbucchia states that ETFR is possible with DCS (via OXRTK) if ED changes some codes. As long as most headsets out there don’t feature eye tracking it is hard to entice developers to add this in. Unfortunately, this is a common scenario in PCVR. We have all these extra features on our HMDs but nobody is using them and VR headsets are just functioning as a monitor with head tracking.

^That was a measure to prevent intermittent connection loss, screen blackouts etc. No ETFR with DCS, sorry was talking about ETFR with PSVR2. For DCS fixed foveated rendering works fine via OXRTK and yields extra 1ms reduction in GPU frametime with Wide/Quality (probably more with lower settings).

Try tightening up the headset’s USB connection, pull the cable out of headset’s socket and twist it 180 degree and plug back in. See if this gets rid of the problem.

No but the video output signal isn’t encrypted so people can try to hack it to make it work, but that typically doesn’t go well. AFAIK they can easily release the PC version of this and take the big chunk of market share (OLED HMD plus advanced controllers for $500 is quite a steal in my book), but they probably won’t. Clarity wise the Aero still wins by a mile.

If Sony decides to release this headset for the PC I can see them take the number one spot away from Meta. They probably won’t as their main focus is the PlayStation console, and Apple likely won’t push gaming either but instead their HMD as a laptop replacement.

lol there's lots to learn about this new headset and platform. Hardware-wise it's very interesting because it's like a Reverb G2 with wide FOV, high edge to edge clarity, plus OLED HDR. Fresnel lens that they use allows plenty of lights to pass through to meet HDR qualification (Pancake in comparison kills about 80% of the lights going through thus reducing brightness/contrast/vibrance significantly). Then there's haptic feedback on the headset itself as well as force-feedback trigger buttons, some of which we could probably use in DCS if other hardware companies decide to make them (imagine haptics on your HOTAS when you squeeze the trigger, or throttle shakes when you go afterburner, etc.). Software is also tightly integrated with the hardware taking full advantages of all the features (full use of eyetracking for foveation, menu selection, aiming, etc.). We can learn from SONY's insights and engineering prowess, and they seem to be very serious about VR tech right now.

I think it depends on what your frametime is doing during those moments. If you can maintain less than 16ms (both CPU and GPU) there should be minimal hiccups. I'm mostly using Steam OpenXR though (no significant issues), need to do more testing on other modes but once my PSVR2 arrives I prob won't be touching anything else for a week lol.

Anyway, more on the Motion Smoothing beta. It increases my GPU frametime by 4.5ms with minimal effect on CPU frametime. This is a huge tax on GPU frametime unless you have top of the line GPU such as 4090 (almost like dropping GPU from 4090 to 3090Ti). Any frametime spike that goes above 22ms will cause retention artifacts right away, so it doesn't matter how good your average fps is but it's more of how good your minimum fps is in order to remain artifact free. There is also mild artifacts in this mode even with constant 45 fps but it's mostly in the peripheral vision so it's very hard to notice unless you glance around while turning your head, this is more noticeable when compared back to back against 90 fps mission in non-framelock mode. So for completely artifact free and super smooth gameplay, nothing beats the good old 90 fps if your rig and setup can get you there. The non-motion smoothing 45 fps lock also gives smoother gameplay albeit at the cost of blurry objects that are close and moving towards your plane.

Makes no sense to me why it works but apparently it did. Reshade shouldn't work with OpenXR because the API is not supported. I'd still recommend deleting WMR stuff, wiping SteamVR then fresh reinstall though.

You can use Varjo OpenXR but you need to install mbucchia’s wrapper that disables Quadview. My recommendation though is to delete all the WMR related files because it can still mess you up in the future. The current OpenXR runtime in Steam Dev Window should be either Steam or Varjo only, not WMR.

The WMR stuff shouldn’t be on there. I think that’s what’s causing trouble.

According to the people on Discord, motion smoothing taxes the system quite a bit so your current optimal settings will likely need to be reduced to accommodate this mode. I won’t be doing much testing as I’ll be spending most of my time with the PSVR2 this week.

Have you tried running it via Steam OpenXR? Enable in Steam setting/Developer, and this should automatically turn off Varjo OpenXR switch in VB.

You can pick and choose between auto vs 45 vs 30 fps lock. This is beta so things can still change and it might not be ready for the mass. I only had little time with it and most of it was figuring out why my DCS kept crashing. Might be safer that way if you value stability. But I think this is it for motion smoothing, they did fix the cockpit stuttering…took about a year lol.

Motion smoothing seems to be fixed in the latest beta--and it's good from my brief experience before leaving home for work (tested with Steam OpenXR). Go to Discord and ask to get in if you want to test this. If you use mbucchia's wrapper that disables Quad view or any mods that go directly into the Varjo folder my recommendation before installing the beta is that you should also manually remove the entire Varjo folder in the C drive (or wherever your default location is) prior to installing the new software because there might be some conflict causing DCS to crash (might have been the old VarjoOpenXR.json in my case).

I don’t have the Steam version of DCS, but I suspect that you may need to add the force command line differently. Try R click on DCS from Steam and choose Properties, and under Launch Options add the force OpenXR command line that way. Let me know if it works too.

Stuttering has been fixed but motion smoothing isn't, hopefully will be in the next version.

Use Necksafer Beta2 version instead of the newest one.

HDR support would be great also (of course we still don’t have HDR capable hmd). I used to be skeptical but newer games such as Hogwarts Legacy in HDR and full RT mode really floored me. Spent hours calibrating my OLED TV settings just for that game.

Trying to simplify this. CPU: handles logic, AI, object rendering, movement, collision, assigns graphic processing tasks to GPU and has to wait until that task is done (e.g. rendering one frame) before it can move on. GPU: handles graphic processing, shaders, textures, lightings, reports back to CPU. Typically has tons of cores (16,384 in RTX 4090 vs a dozen or so in a typical CPU). In general, the limiting factor is whichever has the highest frametime as the next rendered frame cannot happen until the whole process is completed. So if your CPU frametime is 7 ms and GPU frametime is 14 ms, the final frametime will be 14 ms for that frame and the repeated processes determine the overall fps—and in this case, GPU limited which is a typical scenario for most games out there. Personal experiences. Going from 9900K/3090 to 9900K/4090 gives me instant 90 fps in Caucasus free flights as CPU isn’t taxed much in these type of missions. Note that I would never hit 90 fps with any CPU in combination with 3090 because the GPU itself isn’t strong enough to produce low enough frametime (below 11.1 ms) with my current settings (3Kx3K pixels). The fps gain is reduced in complex maps such as Marianas or crowded MP mission because CPU frametime takes more hits in those scenarios, and this is alleviated after I upgraded my 9900K CPU to 5800X3D. With this my min fps improves a lot while max fps stays the same (hence avg fps goes up), on average scenarios. But it gets more complex in VR because of the headset’s fixed frequency and motion smoothing. If you use motion smoothing, unless you hit 90 fps (or whatever your headset’s frequency is), the fps will drop to the nearest multiplication factor such as 45. Say, you currently get perfect constant 45 fps and upgrade to a system that cannot consistently hit 90 fps you will not see much benefit. On the other hand if you’re currently below the 45 threshold and upgrading CPU and/or GPU will get you way above then smooth 45 fps gameplay will happen.

This could’ve been my next headset had it been more versatile. The pricing is reasonable but sort of let down by fixed IPD, customed face plate that only fits your face, and housing that’s too small to support eyeglasses. The image fidelity/clarity probably will be incredible with the high res OLED screens and narrowish FOV. The Panasonic Shiftall Megane X doesn’t have these shortcoming but quite expensive for what you get.

DLAA with DCS will probably yield the best image fidelity, although I’m probably going to use DLSS mostly since its upscaling is good enough and the performance gain is substantial in most games. May be ED will also think about adding some raytracing options to the future update, would be awesome to see RT shadows and reflections in the cockpits.

Agree with this. Need to pester Reshade creator to make it compatible with OpenXR.