Qcumber

It looks like you have a network issue. The networking latency is high and your max Bitrate Is only 20 mbps. Is your PC connected to your router with an ethernet cable? Is your router close to your headset? As you already have a good cable that has passed the meta test, I would suggest using meta link. It works very well and is at least as good as VD. I mainly use meta link now. For me it is a more stable experience than VD at the moment. I can get 960 Mbps and the clarity is slightly better than VD (very subjective) and there is less latency when moving your head quickly.

I'm not sure. It would be worth looking at your performance using CPU-Z or similar.

Does anyone have a 9800x3d and a 4090 using a Quest Pro? I'm interested in comparing this with the 5070ti and 5080.

Yes. A 32% increase at stock speeds and a 28% increase when overclocked. Of course the overclock potential will vary between cards. Also, this is a single test. I need to compare the two in a more demanding situation.

I just tried the F-4 take off from Afghanistan in VR. About 11.5 Gb VRAM on the ground. Less in the air. Slightly off topic but the ground is very poorly optimised. If I look straight ahead I get 72 fps with GPU frametimes about 10 ms. Look left it increases to about 12 ms. Look right and it increases to about 20+ ms. I don't know what is going on but it creates some very weird fluctuations in FPS unless you keep your head very still.

I have been lucky enough this week to be able to compare the 5080 FE with the 5070ti (MSI Ventus x3 OC). Setup A 9800x3d with a x870 motherboard (Asus), 64Gb DDR5 RAM at 6000Mhz, a 2 Tb Lexar EQ790 NVME drive (game drive). The CPU has a liquid, three-fan cooler. When comparing the two cards all settings are the same. DCS settings are at the bottom. The cards were compared at stock clock speeds and with overclocking (MSI afterburner). Stock OC Core Boost Mem Core Boost Mem 5070ti 2295 2482 1750 2695 2882* 2000 5080 2295 2617 1875 2695 3017* 2125 *Actual clock speeds were close to 3200MHz for both cards during testing. For comparison here are the 3DMark scores: 5070ti (stock) 5070ti (OC) 5070ti (%) 5080 (stock) 5080 (OC) 5080 (%) Steel Nomad* 6273 6745 107.5% 8050 9020 112.0% Fire Strike# 67955 72704 107.0% 78293 83752 107.0% *Average of 4-6 runs, #graphics score Quest Pro with Meta link cable at 72Hz and base resolution (1808x1856 per eye). QVFR smoothen_focus_view_edges=0.1 sharpen_focus_view=0.9 horizontal_focus_section=0.25 vertical_focus_section=0.25 peripheral_multiplier=0.8 focus_multiplier=2.2 Equivalent resolutions (if applied to the full screen) Base 2.2 0.8 Horizontal 1808 3978 1446 Vertical 1856 4083 1485 The test run was the instant action mission “Free flight over Syria” in the F-16. I used “XRFrameTools by Fred Emmott to capture single frames over a 1-minute period (4300 frames). XRFrameTools/README.md at main · fredemmott/XRFrameTools. Data recorded: CPU render time GPU render time VRAM use (current) FPS The results were extracted to a spreadsheet and used to calculate average values (plus min/max) and the number of missed frames (those that exceeded 13.9 ms; (1000/72 = 13.89 ms)). This is shown as the red dotted line in the charts. The charts represent the number of events occurring in 0.1 ms bins from 0 to 20 ms, displayed as a percentage of the total frames. What this shows is the distribution of frame times and the consistency across the track. Ideally, these should look tall and narrow to represent consistent frames times. Results The blue traces show the results for the 5070ti. Base clock (open). Overclocked (filled). The green traces show the results for the 5080. Base clock (open). Overclocked (filled). GPU render times were 2 to 2.6 ms faster (approx. 28-32%) for the 5080 vs the 5070ti. Overclocking for each card produced a 7-8% reduction in GPU render times, and a more consistent distribution (narrow and taller). The stock 5070ti was pushing the 13.9 ms boundary which could lead to missed frames and stutter. The CPU render times were essentially the same for each run. f-16 Syria f-16 Syria f-16 Syria f-16 Syria 5070ti (base) 5070ti (oc) 5080 (Base) 5080 (OC) CPU mean 4.12 4.04 4.09 4.06 CPU median 4.09 4.01 4.04 4.01 CPU min 3.37 3.16 3.31 0.24 CPU max 7.48 6.80 6.74 8.93 GPU mean 10.65 9.49 8.05 7.47 GPU median 10.58 9.42 7.97 7.34 GPU min 8.03 7.07 5.85 0.21 GPU max 14.00 13.22 11.21 13.66 VRAM mean 7.11 7.26 6.93 7.60 VRAM median 6.88 7.27 6.97 7.52 VRAM min 6.13 7.12 6.54 7.29 VRAM max 7.83 7.32 7.01 7.85 Events 4229 4229 4214 4214 Missed 1.00 0.00 0.00 0.00 % missed 0.02% 0.00% 0.00% 0.00% FPS 72.2 72.1 72.1 72.0

There is a "tick box" at the bottom right of the VD headset menu which allows you to view stats in the game: "Show Performance Overlay".

