slughead

It allows you to turn your hands into mice to point at cockpit controls and click without fumbling around for your normal mouse. It's currently on a 25% Christmas discount. Full details here:

Merry Christmas. Don’t forget to order a Slugmouse

Yup. See how you get along with that. If you're still struggling to stay at 72fps, drop it down to 1.2x. You won't be able to stay at 72fps in all scenarios, especially using MSAA. DLSS will give you a lot more headroom.

Good. So set it to 1.0 in OTT, leave it alone in the Meta Link and try that. Also, set it to 72Hz in Meta Link.

Oh ok. In that case, just set the PD in one place. 1.3x in your headset should be sufficient. Set the one in OTT to 1.0. But.... you still haven't shown your DCS PD setting.

NVidia settings make no difference in VR that I have seen. Also, you didn't show your DCS VR settings screen that shows the DCS PD.

You've got a render resolution of 1.3 in the headset - render resolution is the same as PD (pixel density). A PD of 1.2 in OTT. So that's 1.2 x 1.3 = 1.56 total. Multiply your headset's native resolution by 1.56, and you'll get a high overall render resolution, which is hard for any system. I think I saw you are using Quad Views as well. If so, set both headset PD to 1.0 and OTT to 1.0 and just set the PD in quad views. And lower your headset to 72Hz. You're expecting too much from DCS.

Ok. I think you'll find that if you have your DCS settings maxed out, no one is going to achieve 90fps all the time on DCS unless you're up high in clear skies. Typically, we set the headset to 72fps and can maintain that most of the time. I run a 14900k, 64GB DDR5 ram, nvme drives, 4090, Z790 chipset, Win 11 and a Quest Pro at 72Hz. Also, what is your PD setting in the game and the render resolution setting Mata Link?

I expect that isn't as demanding as DCS though. Are you using Oculus Tool Tray?

If you don't know... you've not done it I'm guessing. Are you using Meta Link or Virtual Desktop to connect the headset to the PC?

Compare it to other systems. I would expect there would be benchmark results from other users to compare against. Also, are you sure you haven't set ASW/SSW to always be on? If you have, that would fix your FPS to be half your headset FPS.

I don't have or use AMD systems. The default memory speed is often not the maximum and can lead to degradation of frame times. Have you run a Cinebench test to check your system is performing as it should?

Perhaps it's down to how your hardware is configured/assembled. 1. Check XMP is chosen for RAM speed. 2. Check your setup's cooling performance. Is it getting too hot and thermally throttling the CPU, causing it to run slower than you otherwise expect? 3. Does the PCIe bus gen speed match the 4090 card? I think it's 4.0 x 16.

Phew! What a month! I just managed to squeeze five orders out before Christmas. I will continue manufacturing units over Christmas and ship units between Christmas and New Year's. Have a great Christmas everyone!

Did you consider using the earbuds for the QPro?

I just tried the mic on my QP. Seems ok to me.

There's nothing else you can do other than covering the sensor with tape. The problem is within DCS itself.

Bypass Sensor - sadly, it doesn't stop it from sleeping for either headset. If you install the Quad Views Foveated Rendering tool, it fixes the sleep problem. You can use the QVFR tool without the QVFR functionality enabled and still benefit from the sleep fix. Alternatively, you can use Virtual Desktop instead of the Meta Link, which I think also fixes the problem, but I note you say it is not an option for you. Maybe if you expand on your reason, we can offer a solution. I can't speak for the microphone as I've never used it on my Quest Pro.

Yes, you can also use Slugmouse in that way.

That's where Slugmouse comes in. Use the Leap Motion Controller with HTCC to give you a hand-to-mouse cursor control and the Slugmouse to perform the mouse or joystick button clicks. It's currently on a 25% Christmas sale for £100 for a pair of Slugmice and case. More details here:

From the quad view foveated rendering instructions…

Yes, I’m sure I said that. Off topic so start a new thread if you want help on performance of your machine. Check you are running xmp profile for your RAM. Check you are not running intel defaults for CPU, check CPU is not thermal throttling.

I’m assuming you are using QVFR hence four resolutions are shown.

I think we are heading off topic now.

Neither is least taxing. The are combined to produce a single render resolution that the app draws its images at.