Qcumber

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?

You don't need your link cable. Just a female USB c to male USB c cable such as this one: https://amzn.eu/d/aHXLYVf Otherwise you could strap the ethernet-usb adaptor to your headset, which is not an ideal way.

This is the one I use. https://amzn.eu/d/3FTqgWD And a USB extension cable

Thanks. That gives us a starting point. In theory you should be able to get a reasonable performance from your setup with a Q2. As above are you using Meta link with a usb cable? Virtual Desktop can produce better results but meta link is very close in terms of quality so if you are currently using meta link I would stick with this until you are more confident with VR and tinkering with settings. This post has a lot of information for anyone new to VR. You might find it useful.

The movie "Devotion"?

Very good! I'm really looking forward to flying it.

That's what I have read too. Hence the difficulty landing in deck with sudden changes in throttle. The widdowmaker. I was wondering how it handles in general flight and dogfighting.

That makes sense. I wonder how the F4U handles compared to the P-47 and P-51.

The first thing I would advise is to make sure that the output resolution is sufficiently high. You need to aim for at least 1.5 times the native resolution. So for a Q2 that would be around 2900 pixels. I would aim for something like 3300 pixels if you plan to use DLAA or DLSS. Set the Meta link app to x1 output then use Oculus Debug Tool or Oculus Tray Tool upscaling to x1.5. There are lots of things to try before getting a new headset. It also helps to "learn" VR with a more basic headset so the Q2 is fine. I still have a rift s and use it occasionally. Once you understand the various VR settings then you can make a more informed decision about another headset. Edit: what are your PC specs?

It's better to do everything in one place if possible so I would advise using Meta and the Oculus Debug Tool or Oculus Tray Tool

Have you tried VD using an ethernet-usb cable connected to the headset? This is for the quest pro but I think the Q2 and Q3 can use this by default without needing the android tweak.

I can confirm that the problem still exists for me as per YoYo's summary. It lasts for about 1 minute in the hanger. By the time I have loaded a mission it has settled down so I have not worried about it too much. I have a fast NVME drive so perhaps this is it. No further stutters in missions and the flying is smooth.