Qcumber

Thanks. The next Quest is unlikely to have eye tracking so I am not relying on that. I run my QP at a centre resolution of about 4800x4800 pixels. I know that seems extreme but I can get a steady 72 FPS using DLSS Quality with no ghosting. A very sharp and smooth image and my maximum VRAM is about 12gb. Based on that I should be able to run the Crystal Super with similar settings. I'm not in a rush to buy but the temptation is there. Which would be the better option: 57, 50 or Ultrawide?

Which one to go for? 50, 57 or Ultrawide? The other thing I would like to know is how good the Super eye tracking is compared to the QP?

On paper it seems that way but in reality the QP a very good headset. I have 12 months experience with the Pico 4 and the QP is much better even though the resolution is much lower. Weirdly the screen door was effect is worse on the P4. Ideally I need someone with significant experience with the QP who has upgraded to the super. It is a lot of money for something that seems very buggy at the moment. How is the resolution for distant objects? Will the Crystal Super run on my specs (in signature)?

Monitor resolution? No effect at all.

I'm not sure if I want someone to persuade me to buy one or not to buy one. Cost is a big issue as is reliability (or so it appears on this forum). That said they do appear to be very keen to develop what we need for DCS so that's a big plus. With foveated rendering my 5080 should be OK. I run my QP at pretty high resolution settings so that I offset DLSS ghosting.

Does anyone have any direct experience with both the Crystal Super and Quest Pro? Is it worth an upgrade?

That's odd. Are you capping your frame rate in DCS?

I would advise running at 72Hz rather than capping the frame rate in DCS. 90Hz is probably means that you are maxing out your system.

Flying low over Berlin is very demanding. I get about 40-50 FPS. I can maintain 72 FPS over Cairo and about 50-60 over London and Paris. This is without shadows and civilian traffic and with range set to extreme. I am using QVFR with Quest Pro.

The F4-U is definitely more demanding. I can still maintain 72 FPS on most maps but it has a higher GPU load. I need to do a direct comparison of frametimes with other modules.

It will be worth waiting for. Once it does arrive we can all live long and prosper.

Yes please!!!!

The only advantage to using a lower resolution is if you want to have a windowed mirror rather than full screen. I set mine to 1080 with a 1440 monitor. It has no effect on performance.

Interesting possibility for a future VR experience. YORO Increases VR Frame Rates By Rendering One Eye & Synthesizing The Other https://www.uploadvr.com/you-only-render-once-vr-frame-rate-improving-technique/

"Unplayable with meta quest 3 controllers in VR" Yes. It is. Unfortunately you still need a HOTAS etc.

The image is more blurred when QVFR is enabled for me too if I leave it set at x1. I push the foveated region up to x2 with VD godlike. This gives me very sharp images and no ghosting with DLSS quality. However I have a Quest Pro so can get away with a smaller foveated region due to eye tracking. With centre at x2, 0.25x0.25 and periphery at 0.5 I still get a good performance boost over no QVFR at Godlike.

With QVFR you need to have plenty of headroom with your CPU. What are you using? With a 5070ti you need a pretty beefy CPU to make best use of QVFR. If you have not done so already try adjusting the QVFR settings. Keep the periphery as low as possible (about 0.4) and a narrow foveated region (about 0.25x0.25). With DLSS set the foveated region to at least 1.5 to counter the ghosting.

Issue solved. I had been adjusting IPD in DCS when it crashed. I opened DCS in flat screen and checked all the settings. IPD was set to 5555.5. I did not know this was possible. I reset it and no everything is fine.

When I try to launch in VR I just get a black screen. It happens with both Meta Link and VD. Using Quest Pro. I have tried disabling XR layers and no effect. Log file is attached. dcs.zip

Kept getting a black screen in VR last night with both meta link and VD. Sound was OK. I gave up as it was late. I need to try again tonight. Edit: I am still getting a black screen. Edit: weird thing. Black screen caused by IPD in DCS being set to 5555.5.

I agree with the engine sounds. I've heard a Corsair start up and fly but I've never sat in a cockpit. I imagine it should sound a lot more gutteral. Hopefully that will improve. To be honest I find the P-47 a bit disappointing with sound.

I prefer not to use ASW and keep to 72 FPS. It is not often that it drops below this. I sometimes use ASW when flying low over big cities etc but it is still smooth. It might be worth comparing systems. I set up a method for analysing frame times in VR. If you try running some tracks without Turbo and see how the frametimes look. Or you could just record them and send the XRFrametool data files to me and I can add them to the spreadsheet. If you then send me your DCS track I can play it on my system and compare.

It's not necessarily the headset. It is more likely a combination of other factors including pc hardware and software. In some cases Turbo mode can introduce stutters. I only need to use Turbo mode when I use VD via WiFi. It helps smooth out the frametimes but does not necessarily reduce visible stutter. With VD ethernet and Meta link I don't need it. The frametimes are very consistent. This is what mbucchia says about it in his GitHub Wiki: "Turbo mode Note: This is a highly experimental feature. If it makes your game crash or misbehave, please disable it. Turbo mode makes the game entirely ignore any frame timing or throttling dictated by the OpenXR runtime. In other words, Turbo mode forces the game to draw and submit frames as fast as possible regardless of any recommendations or policies from the OpenXR runtime. Turbo mode can increase your frame rate under certain conditions, but there is no rule or guarantee. Turbo mode can also have undesired side effects: Any statistics or performance measuring tool might now present incorrect data for frame times (however frame rate will be reported correctly). For example, on WMR, when using the performance overlay, all app CPU/GPU values will read 0. Any feature of your platform that relies on frame timing data, such as Motion Reprojection/Motion Smoothing/ASW, will not behave correctly. For example, on WMR, the motion reprojection will not engage automatically anymore, but it can be forced via the Lock motion reprojection option. Latency is increased, in a way that may or may not visible. Note: Turbo mode is offered as-is. There will be no support for issues filed while using Turbo mode."

Turbo mode works well for me and does not affect ASW. It does vary though and can depend on your system.