PSVR2 - now works with Eye Tracking and Quad Views!

[RealDCSpilot]

On 8/19/2025 at 9:59 PM, Qcumber said:

Does anyone have a direct comparison? The Quest Pro is a very good headset and can be bought for a similar price to the PSVR2 (in the UK at least). The QP lenses are excellent. The PSVR2 has Fresnel lenses so how does the quality compare? 

Still higher resolution panels and no compression and latency compared to the Facebook HMD. The trick about the PSVR2 panels is always the super sampling setting, which you can set even higher now thanks to the help of DFR and DLSS 4.
For me it's crazy to see these two significant VR performance and quality boosts for my VR setup this year, without spending any money on hardware.

Big Thanks to @mbucchia and whatdahopper !!!
 

[Qcumber]

3 hours ago, RealDCSpilot said:

Still higher resolution panels and no compression and latency compared to the Facebook HMD.

On paper the PSVR2 appears to be better but the QP is a very good headset; much better than the raw stats would suggest. I had hoped that someone might have direct experience with both the QP and PSVR2. 

[Stellatny45]

10 hours ago, Qcumber said:

On paper the PSVR2 appears to be better but the QP is a very good headset; much better than the raw stats would suggest. I had hoped that someone might have direct experience with both the QP and PSVR2. 

I had several QPro's but was never able to get past setup as they were trying to force me to register as a business account. I think the image will be much better than that of the PSVR2. I had a good PSVR2 and was able to turn down the brightness to where mura was no longer readily visible. The DP connection is certainly better than fiddling with the Quest Link cable. The problems with the PSVR2 are narrow sweet spot and glare. Other than that it has great HMD tracking and controllers seemed to track reliably. Problem with the QPro will be unpredictable mandatory software updates and that Meta can brick a QP at any time for any reason and there is no recourse. Another possible issue is that there might be a block on registration for a given QPro ID# so it would be best to buy one that is returnable for refund. 

[Morat]

 

Well, I did some testing just now and woo

I've taken @RealDCSpilot advice and installed the latest DLSS and set it to Performance and Preset K. Sharpening I guessed at 0.2, I haven't played with it yet so I don't know what image/performance compromise will be needed.
I've upped the SuperSampling in Steam to 130% (from 100) which I reckon is quite a big leap!

The Image Quality is fantastic! Hard to quantify, of course, but as an example I can now read the smudged and faded cockpit labels in the F-14B without moving my head. I used to have to lean forward and get close in. The countryside looks amazing and it still rips past smoothly. My first impression as I loaded in was "Wow, that's much better".

Framerates have dropped back, as you'd expect, but I'm genuinely holding >50 FPS everywhere, even when taxiing at Ramat David. The range seems very small, which I wasn't expecting. I don't see over 60FPS in my test mission but it is always smooth and that's all I need. I did try 150% SS to start with and found that the FPS dropped to unacceptably choppy levels if I went very low over Lake Gallilee - possibly because I have water at Medium against all advice.

Moire effects are improved too, even the fences at Ramat hardly shimmer now when before they were an horrible mess.

Anyway, that was my test mission Cat vs Eagle instant action in Syria. I'll see how MP holds up but I'm hoping it will be OK as I've got a decent CPU and I'm now mainly GPU limited. I'm sure there will be more tweaking to come but I think I have a very solid baseline with much nicer visuals.

@JMW I tried to reproduce the glitch you described but I couldn't. The brightness appeared uniform, even when I ducked into the cockpit and squinted at the sky out of the corner of my eye (without moving my eyes, of course). So I can't help you there, sorry.

 

@mbucchia You are a legend amongst VR enthusiasts! Thank you so much for your work.

 

Specs for reference.

