edmuss

Either use the performance overlay in openxr for WMR or the overlay in the toolkit (or both if you so desire). The toolkit does performance logging now though so you can more reliably benchmark

Reshade doesn't work with openxr, that could well be your issue.

No, the panel resolution is 2160 per eye, the render resolution to account for lense distortion is closer to 3200 wide (2160x1.477), set the render resolution to 2160 wide and it looks terrible. Don't ask why the render resolution on the G2 was far higher than it was on the G1 when they both use 2160 panels but the resolution when set by steam supersampling and openxr resolution overrides at 100% has been confirmed by HP tech to be correct at 3100ish wide.

I went from 3600 with a solid 4.3 all core overclock to the 5800x3D and instantly saw uplifts of 25-30% in free flight missions, CPU heavy scenarios are night and day different.

I would hazard a guess that TM use the same assembly design for all of their 4 way switches.

I think there was a rumour of a 5600x3D but I could have been imagining it

In a nutshell yes, given that the DCS doesn't drag to a crawl, which will inevitably happen at some point. I'm not there with the ram capacity or speed, nor the GPU speed but my settings are as below. If I run without reprojection I can hold above 60fps pretty much all the time, generally it's at the 12-13ms frametimes which is 75-85 fps, with the G2 @ 60Hz I'm above refresh rate most of the time and it's perfectly smooth and artifact free. In order to achieve this consistently I do have to reduce the resolution to around 2600 - 2800 wide in openxr toolkit. If I run with reprojection I can run the same settings but with terrain shadows on default and increase the resolution up to 3100, it still generally keeps in the 45Hz reprojection bracket but will drop down to 30Hz on busier bits like flying over Beirut. The only openxr toolkit performance settings I use are FFR on the quality/wide (the slowest and best looking) preset. All of the above is based on SP only, discounting the whim of whichever server or mission is running

I'd keep an eye on ocuk, they'll likely have them in as soon as anyone else Yeah, being in the UK sort of sucks with the current brexit/tory/recessi on/cost of living BS edit: there are many place much worse off than us though!

From how I see it, the 5800x3D works very well in DCS (and other heavily CPU dependant titles) despite having a signifcantly lower clock speed than it's intel competitors. The 5800x3D was basically a tech demo to prove that monster L3 works (for a specific usage case), the 7xxx have hugely upped the clock speeds over 5xxx and there is promise of x3D chips on the near horizon (I have read November?). The 12700k is coming up to a year old and is shortly to be superceded by 13th gen, you could always upgrade the 12700k to a 13700k or similar later down the line. Given AMDs track record with socket type longevity (AM4 was launched 6 years ago now and is still in use) for future proofing it would make sense to switch to AM5 and a 7xxx CPU; hopefully the support for AM5 lasts as long as AM4 did - given that AM4 was DDR4 and AM5 is DDR5 I would suspect that it will do. Historically, intels CPUs are released on a tick/tock cycle, every tick release is a generally on a smaller process with a jump in performance and every tock is then a die shrink for efficiency and power with less of a jump. Both the 12th (tick) and 13th (tock) are on the LGA1700 socket and I would hazard a guess that 14th gen will be a new socket entirely again - the future proofing is nothing on the AM4 socket lifecycle. I would still stand by the 7600x/7800x route for now and slot an x3D in later if you're struggling to feed the GPU

Well if you're building a new system with a 12700k then I guess you'd need new motherboard anyway and the only thing you'd be able to carry over would be the ram. The 7600x is 300, the 12700 is 350 and slower, the 5800x3D is 440. edit: I put the 5800x3D in because it's going to extend the life of my current build for a good few years yet and I was fortunate to be able to make the upgrade and not be massively out of pocket; if you have AM4 already (and not a 5800x/5900x) then go for it.

In a new build, no. Personally I'd use a 7xxx with DDR5 and upgrade the CPU to an x3D at a later date if they prove to be as transformative for DCS as the 5800x3D has proven to be. If you're already on AM4 and not intending to upgrade board and ram for the foreseeable future (your CPU turn around time) then I'd say yes.

