diamond26

this is usually the picture you see when you have DCS running. If you close DCS, do you still have the same issue?

I had that feeling too when I first used VD but with the latest version with VDXR and the Ultra or Godlike resolutions (sharpening is 100) I'm not experiencing this problem. For sure Link sharpening is more prominent compared to VDs one, but the clarity has been improved drastically. I also use the H264 codec with 400 bitrate and of course Quad Views

I’m a bit confused with the point about link is used with higher render resolution. (VD stated resolutions are per eye) Whenever I check OpenXR toolkit log the resolution stated for max out Oculus setting is 2704 while with God like VD resolution is 3072.(no other supersampling is applied) So it seems that VD is already running higher resolution than link. I do agree that the visual result seems better with Link but on the other side VD seems more stable especially after the latest DCS patch that caused a lot of issues with memory leaks.

I prefer Oculus sharpening first because it affects everything on headset and then per application I control how much I want. For DCS I use 0.5

only in fixed mode

That was actually my problem that turned me away from VD at the end. Although it has a lot of nice things, it's not able to keep framerate the way Link does and as you said ASW is much better. Fortunately I 'm happy using Oculus link both with Q2 and QPro. I don't understnad why you are able to use it with Q3 but not Qpro . When I first moved to Qpro from Q2 it worked exactly the same with better clarity. It's very strange if you want my opinion

I believe @Gunnergolly asks for more than data/power USB cable, as in his message he mentions ethernet adapter and internet feed to the headset.

+1 (Quest Pro)

It was so nice that they have fixed in 2.9 and now it’s worst than ever!! NVG view everywhere

Personal preference is to have Distortion Curvature at Low, Encode resolution 3664, Encode bitrate 500 and Link Sharpening on Normal (or enabled). I would suggest also to check the adaptive option in ASW provided by OTT since you want ASW for Apache.

It's very strange how different are the results from system to system or user to user. the first time I used QPro was with the exact same settings I used for Q2 in Oculus app, OTT, Quad views, DCS settings and I was impressed to see better perfomance with QPro (apart from the obvious differences coming from lenses)

I finally made the switch from Q2 to Qpro and I'm very happy about it. The clarity is phenomenal coming from Q2 and the colours are much better. I used the exact same settings I had for Q2 in OTT (encode 3664 and bitrate 500) and I haven't notice any problem. I use link cable and while with Q2 the charging was enough to keep the battery above 80%, with Qpro I'm not sure it works the same. I need more testing on this. Oculus app resolution is at max so I can compare at the same level with Q2. The end resolution as reported in OpenXR toolkit log is higher in Qpro despite been officially lower compared to Q2. Performance seems better in Qpro using the same settings with Q2 (I will do more tests in the upcoming days) I use Quad Views and I'm really amazed the way it works. My only point with this is that you see (even slightly) the transition between focus and peripheral area. Comfort wise, I had to turn around the back headrest to make it fit better on my head.

I'm also in the market for an upgrade from Q2 and for sure reading the users' statements on QPro, the differences between Q3 and Qpro are more than eyetracking and local dimming. Lenses are better in Qpro offering better color and clarity. If those are covering the price difference I guess it's personal. I still try to make a decision myself between the two.

On my Q2 2 examples (using Quad Views fixed)

I believe that the resolution you finally use is the one set in the override option in OpenXR toolkit. You can see what resolution DCS was running on in OpenXR toolkit log.

In fixed mode it does not need eye tracking. It sets it to a static section of the view which you can configue values for. but isn't that job done by the Fixed Foveated option already available in OpenXR Toolkit?

How do you use QVF with Q3 that doesn't have eye tracking?

We had the same experience in a recent flight with Mosquitos using Normandy 2 map. One of us was flying in ST mode while others were in MT. In both modes the result was the same. It's very annoying that you get the effects in the cockpit, but you don't know where it's coming from unless you use zoom.

Try the highlighted settings in ODT null

very strange incosistency from Meta. I guess if you enable experimental options you will also see 120 Just checked Meta website (Europe) and this is the comparison chart between all three headsets. For wahtever reason 72hz and 80hz are not visible even in Q2!!! nullSo I get from this that 72Hz is available in Q3 as is in Q2 and as we saw earlier in this discussion form the review @Vladdo posted

very strange incosistency from Meta. I guess if you enable experimental options you will also see 120

According to Meta website it’s not

Thanks for the first impression. I would like to clarify this point though. According to specs Q3 is not supporting 72hz but you say it does. Is that right?

It definetely looks like a high end device and very promising. Let's see the pricing because the bracket they gave is from Pico 4 to Apple Pro (tha's some gap in between )

I will give it a try, although I was thinking that I was closing manually when I click the x button on top of the window. Thanks