I like the look of the eye tracking version. My main issue is that you need to buy base stations and controllers separately.

The bitrate is very low. Ideally you need 150mbps+. Could you please post a screen shot of the in game overlay? Try meta link. You should get a better experience than you are with VD at the moment. Download Oculus Tray Tool and then you can adjust settings such as the image scaling, control of ASW and cable bitrate. If you are lucky you should be able to get at least 500mbps, possibly the highest at 960mbps.

Meta link has worked fine for me with the 5070ti and the 5080 with the latest NVIDIA drivers. The meta link desktop app does not recognize the cards but just gives the message "your system does not meet the requirements". It still runs though.

There is a massive variation in CPU and GPU load in DCS. Up high with a limited number of planes, you can get away with lower specs. With more objects, newer planes and low down on poorly optimized maps (e.g. Marianas) even high end systems struggle. There are certain situations when GPU and CPU appear overloaded and it is not clear why. I have recently upgraded to a 9800x3d and even that is very stressed in some situations. I think it might be QVFR related when the GPU is maxed out. I am working on some VR benchmarks to look at this. Hopefully I will be able to post them soon.

I like what AMD are trying to do, but the recent increase in MSRP of the Rx 9070xt is a bit frustrating. Especially as it is very difficult to buy anything even at that new price. I am hoping that over the next few weeks the stock levels will make this card more accessible. They are certainly being more proactive than NVIDIA.

For VD you need a dedicated wifi 6 router connected to your PC by an Ethernet cable and close (2m) to your headset. Otherwise you are likely to have poor stability. The VD discord have information on the best routers. https://discord.gg/PPJrGY8U The other option is using meta link cable. You need a decent cable such as this one: https://amzn.eu/d/8PcVw87 A lot of people will tell you that VD is better. There are pros and cons with both, and I often switch between them. However I mostly use Oculus cable link. The other thing to try is Quad Views Foveated Rendering. This can be used without eye tracking and can give you a big performance boost. https://github.com/mbucchia/Quad-Views-Foveated

Welcome to VR. If you have persevered for 3 weeks then you now realise that VR can be a challenge. Don't give up. With your PC specs your fps is about where I would expect if you are at full resolution. Before going any further some more information would be useful. What are your VD and DCS settings? VD does not support usb connection, unless you have used some unofficial workaround. Could you share a screenshot of the VD in-SIM overlay?

Glad you like it. What are your system specs? I am thinking about benchmarking QVFR settings with different setups to help people with QP get optimal results.

Have you followed all the instructions here: https://github.com/mbucchia/Quad-Views-Foveated/wiki/Meta-Quest-Pro#if-you-use-link-cable-or-air-link Or are you using VD? https://github.com/mbucchia/Quad-Views-Foveated/wiki/Meta-Quest-Pro#if-you-use-virtual-desktop I don't remember it being that difficult.

Updated driver and results for 9070xt. Not tested in DCS yet but looks like a big improvement for VR.

I would advise that too. Depending on where you live you might be able to get a 5080 at MSRP. I'm in the UK and used a tracker app to alert me of availability. I just managed to get a 5080 FE at the new price of £949 from NIVIDIA. Just be patient and keep your phone nearby for alerts. You need to be quick.

I can vouch for what diego999 says. Hopefully though this will get easier as more people use VR and can share experiences. The problem is that things change very quickly so advice from a year ago may no longer be relevant.

Ghosting is much better than it used to be with DLSS 4 and preset K but it is still there. It's noticeable against the ground and in some situations against clouds. I find it is very usable compared to how it was. I'm still on the fence about wether I should use DLSS or MSAA. I noticed it was better going from a 4070 to a 5070ti. I also think that increasing the resolution as high as possible helps too. I'm speculating here but I do think that maintaining consistent GPU frametimes helps too. How does it compare to MSAA? Well, MSAA is still a sharper image and no ghosting but comes with "jaggies" and "shimmering". DLAA/DLSS is much better in this regard. If you look at one of my comparisons above DLSS does come with a significant performance hit (about 1.5 ms Vs MSAAx4). It's even worse with DLAA (+2.5 ms). I need to do some more benchmarking on this, particularly in challenging missions. I am planning to use "xrframetools" so that I can capture every frame. I think this is important in more intensive GPU loads so that there is a more accurate reporting of missed frames etc. I don't think OXRTK does this very well as it only reports and average of about 10 frames.

Yes. Or at least check.

I've just posted some GPU benchmarks for VR.

Here is the thread with my latest benchmarking

The final results and my current settings. Very similar to the "Low" settings and better than my old settings Comparing the F-16 flight over Syria with F-4 take off from Syria and Marianas Some dropped frames on Marianas but overall a playable experience. The F-4 take off in Syria has a biphasic component which relates to longer latencies on the runway and much lower latencies once airborne.

In the next run I tried maxing out all the details sliders. T8 has these sliders set mid range. T9 are all maxed out. You can see that the "Flight over Tripoli" part of the track is causing an increase in the latency which is as expected but overall its a small amount and can probably be controlled with backing off on some of the details sliders and not others. I am not sure why the VRAM is showing as lower. I think this is some error in the recording. I will try to repeat it.