Mr_sukebe

A few more things to try: Ensure that you're using OpenXR Disable the "home" for your Pico. If it's anything like the Oculus "home", it'll eat a couple of GB of VRAM before you're even opened DCS Run a search for Empty VR Hangar. When you first load into DCS in VR, you'll normally be sat next to a jet. Again, that eats VRAM and adds no real value. The Empty VR hangar replaces that initial view with zilch Textures do tend to eat lots of VRAM. Another that I found was the Preload Radius. Mine is now set to around 45%. Give that a try When you're in game, open the DCS FPS counter. Open that twice and you get both the FPS count (small box) and a bigger box with more detail in it. That now displays both the USED and RESERVED VRAM usage and is worth taking a scan at. The most I've seen USED is up to around 12GB on loading a complex mission in the Chinook. In most scenarios (single player) I'm typically using sub 6GB, which "should" fit into your GPU Go checkout the DLSS4 threads. DLSS4 introduced an update to the upscaling and AA that is available to all RTX cards, including your 30 series. There's a need to use an App (free to download) called NVPI (Nvidia Profile Inspector), but it's like Nvidia really has applied some magic to the results. Use the latest DLSS profile and there's a definite improvement in frame rate/visuals IMO, VR in DCS has improved in the last few months, but that's partly a result of the above settings

The RAF versions…

All of them...

Another idea to try is lowering the polling rate on your mouse, as suggested recently by Spud. The default polling rate for my Logitech 502 was 1000 (per second). I dropped it to 125 and it did eliminate micro-stutters.

The Canberra would be a great addition, if for no other reason than the number of countries that flew it and the number of conflicts that it was involved with

Of course it might actually be useful if we had Korea as a map.

Go into the audio settings within DCS. There's a bunch of drop down options on what to output to. This overrides what's set by windows, so it needs to be done here too.

Agreed, it would be great to understand what feedback is received in real aircraft. The force comments are really useful, but what about other potentials, eg does speed influence weight (as it does in a warbird), lowering flaps, speedbrakes, wind gusts, dropping ordinance etc. There’s a mass of external factors that might in reality produce feedback in the sticks. Probably far less in a FBW fighter, but what about say a Phantom, Mirage F1?

Of course it depends on the aircraft and terrain, which is why I mentioned examples above. Just checked out Afganistan with the Chinook. Whilst jumping into the cockpit cold and dark, VRAM usage (not reserved) was over 11GB. It then dropped to sub 7GB whilst airbourne. That's with High textures for both terrain and the aircraft, and ultra settings on the clouds. Another point that most certainly DID help was to follow up on a suggestion mentioned by Spud today, i.e. the lower the polling rate on my Logitech mouse. I vaguely seem to remember doing that back on Windows 10. With the move to Win 11, didn't bother. Either way, dropped the polling rate to 125 and wow, it really did smooth things out and reduce micro-stutter.

Try using in game FPS counter within DCS. I think it’s Right Cntrl and Pause. Hit that twice and it displays a more complex summary of what’s going on. Towards the bottom of that rectangle of data, it now shows not only the VRAM reserved by DCS, but also how much is really being used. In the mission today, DCS had reserved 15.3GB, but was using under 5GB. What I don’t understand is why DCS is not making use of more of reserved VRAM?

I was out earlier in an F16 over Afghanistan. VRAM use sub 5GB. No one else wondering about this? What did occur was whether ED has reduced actual VRAM usage, meaning that DCS would need to more regularly load and unpack new textures. Could that be why we might have good FPS, that is not really smooth in delivery?

Have you enabled eye tracking in the headset itself? I vaguely seem to remember that you need to be in developer mode to be able to change the setting.

The older ones have just worn out the wiper blades. Maybe some of the new Bosch aero type will help?

I had a Pico 4, but was so unimpressed that I gave it back. Being fair, that was mainly about my inability to get it linked up, I thought the image quality was fine. On the QP: - Eye tracking on the QP does help performance. - I found the comfort to be poor as stock. It added velcro bands to mine which were very cheap resolved the issue - I honestly can’t remember if the QP has better visuals, both are good - clearly I found the Oculus software easier to deal with

From a WW2 perspective: Just looking at that map, phase 3 looks like it'll include Arnhem and Nijmegen. Also has enough on the western side to include Boddenplatte, the bulge etc, with us able to use allied bases in northern France. Plenty of cities in the middle to conduct bomber intercepts. We'll finally have a genuine location to use the K4 and D9 Awesome stuff.

Doesn’t seem to be an outrageous price, which is good. The real question will be how it compares from a quality perspective to other existing solutions. For example, does the build lock the components in place? If not, is there a degree of wobble on each component. That would annoy me

Do you mean in DCS, or reality? My assumption is that it would be faster on the ground, as it's a safer environment to conduct fueling. It's worth remembering that drogue and probe is (as I understand it), significantly slower than boom, as used by Air Force aircraft.

It's well deserved. Please pass my thanks along the your whole team. As an ex-programmer, it's rare that we get thanked, so it's nice to return the compliment when the opportunity arises.

I believe that someone tested the Beta of 1.1.1.36 and was still getting Ghost presses, at least that was the comment on their Discord.

The benchmarks I saw yesterday showed the 9950x3d not having any real benefit within gaming. That "might" be slightly different within DCS, not with DCS running on the primary CCD, but with the number of other background Apps that some of us use (e.g. Simshaker, Discord, SRS etc).

No mention of a fix for Virpil Alpha "ghost" button presses.

Interesting. I wonder which one is correct? Maybe neither are.

+1. One of my favourite modules. Very "hands on". The most amusing thing being that I still can't hit anything.

Thanks, not just me taken by surprise.

Have you tried the updated options in DLSS, eg preset K? if not, there’s a thread on how to configure it.