edmuss

Headset slaved vr mouse should be perfectly accurate. Bind the mouse buttons and wheel to hotas controls in DCS (modifiers are super handy for this) and ensure that use VR mouse is enabled. You can use joystick gremlin to bind mouse movement to a slew stick or hat switch.

I think most people don't use the controllers, they either bind mouse controls to hotas with the cursor slaved to the headset or use leap motion/pointctrl to manipulate controls. Push comes to shove you could use the mouse

The CPU thermally throttles above 77°C which reduces the clock speeds. Less voltage = less heat = consistently high clock speeds. Because it's not overclocking you don't need the extra voltage to help the silicone run at the higher frequencies. A lot of modern hardware has the voltages set artificially high to ensure maximum stability across the massive range of system configurations they're likely to be in. Basically by undervolting you're finding the lower limits that still retain stability with your machine; to some extents the silicone lottery still exists.

Possibly use shift+Y to focus control to the headset and use ESC? I'm not entirely sure

I can't adjust anything via bios on my B450M, setting a windows task to run on boot to undervolt via pbo2tuner works fine though.

I run mine with a 25mv undervolt in all cores via PBO 2 tuner and it sits at 75°C on a cinebenchR23 run, all cores pegged to 4.45ghz which is the most it gets to. I tried -30 but it gets unstable, as it is the core voltage never goes much above 1.2v and the normal max is 1.35v I think. In DCS it sits between 55°C and 70°C with the average at about 62°C

No

Ah I didn't realise that one It's possible that it might be incorporated into the GPU frametime?

It might be worthwhile adding the sclGPU (I think it is) values on there, this emcompasses the overheads associated with upscaling; the higher the resolution the more overhead you need. I've seen typically values between 0.8 and 1.5ms additional computational time.

That's not openxr, simply VR below refresh rate, nothing you can do about it. If you want perfectly smooth without reprojection then you have to get your fps above the headset refresh rate. The is no other way about it. The 5800x3D has lifted the framerates significantly but still not enough to beat refresh. You could shoot for setting the headset to 60hz and reduce some settings to keep your framerates above 60 or you could leave it at 90hz and embrace the stutter. Note that at a locked framerate, the stutters can appear to be reduced, around 56fps is about as good as it gets from my testing. Adjust the framerate throttle in the toolkit whilst flying along and looking sideways and find the sweet spot for you.

Add a (larger) deadzone to your joystick or enable the option for the hands to use joystick. By default any control input on the stick will hide the right hand, this can include if it's registering an impercetible amount; setting a deadzone can help alleviate this. If you enable the option for hands to control joystick then if the leap hand is moved to the right place (virtually) then it will snap onto the virtual stick and you can then move the stick/axis with the leap alone. Only problem with this is if the physical and virtual sticks are in the same place then you can get dual axis inputs being sent to the sim, however this does eliminate the control input hiding the right hand.

If you use the openxr toolkit screenshot function then it will show the performance overlay and the in-game toolkit menus as well. It could just be I have better thermals so I get consistently higher boost clocks on both CPU and GPU. The increased VRAM usage on my system could possibly be due to nvcpl settings, I think mine are actually completely default at the moment. I'm on standalone latest open beta. I do have Taz's improved trees mod installed for Caucasus, Syria and Marianas, it's possible that they absorb a bit more VRAM. I also have process lasso which forces DCS onto the fastest core and memcleaner keeps the ram usage down. Neither of these should significantly affect FPS though. Run gpuZ and log the sensors whilst you're flying, make note of the GPU core clock, temperatures and perfcap reason. Similarly log the CPU clock speeds and temperatures with hwinfo or similar. It might be you're simply not running at such high frequencies.

Some of them were on my suggestion, the terrain shadows off is because they're unfortunately currently broken so cockpit shadow can be increased with the headroom gained. I've never run cockpit illumination either so that's just my default setting, I've never seen any difference between on and off (that's not to say there isn't some though!). Cockpit screens at 1024 are a little crisper but I've noticed a fairly significant hit with 1024, 512 is an acceptable compromise for now

