PSVR2 - now works with Eye Tracking and Quad Views!

[freehand]

Compared to the quest pro the psvr2 feels like a cheap plastic toy that is for sure.

Edited yesterday at 08:29 AM by freehand

[Qcumber]

Up and running now. XR eye tracking had not installed properly and I needed to reorder the XR layers. Now it's all working fine. Just tweaking settings.

My impressions at this stage are very positive. The sweet spot is small but easy to find and keep.

Eye tracking is better than the QP. With the QP there is a lot of shadow flickering when transitioning between the foveated region and the low res. This is hardly noticeable with the PSVR2.

Sharpness is not quite as good as the QP but the softness means there are very few "jaggy" edges so it does not need any anti-aliasing.

I'll feed back in more detail later. I want to try the QP using Steam link and do a performance/quality comparison. 

[Qcumber]

After using the PSVR2 most of today I am not convinced enough to replace my QP. In my opinion the QP is at least equal or superior in all elements except for the display port link. In testing though I cannot see any obvious compression artifacts with VD or Meta Link and the PSVR2 showed the black borders at lower FPS which I don't see with Meta link. 

I think my initial thoughts regarding better "softness" and "less jaggy edges" are related to Steam VR rather than the PSVR2. I tried Steam link a while ago and was not impressed. Playing around today I managed to get some impressive results. 

[freehand]

I am going to retry my QP for a while I love what the psvr2 gives colours blacks are great the scaling field of view e.t.c I will keep both maybe I have lots of older demos with blacks nice colours for friends as I love seeing peoples reactions to VR for the first time.  

[RealDCSpilot]

@Qcumber Yes, wired directly to the GPU hammers down latency by a lot. This is an important element. Streaming alters the way your mind and body perceive the flight model of each DCS module. If you want to see compression, just fly very low over the huge forest areas in the Caucasus map (south of Senaki maybe...). What i don't get is what you mean with black borders at lower FPS? You should actually reach a much better visual result and fps with your 5080 compared to my 4090. Can you post some logs, Quad View etc.?

19 hours ago, Qcumber said:

Sharpness is not quite as good as the QP but the softness means there are very few "jaggy" edges so it does not need any anti-aliasing.

This is also not quite clear for me. You didn't set DLSS or something? DLSS is an AntiAliasing method(!) Without it, i can definitely see aliasing on the edges of all geometry objects.

Edited 8 hours ago by RealDCSpilot

[Qcumber]

1 hour ago, RealDCSpilot said:

@Qcumber Yes, wired directly to the GPU hammers down latency by a lot. This is an important element. Streaming alters the way your mind and body perceive the flight model of each DCS module. If you want to see compression, just fly very low over the huge forest areas in the Caucasus map (south of Senaki maybe...). What i don't get is what you mean with black borders at lower FPS? You should actually reach a much better visual result and fps with your 5080 compared to my 4090. Can you post some logs, Quad View etc.?

This is also not quite clear for me. You didn't set DLSS or something? DLSS is an AntiAliasing method(!) Without it, i can definitely see aliasing on the edges of all geometry objects.

I am going to take another look today. I'll try to summarise my set up and findings here with more structure. If I get chance I will measure the game latencies using Fred Emmott's XRFrameTools comparing the QP with the PSVR2. Then there will be a more objective comparison if anyone else is considering switching from the QP to the PSVR2. 

[RealDCSpilot]

How does XRFrametools record your latency data? I only see frametime for GPU and CPU, but this isn't latency. Latency is the time how long the already finished rendered frame takes to reach your display panel. The stuff that is shown in VD's frame info display. XRFrametools would need to have an app running on your HMD to measure that data.