edmuss

Plug the headset in and confirm its working properly, then start adding layers

The pimax isn't a WMR headset so the normal openxr stuff won't work with it, @mbucchia has developed pimax XR here that should let you join in on the fun

You have updated to hotfix haven't you?

Reprojection appears to be working fine for me, still artifacting but in general it's not worse than before

Yup the hotfix to 112.2209.2003 from 112.2209.1004 does seem to have fixed the reprojection issue. No longer should the fps tank to 15 when vram usage is high

Can you clarify? Do you mean for the rotaries you use a seperate button box with physical controls? It's odd, I find some rotaries implementation much better than others, the KA50 I have no issues with them but the A10 it can be 30% success rate on activating the switch in the correct direction! One day!

I'd turn down visibility to medium and clouds down from ultra, also secondary shadows and cockpit global illumination, I think you might just be saturating your GPU.

To start with. Turn off upscaling, this will be hurting image quality, especially outside of the cockpit, I don't think you need to use it for performance purposes. You have it set to potato quality settings, I think this is the root of most of your problems! Unlock the reprojection, there's no need to do so and if your fps was to dip much below 50 then it will be disabling it all together. Turn off secondary shadows and cockpit illumination, run terrain shadows as flat or off, this should save a bunch of performance. Leave the rest as is and you should have a good baseline to test from. Enable the performance overlay from the from the openxr tools desktop app, this will give you all the information you need for basic troubleshooting/tuning. This will show up as a green/blue/red box in the upper left portion of the view. The main numbers you need to concern yourself with are appGPU and postGPU for now, these are the time taken for the GPU to render the frame and the time taken for the GPU to carry out post processing functions (this includes the overheads for reprojection). The Hz(fps) will show nominally as either 90, 45, 30 or 22, these are the refresh rate brackets that the reprojection runs at (1, 1/2, 1/3, 1/4); there will be minor varitations as and when it steps from one bracket to another. Go flying in your normal situations, make note of what the appGPU is as a rough average and it's nominal highs and lows; this will be the main focus for tuning your settings to achieve what you need. Roughly speaking, for 90Hz to keep in the 45Hz (1/2 refresh rate) reprojection bracket you want your appGPU to be less than around 20ms, if you're well below this then you have GPU overhead spare and you can turn up some settings. If you are over 20ms then you will be starting to drop down to the 30Hz (1/3 refresh rate) reprojection bracket; this isn't necessarily a bad thing though and is one of the massive advantages of openxr over steamvr (steamvr can't reproject below 45Hz). Try that lot out and see if there are any improvements and how the appGPU numbers are looking and then we can go from there

Ok so 60Hz is out, your best bet is to rely on running 90Hz and enable reprojection. The panel resolution of the G2 is 2160x2160, however to account for lens distortion the render frame needs to be 3160; this has been confirmed by HP technical as being correct. It's really confusing and would have been far easier to tell us it's rendering at 2160 rather than 2160x1.463... I'm on thuds discord, yell any time and I'll do my best