The settings are greyed out because I'm in the cockpit, you can't alter those settings with the sim running. Preload radius of 100 because there's little need to preload things now with SSD transfer speeds, I've never seen any negative from running low preload but it reduces mission load times slightly. For reference, the 3090 should be about 5% faster than the 3080ti but that could well be negated by GPU tuning. My gpu core clock speed is aroun 2050mhz with DCS running, if your GPU is only boosting to say 1800mhz then that will be a fair defecit. The same settings below on syria in the huey, 8.9ms is 112fps

In the A10C (don't have the A) I'm getting just shy of 60fps with the mission setup you suggested (cold and dark on ramp 1 at Antonio B. Won Pat Intl). But Marianas is a dog for performance so I would reduce some settings accordingly

Can only really compare if you are using the A10 as that is the only fixed wing module I currently own. Resolution can be set either on the desktop app or overridden in the toolkit, makes no difference in the end but can affect how different apps behave. It's better to set the override in the toolkit. If you're running the headset at 90hz then anything below 90fps will result in stuttering, particularly down low. The reason I run 60hz is that above 60fps it's perfectly smooth because I'm beating refresh rate. As long as I'm above 60fps I don't care what performance I'm getting, however I aim for about 13ms typical appGPU frametime because that generally gives enough headroom to keep it above 60fps (<16.6ms). Note that this is SP only so I'm not considering the performance lost by connecting to a server and the CPU getting dragged into oblivion by AI scripts.

Because I've done all of the tuning and the system is set up and running very well.... 100% resolution for the G2 is 3160 so 2700 is about 85%. It gains a ms or so back for absolutely minimal loss of clarity as long as you have MSAA enabled to smooth the edges.

I have one of the old welders vices from work, it's a record and so incredibly heavy and overbuilt, got to be about 60kg! I'd ask around local engineering shops to see if they have any old vices spare, alternatively eBay for a ropey old one and spend some time cleaning it up

From what you're saying, you haven't done any system tuning or optimisation, all of the things mentioned already are part of this and you would be aware of them if you had done it. Without setting up the system properly it will perform suboptimally. DCS vr isn't plug and play. Read the guides and follow them along with the advice given here, observe what works and what doesn't. It's a very personal choice regarding the image in VR and there is no one answer or setup for everyone.

It's all about incremental gains, there is no one magic bullet but building up the performance 0.1ms at a time. My go to settings are effectively VR preset with high textures/water/shadows, MSAAx2, sliders up a little, AF bumped up to 8x or 16x and terrain shadows off (for now till the flat option ditches the soft edges and returns 2.7 performance). G2 at 2700 resolution, FFR quality/wide preset, I'll typically get 11.5-15ms depending on where I am flying. This is with all of the vr4dcs tuning applied, CPU undervolted, GPU undervolted and overclocked and all things running as they should.

All of the stuff in the VR4DCS guides is still pertinent. With your machine you should be able to run medium high settings at 70-80fps, whether you choose to run reprojection or not, 90hz or 60hz is a choice you have to make

That's likely your problems, there is a massive amount of bloat in windows alone. Read the guides and follow them to the letter

Have you tuned your system properly? Follow Thud's guides explicitly and to the letter, you should be getting more performance than you have.

I used closed cell foam, not sure what rubber it is but I would suspect it being EPDM. As long as it absorbs the IR light then it's good, you can also get light absorbing cloth that Dan@ultraleap recommended but as it was I had the foam in stock and it worked. Things like your clothing can cause interference as well although I generally find that none of the controls are directly above my legs.

Turned off MSAAx2 and set NVCP override at 4xAA and DCS is a shimmery mess again with no antialiasing, gain a couple of ms for not having to antialias anything, even driving the resolution up to full doesn't result is a reduction of shimmer. I'll stick with MSAAx2 and simply reduce the resolution to keep the frametimes low, the shimmers eliminated and the image nice and smooth