gwizdek

Sorry, you are imagining things or didn't pay attention earlier, or had strange reprojection settings. SteamVR: set your Index to 90Hz, 100% global resolution, 100% per app resolution. Disable motion smoothing (reprojection). DCS: disable antialiasing and DLSS. Adjust sharpness slider to yout liking. Verify that you have Pixel Density set to 1.0 on VR tab. Check your FPS. You should get 90 frames per second on 4090 easily. Increase SteamVR per app resolution for some supersampling. You could also: add your DCS instalation folder/Saved Games/DCS folder to exceptions in antivirus software. check Windows HAGS (on or off) - restart Windows after each change. run with OpenXR API via DCS MT (this should be default by now) Always try to match your game FPS with your HMD refresh rate (with some headroom). Using motion reprojection makes the image less sharp than without it. When your HMD is set to 90Hz, for the MR to work fine, you should be rendering at about 60FPS (you need some margin above 45FPS). Edit: Don't try to run DCS at 144Hz as it's simply to taxing for the CPU. If you can get DCS to run at 90HZ/FPS, that will be perfectly smooth. Also try 80Hz if needed.

I think it's coming in the next video where he's going to compare Q3 with PCVR headsets.

Agreed. Rivatuner does better job than Toolkit in my experience with G2. Set HMD to 90Hz and cap frames to 45 which is 1/2 refresh rate. You will see double image while translating left/right in cockpit and looking to the sides on fast moving objects on the ground, but frames will be delivered consistently. This option is less demanding on gpu than reprojection as for reprojection to work you would need to be able to render about 60fps normally. If you can maintain 60fps, for smooth experience you can either: - run in 60Hz mode with panel flicker - run with reprojection , but you will loose some image sharpness (if you are after max sharpness don't use reprojection in general)

I want to know the difference between runtimes (Varjo Base vs WMR), without eye tracking obviously as DCS is just one of few games that make use of it atm.

Can you compare performance between G2 and Aero with the same megapixels per eye res., like 15MP per eye? With the same DCS/OXRTK settings of course.

There is a new version of OpenComposite made for SkyrimVR that has sticks deadzone adjustment and laser pointer orientation fix. Maybe it could help if you're still on OpenComposite. https://www.nexusmods.com/skyrimspecialedition/mods/85389

Why 55 and not 90 / 2 = 45? Is this driver version any better than the other versions?

Ever since ED changed VR subforum location, I keep forgetting where it is. I don't get how it ended up under General Off-Topic Discussion, when 95% of the topics here are in context to DCS World. If we can navigate to VR Bugs, which is a subforum of this forum, straight from DCS World 2.8, then the VR subforum should be there too, just under Multi-display Support. VR is more of a output device for us than an input device anyway.

Exactly. Ideally for VR we would want to specify rings of DLSS modes: - 25% ring - no DLSS - 50% ring DLSS quality - 70% ring DLSS performance it's probably not feasible though.

I don't know if it still works. Tried once without success about 2 weeks ago, but I was on MT version and my wingman was on ST, so it could have impacted. There was/still is? an issue with buddylasing in general with MT

This might help you: Adding maxfps to autoexec.cfg (like below) strangely dosen't do anything for me options.graphics.maxfps = 45

Looks like it's disabled in Config\graphics.lua --in stereo and hmd mode you can try to use single parser for both eyes , by default is false , comment to enable it or set to true stereo_mode_use_shared_parser = false

To add: I have noticed that after update mouse cursor has different sensitivity horizontally than vertically. Now it's 1:1 on my 3440x1440 monitor mirror (full screen enabled), but in HMD vertical axis is mouch more sensitive.

In VR you can see them from 40km as a shimmering black dots even through clouds (no, I don't have labels enabled). When you know where they are it's easy to point shkval at them. Maybe it's some kind of feature...

I also limit framerate to 45fps. It's never going to be as smooth as reaching 90fps or 60fps with 60Hz mode of G2, but I can't get even to 60fps with decent image quality, so I use 45fps limiter. I tried different ways to limit fps with varying results (described here)