Qcumber

That's why we need a Fairy Swordfish.

You don't need this anymore. Just use the default launcher and select the VR option.

Option 1 is more future proof. Another option might be to get a 5080. Cheaper than a 4090 and only about 12% slower. If you can get one at MSRP that is. Prices and stock are pretty good in the UK now.

I'm not sure about that. This occurs on the home screen so CPU and GPU use are minimal. What I have seen is a periodic spike in GPU frametimes every few seconds. I'll try to record a track.

You don't need this anymore. Just use the latest launcher and select VR.

Also Add: Fairy Swordfish Bristol Beaufighter Messerschmitt Bf 110 Hawker Hurricane MkIIC+D (40mm canons).

The OP is that there is intermittent stutter with frame time spikes, which disappear after about a minute. I still see this (frame time spikes about every 5-10s for about 1 minute after startup) but it does not reoccur or affect any missions. It is annoying but does not otherwise affect gameplay. It looks like other posts might relate to different issues.

Shadows have always been an issue with VR. I wish that this could be resolved. I just turn them off.

You don't really need lots of cores. If you are on a budget the 5800x3d is good. A better option (at twice the cost) is the 9800x3d.

Yes. I have a 3rd party one which meets the requirements. It would be worth considering if you need to replace your cable. Save a few dollars. This is the one I got with a charging port. https://amzn.eu/d/0eyVfnZ

NVPI- I would personally avoid forcing settings to DLAA. You have the DCS setting mgs to DLSS and quality. There should be a setting there to automatically use the latest version of DLSS. QVFR- Try reducing the foveated region to 0.33 x 0.33 if you can tolerate it. This makes the foveated region 10% of the overall image rather than 20% (0.45 x 0.45). Also see if you can tolerate a peripheral resolution of 0.5. Reduce smoothen focus view edges to 0.1. DCS settings- These look ok but I don't bother using anisotropic filtering as I don't really notice any difference in quality and it has a small impact on performance. Have you tried setting DLSS to balanced or performance to see how it looks?

You can play with the setting in the config file or use Quad Views companion although I'm not sure if that works with the Mégane X yet. https://www.digitalcombatsimulator.com/en/files/3332882/

You can download it here. https://github.com/mbucchia/Quad-Views-Foveated

It should be possible to look for variations in fps per unit time. I would need to think about how to do it though.

Have you tried using Quad Views Foveated Rendering in fixed mode? That will reduce the GPU burden considerably.

Link cable is working for me since the last update (Quest Pro). Have you done another cable test to see if the cable is damaged? Another thing to try is to make sure that the Meta link app is set to open XR. If you do you do go for VD it is very similar to link cable in terms of performance and quality. If anything the latest VD update (4 days ago) has the edge due to 2-pass encoding with 10-bit HEVC. However, you will need a dedicated WiFi 6 router connected directly to your PC with an ethernet cable. I bought mine for about £35 so not too bad. BTW $80 is a lot for a usb cable. Third party ones cost about $12 and work just as well.

There is a Fokker DR-1 at Duxford. I'll try to get some close up pictures when I am there next week at the VE day flying day. If it will help.

Having just sat in a Hawker Hunter cockpit I would really like to see this in DCS.

I have developed this analysis a bit more. I will update the first post soon and add my new spreadsheet but just wanted to share some of what I have added and why it might be useful. This will focus on FPS and a slightly different way of looking at it. The table below shows the FPS values for three different tests with different loads on the CPU and GPU. Test 1 is an F-4 take off from Syria (heavy) Test 2 is an F-16 flight over Syria (medium) Test 3 is a BF-109 flight over the desert on the Sinai map (low) FPS mean, 1% and 0.1% lows should be obvious. I have also added a "smoothness" score which predicts the range of variation from the average FPS value*. This should be more accurate than 1%/0.1% lows as it also includes values above the mean FPS and the full range in-between. As general rule with a smoothness score of below 90% you are likely to see some stutters, becoming more pronounced the lower the value. Values above 90% should have increasing perceptions of smoothness. Here is a plot of the distribution of the FPS count displayed as a frequency of occurrence. Basically the taller and narrower the shape of the track, the smoother it will look as most of the frame intervals fall around the 72 fps mark. As you can see in the FPS distribution chart (top) test 1 is much broader and flatter than tests 2 or 3, even though all three can maintain an average FPS of 72. This difference is represented in smoothness scores of 81%, 93% and 95% respectively. * For anyone interested in statistics I calculated "smoothness" as [1-Coefficient of Variation]x100. Credit to "tundrowalker" for the idea (https://www.moddb.com/tutorials/measuring-fps-performance-beyond-lows).

Have you run a log file through the discord log analyser? It would be worth doing this before anything else. https://discord.com/channels/542985647502393346/1179171301651402802

Is that the actual VRAM use or just VRAM allocation? You can check actual usage in the DCS metrics overlay. With my 5080 I have not seen VRAM use exceed 12Gb even though all 16Gb is allocated to DCS.

Thanks. I'll update the spreadsheet.

I am in the process of updating my spreadsheet to measure 1% and 0.1% lows, as well as other measures, so it might help you once you get your Pimax Super.

Something strange going on there. I've not been able to try it yet as I've been away. I'm back tomorrow so will give it a go.

Looking at your signature it looks like you are using a monitor rather than VR so measuring FPS and 1% lows is the right approach. With VR the maximum FPS is locked by the headset refresh rate so looking at 1% lows does not necessarily give you the right information when comparing different settings and situations.