RealDCSpilot Posted Sunday at 10:03 AM Posted Sunday at 10:03 AM For me, and this changed my mind to never want to use a wireless VR hmd again, their biggest caveat besides compression is latency. For sims with HOTAS or steering wheels, latency has a huge impact. I was using VR streaming with a standalone HMD for two years and got used to it, but the moment i tried the PSVR2 with cable in a helicopter was a real eye opener. All of a sudden i had direct control over the aircraft, rudder, cyclic and collective felt so much different than before. I'll never go back. 1 i9 13900K @5.5GHz, Z790 Gigabyte Aorus Master, RTX4090 Waterforce, 64 GB DDR5 @5600, PSVR2, Pico 4 Ultra, HOTAS & Rudder: all Virpil with Rhino FFB base made by VPforce, DCS: all modules
Qcumber Posted Sunday at 11:29 AM Posted Sunday at 11:29 AM 1 hour ago, RealDCSpilot said: For me, and this changed my mind to never want to use a wireless VR hmd again, their biggest caveat besides compression is latency. For sims with HOTAS or steering wheels, latency has a huge impact. I was using VR streaming with a standalone HMD for two years and got used to it, but the moment i tried the PSVR2 with cable in a helicopter was a real eye opener. All of a sudden i had direct control over the aircraft, rudder, cyclic and collective felt so much different than before. I'll never go back. I only see latency wireless with VD. With oculus link cable there is no noticeable latency. It's the same as when using my Rift S. I still wish that the QP had DP though. 1 PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
RealDCSpilot Posted Monday at 05:05 AM Posted Monday at 05:05 AM (edited) 17 hours ago, Qcumber said: I only see latency wireless with VD. With oculus link cable there is no noticeable latency. Sorry man, but there is no tech magic possible to reduce the latency of the odyssey a rendered frame has to take through the route of streaming over wifi or usb cable. With a direct Displayport connection it will take a rendered frame only 1-3 ms to reach the display panels, while going through all the hoops and loops of processing needed for streaming over USB or Wifi you'll always end up with 40 - 80 ms. It's all the encoding and decoding, hacking everything into little transferable packets vs. just flushing it through a big pipe. Even with "Oculus Link" you'll end up with 20 to 40 times the latency the sim is actually meant to be played. You will "see" it, once you have the chance to compare it directly. I had two years of built up muscle memory with a standalone headset and was a bit shocked about the difference. When i changed my setup, i also did a DCS session with standalone HMD before and after the change to PSVR2 (which was roughly within 20 minutes). You can go into details here: https://pimax.com/de/blogs/highlights/technical-comparison-displayport-direct-connection-vs-quest-3-streaming-solutions-for-pcvr Edited Monday at 05:14 AM by RealDCSpilot i9 13900K @5.5GHz, Z790 Gigabyte Aorus Master, RTX4090 Waterforce, 64 GB DDR5 @5600, PSVR2, Pico 4 Ultra, HOTAS & Rudder: all Virpil with Rhino FFB base made by VPforce, DCS: all modules
Qcumber Posted Monday at 05:15 AM Posted Monday at 05:15 AM 6 minutes ago, RealDCSpilot said: Sorry man, but there is no tech magic possible to reduce the latency of the odyssey a rendered frame has to take through the route of streaming over wifi or usb cable. With a direct Displayport connection it will take only 1-3 ms while going through all the hoops and loops of processing needed for streaming over USB or Wifi you'll always end up with 40 - 80 ms. It's all the encoding and decoding, hacking everything into little transferable packets vs. just flushing it through a big pipe. You can go into details here: https://pimax.com/de/blogs/highlights/technical-comparison-displayport-direct-connection-vs-quest-3-streaming-solutions-for-pcvr That's why I said "noticable". I was comparing my experience with the Rift S and Quest Pro. With VD there is a lag when moving your head quickly. I don't see this with quest link cable. 1 PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
RealDCSpilot Posted Monday at 05:23 AM Posted Monday at 05:23 AM Ah i see, that's another type of latency on top. Called motion-to-photon. Your headset has to collect and process your movements, send it to your PC - process and apply it to the game - render it - compress it - send it back over Wifi or USB - decompress it and render it on your display panels again. 1 i9 13900K @5.5GHz, Z790 Gigabyte Aorus Master, RTX4090 Waterforce, 64 GB DDR5 @5600, PSVR2, Pico 4 Ultra, HOTAS & Rudder: all Virpil with Rhino FFB base made by VPforce, DCS: all modules
Cytarabine Posted yesterday at 12:46 AM Posted yesterday at 12:46 AM 19 hours ago, RealDCSpilot said: Sorry man, but there is no tech magic possible to reduce the latency of the odyssey a rendered frame has to take through the route of streaming over wifi or usb cable. With a direct Displayport connection it will take a rendered frame only 1-3 ms to reach the display panels, while going through all the hoops and loops of processing needed for streaming over USB or Wifi you'll always end up with 40 - 80 ms. It's all the encoding and decoding, hacking everything into little transferable packets vs. just flushing it through a big pipe. Even with "Oculus Link" you'll end up with 20 to 40 times the latency the sim is actually meant to be played. You will "see" it, once you have the chance to compare it directly. I had two years of built up muscle memory with a standalone headset and was a bit shocked about the difference. When i changed my setup, i also did a DCS session with standalone HMD before and after the change to PSVR2 (which was roughly within 20 minutes). You can go into details here: https://pimax.com/de/blogs/highlights/technical-comparison-displayport-direct-connection-vs-quest-3-streaming-solutions-for-pcvr The magic comes not from any technical wizardry but from how our brains perceive latency. When repeatedly exposed to latency of up to around 150msec our brain adapts and we perceive events such as our motor input on the controls and the visual feedback in the headset as being simultaneous. That however does not make the events simultaneous in reality and means that for things where a delay could be significant (like say oblique gunnery in BFM) the effect is still there even though we don’t perceive it. So when someone says they can’t feel any latency with a standalone headset they are entirely correct, they can’t feel it. That doesn’t mean however it isn’t there. 2
Qcumber Posted yesterday at 05:58 AM Posted yesterday at 05:58 AM 5 hours ago, Cytarabine said: The magic comes not from any technical wizardry but from how our brains perceive latency. When repeatedly exposed to latency of up to around 150msec our brain adapts and we perceive events such as our motor input on the controls and the visual feedback in the headset as being simultaneous. That however does not make the events simultaneous in reality and means that for things where a delay could be significant (like say oblique gunnery in BFM) the effect is still there even though we don’t perceive it. So when someone says they can’t feel any latency with a standalone headset they are entirely correct, they can’t feel it. That doesn’t mean however it isn’t there. At a steady 72fps, VD has a latency of about 35-40 ms which includes game, encoding, networking and deciding latencies. I presume that with DP the only major latency is game latency? So with a maximum game latency of 13.8 ms (to maintain 72 fps) the overall DP latency would be about 20 ms. Am I working this out correctly? I don't know what the latencies are through oculus link cable, but the bitrate is 960 mbps h264 vs 150 mbps HEVC10 with VD. So I presume the latency would be a bit less with oculus link!? Do these latencies affect eye tracking? Is the tracking better through DP vs a link with compression? PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
RealDCSpilot Posted yesterday at 07:35 AM Posted yesterday at 07:35 AM (edited) 7 hours ago, Cytarabine said: So when someone says they can’t feel any latency with a standalone headset they are entirely correct, they can’t feel it. That doesn’t mean however it isn’t there. Yeah sure, it tricks your brain. I got totally used to it with my standalone HMD. But to describe the effect better - i would call it the "old man" filter. Everything reaction time based get's "stretched and smoothed out" in time. Something like this. Stuff becomes more unresponsive. It becomes extremely obvious in helicopter takeoffs, like with the AH64. I have a full HOTAS in a seat, so i have to work with all arms and feet to coordinate a clean takeoff with cyclic, collective and pedals. You have to do a lot of work with micro corrections and my fist takeoff with the PSVR2 was quite an experience after years with of streaming VR. @Qcumber Yeah, you have to take your whole system latency into account, add HOTAS device input latency and so on. In the end you'll have that huge latency chunk of VR streaming in the middle of that data pipeline, which is a massive bottleneck compared to everything else. Based on some old numbers i remember it's ~15ms if you are running with DP and controllers over USB. With streaming you end up with 60 ms and more (VD numbers do only show what is relevant to the VR streaming part), don't forget that DCS is CPU bound and you are putting extra work with streaming on it. More realistic would be 80 to 100 ms even with highend hardware. Edited yesterday at 07:47 AM by RealDCSpilot 1 i9 13900K @5.5GHz, Z790 Gigabyte Aorus Master, RTX4090 Waterforce, 64 GB DDR5 @5600, PSVR2, Pico 4 Ultra, HOTAS & Rudder: all Virpil with Rhino FFB base made by VPforce, DCS: all modules
AlpineGTA Posted yesterday at 01:17 PM Posted yesterday at 01:17 PM On 8/30/2025 at 12:16 AM, mbucchia said: Yes the eye tracking and quad views foveated rendering will work fine on AMD. Thank you! i5-11600K CPU, 64GB DDR4 RAM, XFX Speedster MERC319 AMD Radeon 6900 XT, Oculus Quest 2, HP Reverb G2
freehand Posted yesterday at 02:59 PM Posted yesterday at 02:59 PM (edited) This head set intrigues me. When I first used the CV1 the blacks & the feeling of Hight when sitting in the A10 on the ground was so different compared to how is is now. Have owned many headsets but would like that feeing back. Edited yesterday at 03:18 PM by freehand
Morat Posted 2 hours ago Posted 2 hours ago (edited) I'd recommend picking one up, they're not expensive anymore by VR standards (£360 new in the UK, much less in the US for guidance) and I suspect they're getting to End of Life with the PS6 in the works and the poor sales of PSVR2 to PS5 owners. To add to comments about clarity, the PSVR2 is capable of perfectly good clarity if you use supersampling. Is it ultimately as clear as the new breed of mini-oled 4k/eye HMD? No.. but it's about 1/6 of the price. I have absolutely no issue with the cockpits in DCS or the HUDs/screens/pods. Since DFR was enabled, I've upped my settings and I can spot bogeys MUCH further out than I could before. What I'd love to see is a comparison between PSVR2 and a Quest3 on the same spec PC and tuned to the same FPS. You can run much higher settings with the PSVR2 now with DFR. I bet it would be interesting. Edited 2 hours ago by Morat 1
Qcumber Posted 2 hours ago Posted 2 hours ago 8 minutes ago, Morat said: PSVR2 is capable of perfectly good clarity if you use supersampling. How much SS are you using? Do you need the official PC adaptor or are there any third party ones? PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
Morat Posted 2 hours ago Posted 2 hours ago (edited) 15 minutes ago, Qcumber said: How much SS are you using? Do you need the official PC adaptor or are there any third party ones? 149% with DLSS Preset K. I was shooting for 150% but got bored with the slider, I haven't optimised to 1% I have seen third party adaptors mentioned but I got the official one on release (Amazon.de) Edit: I think you may have an AMD Card? If it's one with a USB-C socket then you may not need an adaptor at all. NVidia dropped that connection after 20 series, but AMD kept it for another gen at least from what I've read. Edited 1 hour ago by Morat 1
Qcumber Posted 14 minutes ago Posted 14 minutes ago 1 hour ago, Morat said: 149% with DLSS Preset K. I was shooting for 150% but got bored with the slider, I haven't optimised to 1% 1 hour ago, Morat said: I think you may have an AMD Card No. RTX5080 so I would need to get the adaptor. PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
Recommended Posts