Supmua

Could be cable issue. Mine is also a bit loose at the HMD connection. Try unplugging the cable to the headset’s top left compartment and twist it 180 degree before plugging back in, that may solve the problem but if it persists then you should contact tech support. Maybe I have higher tolerance for VR artifacts, for me it’s quite acceptable and playability-wise it’s a toss up between this and 45 fps lock without MS. Or perhaps I’m so used to playing games with PSVR2, on that setup motion reprojection is pretty much the norm as the PS5 can’t really generate 90 fps in most games.

When you deselect Varjo OpenXR the game will not run in VR unless you also manually choose SteamVR as OpenXR runtime in SteamVR’s developer setting (because there’s no longer a specified runtime to execute OpenXR API). If you are using any mod/add ons I recommend removing them all except mbucchia extension wrapper that disables quad output. Might be a good idea to do DCS repair also. You do not need any command line to run DCS mt as the default output is now OpenXR. You just pick either Varjo or SteamVR runtime to run OpenXR.

Make sure you run DCS.exe from bin-mt folder, not bin folder. The non-mt build’s default output is still OpenVR and the wrapper doesn’t work with that unless you force OpenXR API via command line.

DCS MT gives significant performance uplift in places that would normally trash your fps due to CPU bottlenecking. You may not see much improvement in light missions depending on the settings and preexisting CPU/GPU frametimes, although this update also fixes shadows issues and should yield better performance in general even without MT. The significant thing I notice is that my frametime graphs stay smooth with barely any spikes with the MT if I don’t go crazy on resolution setting, even with motion smoothing option.

Testing PD setting 0.9 with Aero's Higher setting. The image quality is still very good at 0.9x and GPU FT drops by 1-1.5ms, when coupled with fixed foveation (wide/quality) which gives another 1ms GPU FT drop, the overall performance gain is quite good now that we no longer have significant CPU overhead. I've been leaving Vsync on auto also, the overall performance is good enough that I no longer have to worry about locking fps.

Probably doable via Varjo's system button but the question is whether they'll put an effort into this. Currently you can click the system button and then workspace icon to switch to desktop from within the headset, but have to manually switch Vsync off using VB (which is a quick mouse click btw). They can easily add a button or half a dozen more to the headset pop up windows. If they plan to no longer rely on Steam then this would be the way to go and I would prefer doing adjustment and setting via the headset popup layer, it seems more efficient this way.

For up close dogfighting 90 fps with no reprojection is always going to be better, you don't have increased latency and image retention from reprojection. But for everything else, including BVR combat, it's very good.

You should check it out. I was skeptical also, but not any more with the current beta and the latest MS implementation.

Posting again to endorse Varjo's latest motion smoothing with the new DCS mt build after flying for hours and hours today They're basically a perfect match. So far I've had zero hitch with complex missions or maps that typically would cause stuttering/tearing with my setup. There's some night lighting issue with the current DCS beta but it's not a deal breaker. This is the best that I've seen from DCS VR since the era of the original HTC Vive/Oculus Rift CV1 both in how it looks and how smooth it runs (on a good CPU/GPU setup). There's nothing out there right now that approaches the overall image fidelity of the Aero (maybe Pimax Crystal if that ever comes out), and when you add post processing via OXRTK, and smooth flying to that it turns into a near perfect VR flying experience.

Try this simple settings first. Should give you 90 fps in simple single player missions. 1. Install mbucchia's quadview disable wrapper. Releases · mbucchia/OpenXR-InstanceExtensionsWrapper (github.com) 2. Varjo Aero: Very High setting (37 PPD on VB), V Sync disabled, OpenVR on, OpenXR on. 3. DCS: choose VR preset. When you're more comfortable you can start messing around with other settings in both VB and DCS. I recommend high textures, waters, shadows, MSAA2x. I haven't done a lot of testings with motion smoothing as it costs more performance and it might be more suitable for slower games such as MSFS. If you fly slow aircrafts such as helos in DCS, motion smoothing is not really needed as there's barely any stuttering or tearing at low speed especially with OpenXR mode. I do think that motion smoothing makes more sense now with multi-thread support. So if you want to try it I would suggest Vsync Fixed 45 fps and Always enabled MS. There should be minimal artifacts with MS with the latest VB update. EDIT: I've gone through multiple training missions for Hornet, Viper, Apache using motion smoothing at fixed 45 fps (High DCS Preset without SSAO/SSLR to push the limit, plus +230 MHZ GPU OC and DOCP mode for my 5800X3D). It seems to work really well with no performance drop below 45 fps and I quite like it (motion smoothing). Haven't tried dogfighting/ACM yet but for that type of thing I'd probably prefer reduced graphics setting at constant or near 90 fps.

Actually, when I first got the Aero which was around a year ago it wasn't like this. There was no need for command line to run DCS as the default output was simply Steam OpenVR. You just click on DCS app and SteamVR would start followed by DCS, and things would work normally (although people were complaining about geometric distortion which is no longer an issue). It wasn't until the 1st or 2nd VB update that they started using Varjo openVR with quad view in mirror screen as a default output. Now I'm hoping that OpenXR stays as the default output at least for the mt build because now you can run DCS without using shortcuts or command lines again. From the consumer's perspective, this is the way to do it, keep it simple.

