edmuss

The spring on my original nub has died so wasn't recentring correctly. Ordered so looking forward to receiving and fitting

So before you set the resolution override to 2900 wide in game it will have been running at around 2600 which would explain your performance drop; you should be able to check the current render resolution on the second tab of the openxr tools desktop app The 3070 is faster than the 2080, it's within 1-2% of a 2080ti so I would expect your GPU to be happier with slightly lower resolutions, fortunately openxr seems to downscale pretty well.

Had you previously set a resolution override using the openxr tools desktop app or is it set to default resolution? The default resolution will calculate the recommended display resolution for you based on how much VRAM your GPU has (the calculation is based on the three render buffers with 4xMSAA applied shouldn't exceed 10% of VRAM available). For my 8GB 3070, by default it sets it to around 2600 wide; I prefer to run slightly higher resolution rather than use MSAA as it improves the clarity of the image (I find MSAA makes it a bit blurry in the cockpit). If you had it set to default before and that was calculated to a number lower than 2900 then your performance will obviously suffer if you override it to the higher amount. It sounds as though you're running low on VRAM (DCS appears to not release VRAM properly and causes massive performance loss), try reducing texture and shadow settings to see if it alleviates the issue.

Also, if DCS is running in the headset and steamvr isn't running then yes, open composite is working

Yes, use the system tab of the openxr toolkit ingame menu and use the resolution override (needs a restart of DCS).

Switch to openxr and with a well tuned rig you should be able to get better framerates at higher resolution and settings. My 3070 is slower with less VRAM and running the G2 at 2900 wide (about 85-90%) and medium high DCS settings I can still generally pull 60-70 fps. This is without motion reprojection but openxr is far smoother all round so it's possible to play at 45-50fps without too much hassle

You can undervolt the 5800X3D using the tools linked to above, mine runs quite happily with -25 on all cores, it doesn't play ball with -30 and I've not taken time to go through each core one by one to find the lowest level yet. I'd disagree about the cooling, with the undervolt my 140mm single fan heatsink keeps it below 70 in DCS, yes in prime 95 it's going to get toasty but that's completely the wrong work load for it. edit: heres a quick screen grab from the start of a p95 blend run, yes the heat load at this point is low but it's sat at 50°C with 100% load. The temperature will ramp up later in the run. Ambient is currently 23°C. null

Yeah the mismatch in resolution is an odd one especially as I believe the G1 used 2160 as per the panels; but the 3176 @100% was confirmed by HP tech for the G2.

I'd try binding a different key combination and see if it's somehow linked?

Turns out that the task scheduler hadn't run and applied the undervolt, I have now triggered it to run every hour indefinitely Run a quick test on the syria A10 AG mission and the CPU has peaked at 68°C which is more like it.

Native display panel resolution on the G2 of 2160 wide, however you need to supersample the renderer image by a factor of about 1.47 (3176/2160) to account for lens distortion correction. Setting the G2 to 100% in any VR renderer will result in 3176 wide, anything less is undersampling it. When setting default resolution in OXRDT (where is bases it on your VRAM capacity) it worked out that for my 8gb to use 2600 or there about which was a little above 60% according to the slider/reported resolution in openxr. To me, setting the G2 to 2160 wide looks terrible, using the maths above it's an apparant resolution after distortion correction of about 1470 wide. On a bit of a U-turn I'm currently running 2800 wide which is about 88% of 3176 and FSR at 85% with no sharpening. Not sure if a recent OXRTK has cleaned up the FSR crawling ants and shimmer but it seems much cleaner than it was.

Ah yes I've already done that one, got it set up on task scheduler but not checked to see if it's actually run each time

An old thermal right true spirit 140bw that I hacked the mounting plate to fit the am4 socket I don't have a case as such, the motherboard is mounted to an old case back tray that I cut up and screwed to the wall to save space.

I believe the main advantage of the stereo 170 it's that it's got a larger tracking envelope but the software and setup is identical. Did the leap work ok in the visualiser? If it's working and configured correctly in the visualiser then it should work fine in DCS.

Regarding temperatures mine idles at 33 and normally peaks around 70 in DCS although this last couple of nights it's been shooting up to 80 but then the ambient has been 32+. It's hotter than the 3600 @4.3 GHz but much, much more power. Hopefully AMD will allow future bios updates to be able to reduce vcore and better control thermals.

0.6.3 has been deprecated for over a month, the main openxr thread has full set of step by step instructions and has done since Jabbahs development was merged with open composite and the global switcher was released

Just dug out my explorer and plugged it in, running DCS at 100% resolution for the headset (1400x1400 per eye) I'm getting a little over 9ms, with the reverb at 90% (2900x2900ish per eye - my normal resolution) I get around 13ms. Image wise, the reverb has much less godrays and the screen door effect is invisible in comparison to the explorer, however the image quality is DCS is actually pretty good and I could play it quite happily. The MFD text and guages are much more indistinct though but this is a limitation of the much lower resolution, adding some sharpening might help a little. At the explorer resolution (1400x1400) vs the reverb at the equivalent (1960x1960 - 1400x1400 x 1.4:1 ratio applied by the G2) the lenovo is much crisper. My money, having just tested the two side by side is with the lenovo. The lenovo is running 1 image pixel per display pixel, the reverb is running 0.6 image pixel per display pixel and that results in a fuzzy image. For a little over 100 of your kangaroo dollars I'd say it's worth a punt. Grab a VRcover face pad and you should be good to go https://www.ebay.com.au/itm/403733823423?hash=item5e00693fbf:g:A-EAAOSwV3FitCfA&frcectupt=true edit: agree with the above aswell, a minimum of 2080ti/3070 really for a G2 and that's needing to make visual compromises, however your CPU is then going to be a massive bottleneck. I would say you have a pretty balanced system for now, approach VR with a headset of the same era and capability to see if it's for you and then start saving for the big rig upgrade + big headset. edit again: I did test the reverb at full blown explorer resolution of 1400x1400 (not taking into acount the 1.4:1 pixel ratio that needs to be applied) and it was diabolical, completely unreadable text everywhere - think playing on a monitor at 320x240, it was that bad

You can use the global switcher to tell all VR apps to use either open composite or steamvr. If you're using an oculus headset then setting it to use the oculus runtimes will stop it using openxr. Alternatively you could just uninstall open composite.

Yeah a 1080 isn't going to be enough to run a reverb really. However a Lenovo explorer (wmr) or rift s (oculus) should work quite nicely and be a lot cheaper as an initial foray into VR. The Lenovo has better resolution and is supremely comfortable as it's very light but the rift has better tracking and controllers. I spent hundreds of hours in my explorer on elite dangerous and I still have it as a backup in case my reverb dies. I used it with a 1070 without any problems although I didn't fly a great deal of DCS with it, the image compared to the reverb is obviously worse but given my acquired knowledge now I reckon it could be pretty useable in DCS. I might dig it out to test in DCS with openxr and see how it compares

Unfortunately no, reprojection is still a bit flaky with the toolkit. Sometimes it seems to work ok and others it just spirals into a death dive and locks the framerate to 20fps.

For the budget a Reverb G2 as long as you have a reasonable GPU, run it with openxr (see the VR subforum) and are willing to spend a lot of time tweaking and configuring your system* What machine specs do you have? It can make or brake your VR experience. *this applies to DCS VR no matter the headset.

DCS vr is the only thing that knowingly stressed my 3600, the opportunity came up to grab the 5800X3D so I did so to alleviate the bottleneck and future proof some more. The 5800X3D has more than halved my CPU times (and in some instances quartered) for the same situation compared to me 3600 at pretty much the same clock speed. How that compares to a lower cache, higher clock speed Intel I don't know.

There is only one post regarding the setup for WMR headsets, it's Nikoel's, follow that and you will be fine

I think it's listed as something like AAP engage? I could be wrong, I can have a look later to confirm if you don't get it sorted edit: It's the LAAP commands, the default keyboard command is Q to engage and it should be in the HOTAS sub list of control bindings.