What you want is Arma Not so much the fast movers (although they are in there) but the integration with infantry and helos is really good and the shiny graphics are shiny enough for FPS use. The sim level of the flight element isn't a patch on DCS with regards to the systems (I think the helo flight modelling is fairly decent), but it is an infantry simulator first and foremost; that said it does blow ghost recon out of the water in all aspects - it's not an arcadey game.

Admittedly I've only done a couple of quick tests but it should be an accurate measure of vram usage by DCS compare to task manager The vram value in the stats file isn't total vram usage, just for the app that's running.

I had seen that, @speed-of-heat can regain his queen of benchmarking crown again Holy crap, I've just looked at some of mine, it logs the vram usage; my highest so far is 9.7gb - this might put to bed the wild estimations of how much vram is actually being used (not allocated).

I replaced my pinky switch a couple of months back, it was a couple of quid from RS here in the UK. Super simple job of solder it in and it's perfect Can't help on the mic switch though, sorry!

No need for steam at all, openxr for WMR is on the MS store, open composite and openxr toolkit are on GitHub.

Looks like sheets of water running over the screen, you'll know if you see it!

As a test, try turning on the sunglasses post processing filter in the toolkit, it quells some of the 60Hz flicker. As long as you've updated the openxr for WMR (search for it on the MS store and got the update button) and the toolkit then it should all be good. Make sure that motion compensation is set to zero in the toolkit, that can cause the waterboarding effect. Helo rotors are still a bit wonky but it's getting better all the time.

Yeah openxr is much smoother than steamvr without reprojection but you still need to keep the frametimes low, it certainly isn't smooth at 30fps without reprojection! The most recent runtimes have improved the reprojection, specifically the performance tanking to 15fps and whilst the artifacts are still worse than steamvr it's much smoother at framerates <50. 60Hz without reprojection is where it's at

Interesting that it's set as an option in the AMD driver itself, @Sandman1330 it would be worth trying to find it and check the status, the blue screen crashes for me happened with HAGS on.

Ah it appears to be driver dependant, AMD simply don't enable it; probably for the best, some problems it fixes, some it causes It could be as silly as your motherboard not being able to supply enough power to the USB circuitry, whether that be through hardware degredation, USB saturation or PSU breakdown. Of course it could just be bad luck with the cable but I think cable errors typically show up with an error code in WMRP rather than a hard crash. I started getting 7-13 errors with mine, had 2 weeks of warranty left so HP sent out a V2 cable which didn't help so they replaced the headset and it's been fine since (I now have both cables so can always go back to the V1 cable in case of an emergency). I tried a powered pciE USB expansion card and it made no difference in my instance because the headset was dead in the water - didn't even have the HP logo light up! I have had similar crashes to what you describe, however it was pretty rare. It would be interesting to see if the USB power states and WMR sleep settings make any difference.

HAGS is in start>settings>system>display>graphics settings. As far as I'm aware it's hardware independant (at least on modern GPUs, I don't think it's an nvidia only thing. Fingers crossed, windows does have a nasty habit of changing settings when it updates!

Check the headset is set to not sleep and that HAGS is turned off. Motherboard definitely supplying enough power for it? Have you tested on a seperately powered pciE USB expansion card?

The second tab of the openxr tools desktop app will show the current resolution that the headset it running at, alternatively you've overridden the resolution in-game using the toolkit then it will stat what resolution it's set to (rather than a percentage). My preference is to leave the desktop app resolution at default and override it with the toolkit.

From the very start of @nikoel monster thread on running openxr... Pimax is slightly different implementation from WMR but from what I understand it should all work the same. I see a consistent 10fps or so improvement switching from steamvr to openxr, this is for identical resolutions and settings. Clarity is better with openxr and there are a whole host of advantages both from the runtime and conferred through openxr toolkit. Because of the way that openxr renders the frames it's much smoother than steamvr, particularly when reprojection isn't used. With reprojection enabled it grants you the ability to reproject at multiple fractions of the refresh rate rather than just half as steamvr does, this means you can still be achieving perfectly smooth, stutter free VR ar 30 fps. The reprojection isn't quite as good as steamvr with regards to the artifacts but it's getting better all the time.