Qcumber

By "true PCVR" I presume that you mean a dedicated DP connection without any compression. DP will be better from a technical point of view but in terms of user perception the differences are likely to be negligible. As long as the headset is properly configured and the user knows what they are doing and can optimise the bitrate, video codec and other related settings (e.g. router for VD etc.). Do you mean Q2 or G2? The context of your comment (DP Vs link compression) suggests that you mean "..get the most out of the G2". If that's what you mean then yes, you should always aim the get the most out of any headset you have before going down the upgrade route. I still have a rift s and learned so much about VR using this headset. I still go back to it occasionally to apply new knowledge and experience to see how I can get more out it.

Yes. But subject to the disclaimer

Or a countdown to the start of the countdown for the next update?

It's probably your antivirus. I had to run an exception for the latest version. @actually_fred has anyone else reported this issue?

I would really like to help but you have not really answered the question I asked about maintaining the minimum frametimes. The only data that you have shown is at 45 fps and/or with high frametimes. In my experience if you exceed 13.9 ms with 72Hz you will get stutters. Even with reprojection. The other issue is if you are using OXRTK (or QVFR) Turbo mode. This can help. But in some cases it can make stutter worse.

Thanks. Are you noticing any fluctuations in the decoding latency? If you have time I would be interested in reviewing your data as I am currently working on a VR benchmarking method. If you are interested please see the link below. You can PM me the dara if that is easier.

I had issues initially getting 6000 stable even though motherboard and RAM were compatible etc. I appreciate the sentiment as do like tinkering and overclocking but I think I will leave my RAM settings as they are for now.

I was thinking more about the stability of your connection rather than the resolution. If the bitrate is too low or variable you will get stutters. What do the latencies look like in the VD overlay?

Have you tried adjusting settings so that you can maintain a steady 72fps with a frame interval if less than 13.9 ms? Do you use OXRTK and is Turbo mode enabled? Could you please post an image of the VD in game overlay so that we can see your bitrate etc?

Is 6400 really a significant boost in performance over 6000?

PoE?

That's the same one I have been using for about 2 years so yes it should work ok. Edit: here is a list of routers that have been "approved" by the VD team. https://reddit.com/r/OculusQuest/w/faq/virtualdesktop?utm_medium=android_app&utm_source=share

Unfortunately yes you still need to use a router. Is your current router close to your pc? You could use that to check if it works for you. Edit: please see the guide in the first post. It explains what you need for the connection. This is for the QP so ignore the eye tracking stuff and you should not need to use the android edit.

You only need the developer account for eye tracking with the QP. Are you connecting via the router? You need to connect an ethernet cable from pc to router then another ethernet cable from router to the headset (via the ethernet-usb adaptor).

Thanks. Although it did not go ahead it is still a nice "what if" mission.

Just doing some basic research into the use of the Corsair in the ETO. I see that it took part in several attacks against the Tirpitz whilst anchored in Norway. Given that the Kola map could potentially be used for WW2 missions, is there any asset that can be used to simulate the Tirpitz? Also, does anyone know if the Corsair saw any action on D-day? From what I have read the Fleet Air Arm operated several aircraft in support roles, including the F6F but I could not see the Corsair mentioned.

Don't forget the use by the Royal Navy.

Have you read the whole post? Your comments suggest that you have just skimmed it and made some assumptions.

Left rudder, left stick, shift your balls to the left and pray!

Just did a double check to see if I gave you the correct advice regarding Q3 and it does look OK. Hopefully Meta have not changed anything. https://communityforums.atmeta.com/t5/Get-Help/Virtual-Desktop-with-cable-connection/m-p/1163316

You might need to reboot your headset after disconnecting WiFi. I have to do that sometimes.

I would appreciate if you can send me XRFrameTools logs of comparison tracks of this so I can take a look. One with minimum pre-load and one with max pre-load, then we can compare the difference. I should add that CWG needs some optimization. It would also be useful to see the same applied to a more optimised map such as Syria.

I agree with that. VR takes a lot of perseverance. Unfortunately it's not easy to set up an tune yet but it has got better and better over the last couple of years.

Good post. I think there is a lot of potential misinformation out there that has not been tested recently. Please see my post at the bottom as I am trying to test these parameters objectively. From what I have tested so far none of these appear to make any difference in VR performance or with stutter. Again I need to complete testing and then I will post my results. I am not sure about this. My gut feeling is that sharpening has no effect on performance in VR but I have not yet tested this. This and reducing pre-load radius can reduce VRAM by about 1GB. However, you don't really need to do this if you have at least 12GB VRAM. Yes. In a lot of situations this can help. But not always. My preliminary tests suggest that you only really benefit from QVFR if you use a narrow centre view. Anything above about 3.5x3.5 has diminishing returns. I am running tests at the moment and really need lots of data from other users using different hardware and settings. If anyone wants to help then please see this post.

Have you tried my advice above regarding Meta link app and Oculus Debug Tool?