For mt build currently no as it would freeze (at least on my setup), for the old st build yes. Without the wrapper you would have to use Steam OpenXR to get stereo view, although the mt version has better performance in quad view now…but you’ll still see double cursor in the cockpit view which can be aggravating.

Ok it looks like DCS MT's default output is OpenXR instead of OpenVR. Which means Varjo users no longer need to run command line to use OpenXR. You can run the DCS app directly without any command lines or mods (except mbucchia's Quadview disable wrapper for Varjo OpenXR mode. For Steam OpenXR no mod needed, just enable Steam as OpenXR runtime in SteamVR setting). This is very nice, getting closer to plug and play. It also seems OXRTK underestimated CPU frametime compared to fpsVR in my testing. In F-16 Caucasus FF mission, my fps was in mid to high 80s from both OXRTK and fpsVR, and this was also confirmed by DCS's own fps tracker. CPU FT reported by OXRTK was 7-8 ms while GPU FT was 9-10 ms, these numbers if true should give me >90 fps since both numbers are below 11 ms. fpsVR on the other hand reported similar GPU FT but CPU FT was over 11 ms, which translates to final fps below 90 fps--hence appears better correlated. Perhaps OXRTK CPU FT does not reflect the overall CPU FT but only within DCS app?

Second this. And also make OpenXR the default output so there's no need to use command lines. OpenVR API is no longer the favorite so it should not be the default output for DCS.

Tried the F16 Syria Free flight, 90 fps smooth even when flying above the populated areas. I'm testing with standard VR preset, Higher Varjo res setting but Steam 80% rendering (3228 horizontal pixels). This is a definite improvement from before. There seems to be discrepancies in frametime report between OXTRK and fpsVR, fpsVR reports higher FT in general (1-1.5 ms in CPU and 0.5 ms in GPU) so I'm not sure which one is more accurate but sticking with fpsVR my recorded GPU frametime from this mission is typically between 9-10 ms and CPU 4.5-5.5 ms).

I no longer have the VP2 (sold mine), but if Varjo can fix the stuttering issue with the rtx 40series so can Vive which is a bigger company. With the DCS MT version, being CPU bound becomes less of a problem and now it's mostly GPU that will dictate your final fps. Now that DCS outputs OpenXR natively, it should work with VP2 (or any SteamVR HMD) via Steam. I'm running OpenXR via Steam right now with the Aero.

I only see this with Steam OpenXR + OXRTK (in my case, it was the Turbo mode on OXRTK that was causing this). No frametime spikes with Steam OpenVR mode. You can either disable OXRTK or do a setting reset to get rid of the spikes. EDIT: having freezing issue with OpenVR mode with mt version. OpenXR is the only API that is currently trouble free for me.

DCS MT seems much better than the ST version in complex missions and MP. I longer see framerate drops in areas that typically causes CPU FT spikes (e.g. Apache Mariana hot start, flying around the carrier full of planes on deck NW of the airport, Hornet supercarrier operations, etc.). It doesn't really increase my max fps as I'm still mostly GPU bound with my setup, but the min fps goes up significantly, it feels like getting a brand new CPU that's 2-3 gen ahead.

Don, try to reinstall the wrapper again. After the firmware update the wrapper needs to be reinstalled or it might not work properly. If that still doesn't work then reset Varjo Aero to factory setting.

The easiest way to test is Quad mode because you can just run straight from the windows menu without any add-on command line. Of course you'll see double cursor in the cockpit and mediocre performance but it's the quickest way to test if things are working.

Just follow my guide in the 1st post. Of course you need to make a new shortcut for the DCS MT because the new app is now in the bin-MT rather than bin folder. Also disable OXTRK for now to make sure everything works before reenabling it. I'm currently using Steam OpenXR but I have tested all the runnable routes and everything is working as expected.

I just did some test runs on all the options with DCS MT (Varjo OpenVR Quadview, Steam OpenVR, Steam OpenXR, Varjo OpenXR), and the only issue I had was significant CPU and GPU frametime spikes at regular intervals with Steam OpenXR mode. This was traced to OXRTK, and the problem is gone after doing OXRTK reset in safe mode with CTRL F1 F2 F3. Aside from that temporary issue, everything is working the way it did before. No significant changes seen in SP missions in terms of performance, haven't tried MP yet. Funny thing coming straight from PSVR2 headset is that now I'm starting to see mura on the Aero, although it's very minimal compared to that headset.

Check the very first post of this thread for various ways to run DCS, note that I haven’t had a chance to play with the newest beta yet so can’t comment on the mt.

I haven’t done any testing but personally find it hard to believe that CPU frametime would be in 2-3ms range with this update.

SSAA is supersampling of the entire scene, costs a lot of performance. Not sure this works in VR as we already have supersamplings via pixel density, Steam, OpenXR, etc. MSAA (multisampling) is more economical vs supersampling and tends to work slightly better for edge smoothing. SSLR, I think, is the same as SSR (screen space reflection) which improves/creates reflections of objects on ground/water surfaces but only in the area that you're looking at. I get better water reflections in VR if water setting is high, but currently I'm using both water high and SSLR. Not sure how well SSLR works in VR.