Qcumber

Some maps are better optimised than others. For example, the Normandy 2 map runs very well for me, similar to Caucasus. The Channel map, however, is a real performance hog, despite the same terrain. It might be the trees but I'm not sure. I tried reducing the tree quality and draw distance to minimum but it didn't make any difference for me. Over the large islands FPS is the worst. Over the sea it's great. I am hoping that Marianas will receive some performance improvements with the WW2 update.

If the FPS is below the refresh rate you will always get stutter. I would advise not attempting 90Hz and try for 72Hz. As ischicopter says, if you use ASW it is better to control this via meta. I use OTT to set keybinds for the various ASW settings.

I would advise starting simple. Set PD in game to 1. Turn of all AA settings. In oculus link set the scaling to x1 and 72 Hz. 90 Hz is too much. Use either oculus debug tool or oculus tray tool to supersample to about 1.5 and see how the resolution looks. As has been mentioned above you can use QVFR to reduce the peripheral resolution. Default settings should be ok to start with. Once you have a good balance between quality and performance you can start playing with sharpening and AA. I have a Quest Pro and a 4070 and get very crisp views in the spitfire N2 free flight alongside the B17 with steady 72 fps and about 70% GPU utilisation. You should be able to get the same.

The "./" one worked for me. When I tried before I couldn't get it to connect to the headset. Your instructions are very good so a lot easier. It took me less than 5 minutes to get up and running.

Got it working and eye tracking is definitely better. I am also getting 400mbps with a very smooth experience. One step I did not see on your list though is that I had to confirm connection on the headset before I could run the code.

I'm getting the same issue. The F5 has always run well on my system. One of the less demanding modules. Even the update ran well. Since the latest update I am getting very unstable frame times. I compared a run over the N2 map in the F5 with a p51. Both had similar CPU and GPU utilisation (about 65-70% for GPU). The p51 flight was very smooth. The F5 flight had lots of micro stutters.

I tried this a few weeks ago and could not get it to work. I might try again.

That's a shame but thanks for all your effort. DCS would be unplayable for me without QVFR.

Any news on QVFR being integrated into VD? If I remember correctly it was a possibility but there were some issues.

Spotting dots for VR and adaption for QVFR periphery. Fantastic.

It might be OK. It's a lot better than the rift s (88) and slightly less than the Quest Pro (106) or quest 3 (110) and similar to a Pico 4 (104). FOV on paper is not always a good indicator of real world use. It depends how close you can get your eyes to the lenses. Worth a watch and wait. I like that it is small (relatively) and lightweight. The bulk of the crystal line has always put me off. The Pico 4 is a great headset. Very light and comfortable with a good FOV with a third party face plate so the eye-lens distance is short. Just no eye tracking. Hopefully the dream air could be similar to this.

This looks like the one for me. Small form factor with eye tracking and DP. https://pimax.com/products/pimax-dream-air

I use the head pointer yellow cross with mouse enabled. I then map the HOTAS buttons to allow mouse centering and buttons to offset the centre left and right using JoyToKey. I have a "finger mouse" strapped to my joystick which I can use to left/right click and scroll without needing my hand to leave the stick.

The issue is running QVFR and dynamic/fixed foveated rendering in OXRTK. The advice from mbucchia is not to use both as they are both methods of foveated rendering.

I have not actually tried having both at the same time. I imagine it would create some issues.

Not that I am aware. I use JoyToKey to recentre the pointer.

Do you mean you have QVFR running at the same time as FFR in OXRTK? The QVFR guide notes advise against this. https://github.com/mbucchia/Quad-Views-Foveated/wiki#openxr-toolkit

I got my QP for £300 used but immaculate. You can get new ones on eBay for about £400-550. Last time I looked anyway, but that was a few months ago.

I have no issues with the headset going to sleep. I have QVFR installed as this was the main reason I got to QP. I don't use the microphone so couldn't comment. You can pick one up for the same price (or less) than a Q3 now. It is the only "budget" option for DFR now.

This one is good to see with a Lancaster and Mosquito restoration project. They both do regular taxi runs. You can pay a ridiculous amount to be on board whilst they are running too. https://www.lincsaviation.co.uk/gallery/videos/lancaster-taxy-ride--official-video.htm?gad_source=1&gclid=CjwKCAiAyJS7BhBiEiwAyS9uNXxSAoSTYIQHKbMes8u1l4k8fe8rpVw6nB5hqAKdDgCsZndGpC_GGRoCJPgQAvD_BwE Plus it's close to RAF Coningsby so loads of Eurofighter/Typhoons too. This one is great for cold war aircraft and you can sit in some of the cockpits. http://www.newarkairmuseum.org/

I would agree with that. Trying to run DCS with full settings and highest res needs an rtx 6090Ti super! With eye tracking you can get a massive boost and get reasonable performance on an rtx 4070.

Please could we have this map? Its a small map with lots of sea, desert and not very populated. In theory a simple map?

Do you not use QVFR? It's the main reason I got the QP. I can run 72 pretty much all the time and 90 FPS in some situations. No reprojection.

Yes please!

An update on my previous post. I have been tinkering with settings and I have noticed that the ghosting effect is worse with sharpening enabled. With no sharpening there is virtually no ghosting. I am using Meta link cable and Quest Pro. Meta link scaling x1. PD x1. QVFR centre at 1.7 (0.3x0.3) periphery 0.5. DLSS 3.8.10 preset E. Quality setting but custom set to 0.9 using DLSS tweaks. I would be willing interested to see if anyone else has noticed this.