Shoot for 77% to start with, that's analogous to the old AMD FSR 1.0 ultra quality setting. It will always be better image quality without though. The upscaling is only really required if you're needing to improve performance. With the 6900xt you should be able to run 3160 without needing to upscale and still hold 45Hz reprojection (if running 90Hz) on or 60Hz if not relying on reprojection and able to run the G2 at 60Hz. Beating refresh rate will absolutely give you the clearest image quality, even if you need to drop resolution to achieve it consistently. 60Hz, 2480+MSAAx2 (+MFAA although you can't use it being Nvidia only) gives a better image quality for me then 3160 with better performance, it's all still perfectly readable as well.

The Gemini drivers released early this year made the tracking much more robust, the DCS implementation still has its foibles but it is getting better. The most important part is getting the environment optimally set up, before I did that it was frustration on confusion. Now the only time I can't use leap to activate cockpit controls is when they're physically occluded (think SAS controls to the left of the warthog throttle) or where the physical constraints of the environment prevent it; the walk in cupboard my rig is in means that quite a lot of the side controls aren't achievable because my hand hits the wall before I can reach the virtual switch. All in, because I only paid 30 quid for it on eBay it's one of the beat value investments I've made for DCS vr with regards to immersion

I click all of the cockpit controls with mine, leap motion is lovely once set up right

It should be automatic assuming you have use latest openxr preview enabled on the openxr tools desktop app (I think!). The current release is 111, it should be updated for 112 shortly hopefully

Although you don't get the physical feedback, you do get the precise visual feedback which in my opinion works really nicely now. Some switches are difficult to activate reliably (multi position rotaries can be awkward) but toggle and push buttons are a joy. Hand occlusion from desk/hotas/legs but this can usually be alleviated by leaning in towards the controls in question. Physical clashes are generally a function of making sure the desk is far enough away to be able to get UFC/MFD buttons. Adjusting the world scale can help a great deal here, as can leaning back, setting the vr centre and then setting normally. It's not for all, I took a punt and picked one up on eBay for 30 quid and it's been great

The next release of the openxr runtimes from Microsoft should fix the problem when running openxr. It's linked to DCS not leaving enough VRAM for reprojection to work. The new runtimes pre-allocate a block of VRAM specifically for the reprojection and this has fixed the issue for me entirely. I am running with a test dll from the devs to prove the function. When running reprojection I now no longer have performance tanks to 15fps on mission restarts or slot choices, neither does it randomly drop

I don't touch it at all outside of menus if I can help it, I use leap motion for 80% of the controls and headset slaved cursor with mouse buttons on the hotas for those controls I can't use the leap because of occlusion. Being able to click the mouse in the map and pan it around with the slaved cursor would work just fine for me. Interestingly enough on a different topic, I've been able to use the leap motion hands to manipulate the F2 view like a multi touch phone screen

It's all well and good but I don't think the bind for panning the map exists

I also have no single missions for A10C II, just the instant action ones. I only have Caucasus, Syria and Marianas and none of them come packaged with any SP missions for the module. There are a bunch for A10C that can be converted over.

Ideal use of the custom profiles, generally because I play SP I'll tune to the worst case scenario and then just have higher performance everywhere else

My point was that a CPU at 4.6ghz doesn't guarantee performance. My old 2500k @4.7ghz would have been annihilated by DCS VR. If I were to couple that i5 with a 3060 in the hope of running high resolution DCS VR I would be sorely disappointed. I would agree that if you have a weak CPU and/or a weak GPU then it's impossible to hold high framerates all the time in all modules.

Note that it's best to avoid upscaling between 80 and 130% as the computational overheads may outweigh the performance benefits. It sounds as though you're susceptible to the stuttering, I'd recommend using reprojection and see how you get on. Note that DCS is very aggressive with VRAM allocation and in some cases can prevent reprojection working properly due to lack of VRAM. Essentially unless you have bags of VRAM spare (a 3090 basically) it will occasionally tank to 15fps and be an absolute slideshow. The openxr toolkit dev has identified and eliminated the problem and it should hopefully be fixed with the next release of the openxr runtimes from Microsoft. If you do suffer from the performance tank, try to reduce VRAM hogs (high resolution, textures and MSAA), a temporary workaround is to alt tab out of DCS till the postGPU frametime settles and then it should be ok for a little while.

I meant how does it help the performance in DCS on the local machin? I'm nearly always GPU bound so for the most part surely it wouldn't make significant improvement to FPS but lift some of the load when ai gets active?

Those damn ladies!!

Ah so nothing too major needed if you have the ram available, would likely only use it for SP if it might make sufficient improvement. We're due to upgrade our CAD workstations at work and there will be a couple of 4770ks with 32gb ram and SSDs going spare Presume it doesn't benefit so much if GPU bound? I only have 32gb ram onboard so running another instance of DCS might chew up more than I want.

I've had that in the past it's normally to do with when openxr tools gets updated it leaves behind some registry keys that are linked to 3rd party apps like necksafer or openkneeboard. I can't for the life of me remember what the fix is but I'll look into it