Qcumber

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.

The latest version of XRFrametools has now corrected the issue with exporting individual frames data so you should now only need one version. I have updated the VR benchmark methods thread to reflect this. Also an updated spreadsheet to correct some errors and add a VRAM chart. https://github.com/fredemmott/XRFrameTools/releases/tag/v0.2.0

The frequency is the number of frames that fall within 0.1 ms latency periods. XRFrametools captures individual render times. The spreadsheet looks for events that fall within 0.1 ms periods and counts them. This is then expressed as a percentage of the total number of events. The shortest latencies are being picked up at around 20 ms, peaking at 21-23 ms and extending to 26 ms. You have not included the other charts or table but I would estimate that FPS is 37-50 with mean around 45. FPS is [1000/GPU-render-time] so you need a minimum of 27.8 ms to maintain 36 FPS. However, CPU render time will impact in this if it is too long and cannot deliver to the GPU on time. What do the CPU render times look like? Can you show the FPS chart? This will show the variance and spikes.

I wonder why it's working for me and not you!? Maybe success with today's driver.

Has anyone tried 576.28 yet? https://www.nvidia.com/en-gb/geforce/drivers/results/245385/

What GPU?

No issues that I have noticed up to 576.02. I've not tried 576.15 yet.

Not yet. I'm away from home this week but was planning to look at this at the weekend.

What are your pc specs etc? Is this just the Cold War Germany map?

The 5080 super sounds interesting (if the rumours are true). However, the 5080 16Gb is a great card for VR too. The highest VRAM use I have seen is 12Gb. I got mine at MSRP. In the UK the stock/price is very good at the moment so hopefully the same is true for your location. It would be a good upgrade to a 3090. However, you might also need to upgrade from a 5800x.

No. The BSB2 has much better lenses and the potential for eye tracking. No. The G2 has limited life and old lenses. My point is that you could consider a Quest 3 (or Quest Pro if you want eye tracking). Whilst I like the look of both BSB and the MeganeX they are very expensive and unlikely to give you a significant boost over other, cheaper headsets. On paper it looks great. However, there are no real comparisons with other headsets in DCS. Do you have one yet? How does it compare to a Quest 3?

I did not think that you needed a Bluetooth connection. I'm not at home at the moment so I can't check.