CPU: 9800X3D - Stock Clocks / AIO cooler
GPU: Asus 4080 (vanilla, no overclock)
MEM: 64Gb @ 6000MT/s
Storage: PCIe Gen 4 2Tb WD_Black SN850 (PS5 version!) for DCS, 1Tb Samsung 980PRO for Windows. 
MOBO: ASRock X870E Nova WiFi (hoping it doesn't pop my CPU!!)

 

 

**** EDIT ***

So I forgot that the total SS value is whatever is set in Steam VR * the Per Application value. I had 150% set in SteamVR so I've been rendering at much higher resolutions that I thought in the tests above and the value I settled on was actually 1.95 in total. 

All became clear when I fired up good old FPSVR.
I dropped SteamVR back to 100% and left DCS at 130% Which put my FPS back up over 70 with a definite drop in quality (much harder to read the landing and take-off checklists on the sides of the F14B cockpit.
What is also clear is my CPU framerates are high at ¬16ms and my GPU framerates are really low at 2-3ms. More tweaking!
 

Edited 15 hours ago by Morat
Stupidity

[RealDCSpilot]

@Morat Uh yeah. DCS's supersampling setting is always added on top of what you set globally with SteamVR. You were going crazy high per eye. In my case i never do SS settings in a game (DCS is at 1.0), i always go with SteamVR at 150% (which has one global setting plus one specific setting per game where you can add another factor to slightly finetune the global setting).
My current global setting in SteamVR is ~4100x4200 per eye. Before using Quad Views and eye tracking you could see this directly in DCS's log file. Now with Quad Views enabled, it looks a bit different and shows the Quad View resolution outputs with DLSS:

2025-08-22 15:41:25.297 INFO    DX11BACKEND (18664): Use DLSS preset 'K'
2025-08-22 15:41:25.350 INFO    DX11BACKEND (18664): DLSS successfully initialized, 836x852 -> 1668x1700
2025-08-22 15:41:25.350 INFO    DX11BACKEND (18664): Use DLSS preset 'K'
2025-08-22 15:41:25.385 INFO    DX11BACKEND (18664): DLSS successfully initialized, 836x852 -> 1668x1700
2025-08-22 15:41:25.385 INFO    DX11BACKEND (18664): Use DLSS preset 'K'
2025-08-22 15:41:25.419 INFO    DX11BACKEND (18664): DLSS successfully initialized, 732x744 -> 1460x1488
2025-08-22 15:41:25.419 INFO    DX11BACKEND (18664): Use DLSS preset 'K'
2025-08-22 15:41:25.454 INFO    DX11BACKEND (18664): DLSS successfully initialized, 732x744 -> 1460x1488

One very important tweaking option for DCS is having an autexec.cfg in Savegame/DCS/Config:

options.graphics.stereo_mode_use_shared_parser = false
disable_write_track = true
no_device_hotplug = true
force_cross_eye_recovery_tool = false
DLSS_Preset = "K"
HUD_MFD_after_DLSS = true

And why are you setting sharpening to 0.2? Go much higher! I'm at 1.0

Just in case here are my DCS settings (for graphics and VR only):

["VR"] = {
        ["bloom"] = true,
        ["box_mouse_cursor"] = true,
        ["custom_IPD"] = "62",
        ["custom_IPD_enable"] = false,
        ["enable"] = true,
        ["enableHMDMask"] = false,
        ["handOffsetX"] = 0,
        ["handOffsetY"] = 0,
        ["handOffsetZ"] = 0,
        ["hand_controllers"] = false,
        ["hand_controllers_debug_draw"] = false,
        ["hand_controllers_joint_throttle"] = false,
        ["hand_controllers_type"] = 0,
        ["hand_controllers_use_stick"] = false,
        ["hand_controllers_use_throttle"] = false,
        ["interaction_with_grip_only"] = false,
        ["mirror_crop"] = false,
        ["mirror_source"] = 1,
        ["mirror_use_DCS_resolution"] = true,
        ["msaaMaskSize"] = 0.33,
        ["openxr_eyeGaze"] = true,
        ["openxr_quadView"] = true,
        ["pixel_density"] = 1,
        ["pointer_use_type"] = 0,
        ["prefer_built_in_audio"] = true,
        ["use_mouse"] = false,
    },

["graphics"] = {
        ["AA"] = "DLAA",
        ["BlurFlatShadows"] = 0,
        ["ColorGradingLUT"] = 0,
        ["DLSS_PerfQuality"] = 3,
        ["DOF"] = 0,
        ["LODmult"] = 2,
        ["LensEffects"] = 3,
        ["MSAA"] = 2,
        ["SSAO"] = 2,
        ["SSLR"] = 1,
        ["SSS"] = 1,
        ["Scaling"] = 0.66,
        ["ScreenshotExt"] = "jpg",
        ["Sharpening"] = 1,
        ["Upscaling"] = "DLSS",
        ["anisotropy"] = 4,
        ["aspect"] = 1,
        ["box_mouse_cursor"] = true,
        ["canopyReflections"] = 1,
        ["chimneySmokeDensity"] = 10,
        ["civTraffic"] = "",
        ["clouds"] = 3,
        ["clutterMaxDistance"] = 690,
        ["cockpitGI"] = 1,
        ["defaultFOV"] = 69,
        ["effects"] = 3,
        ["flatTerrainShadows"] = 0,
        ["forestDetailsFactor"] = 1,
        ["forestDistanceFactor"] = 1,
        ["fullScreen"] = false,
        ["heatBlr"] = 1,
        ["height"] = 1200,
        ["lights"] = 2,
        ["maxFPS"] = 120,
        ["messagesFontScale"] = 1,
        ["motionBlur"] = 0,
        ["motionBlurAmount"] = 1,
        ["multiMonitorSetup"] = "1camera",
        ["outputGamma"] = 2.2,
        ["preloadRadius"] = 150000,
        ["rainDroplets"] = 1,
        ["scaleGui"] = 1,
        ["sceneryDetailsFactor"] = 1,
        ["secondaryShadows"] = 1,
        ["shadowTree"] = false,
        ["shadows"] = 4,
        ["sync"] = false,
        ["terrainTextures"] = "max",
        ["textures"] = 2,
        ["useDeferredShading"] = 1,
        ["visibRange"] = "Ultra",
        ["volumetricLights"] = 1,
        ["water"] = 2,
        ["width"] = 1200,
    },

 

13900K and a 4090.

 

 

 

Edited 5 hours ago by RealDCSpilot