Jump to content

Recommended Posts

Posted
28 minutes ago, Lange_666 said:

I have crashes with Rift-S and running MT with Turbo Mode On when taking headset off (ST is fine). Turbo Mode set to OFF solves the problem.
Bug has been around for quite a while, nothing to do with latest updates (either DCS or Oculus).

I wonder why it has only just become a problem for me? I had occasional issues but not as frequently as it has been for the last few weeks. 

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.

IMG_0114.jpeg

 

Posted

Could an update have reset the 'sleep timer' type setting that was introduced back in an earlier headset update? Pretty sure q-pro received the option. I believe turbo mode makes the game/gpu communication ignore some kind of frame sync info, which cures the DCS jitters when GPU scheduling is enabled, but will cause DCS to crash if headset sleeps/wakes 

The last q3 headset update changed my headset frequency back to 70hz. It's never happened in earlier updates - so I guess anything is possible after an update

Posted (edited)

OK. I have resolved my regular crash issue. Clearing out the metashaders2 and fxo folder appears to have solved that one.

As part of my troubleshooting endeavour, I stripped DCS back to vanilla install with all the mods, etc, removed and then I started putting them back one by one. My observations:

  1. Vanilla DCS and Quest headset removal works as expected.
  2. OpenXR Toolkit with Turbo on, remove headset - DCS hangs.
  3. OpenXR Toolkit with turbo on (as we know it smooths the sim out a lot), Quad View Foveated Rendering Layer active (but not advertised for DCS - so running but not doing any QVFR), remove headset does not hang DCS.

So, as I said previously, the workaround to stop Quest headset removal with OpenXR Toolkit hanging DCS is to install QVFR. And if, like me, you don't want QVFR to actually do QVFR because it increases frame times and causes stutter in densely populated areas for high-specced systems, unadvertise it for DCS in the config file.

Thus, it's unfair to blame ED for the hang, as it works ok without the OpenXR Toolkit running. However, I'm not too keen on running an extra layer to fix another issue. I've seen mbucchia's code change in QVFR to solve the headset removal hang. I might look at the OpenXR Toolkit and see if I can migrate the change across for those who don't want to run QVFR or VDXR.

Is that helpful, or am I still being a smart arse???? Lol.

Edited by slughead
Posted

I've turned off "turbo mode" in QVFR and OXRTK and after 4 hours I have had no issues. 

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.

IMG_0114.jpeg

 

Posted

You can leave it on in QVFR if you are using the QVFR. mbucchia fixed the problem in that OpenXR layer. But if you don't want to use QVFR but want turbo on (as it does have a decent benefit), turn it on in OPXR Toolkit and unadvertise QVFR for DCS in the QVFR settings file: no more hang, but turbo boost on — best of both worlds. Just don't enable it in both.

Posted
2 minutes ago, slughead said:

You can leave it on in QVFR if you are using the QVFR. mbucchia fixed the problem in that OpenXR layer

Thanks. I'll try that. I don't really use OXRTK anyway. Just for contrast/saturation adjustments. 

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.

IMG_0114.jpeg

 

Posted

I tried enabling turbo in QVFR and crashed when i took my headset off. Disabling it in both QVFR and OXRTK seems to work. 

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.

IMG_0114.jpeg

 

Posted
11 minutes ago, slughead said:

I thought I'd give Virtual Desktop another go. It's a stutter fest, and frame rates are unstable. How are people saying this is great / better than Oculus Link? Is there a tuning guide somewhere? For the life of me, I can't find anything official. I'm running a 13900 and a 4090 with 64GB RAM.

I am finding it is the same since the v64/65 update. The frametimes are all over the place even when I have plenty of GPU and CPU overhead. I need to post some logs on their discord server. Oculus link is better, when it works (the last few weeks have been a challenge). I am hoping (🤞) that I have now solved all of my issues with link-cable. I really want VD to be the ultimate solution. I would love a cable version but I don't think it is doable. 

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.

IMG_0114.jpeg

 

Posted
37 minutes ago, slughead said:

Hey @Qcumber, can you share the DCS and VD settings that you were using so that I can compare?

I'll post some screenshots later. 

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.

IMG_0114.jpeg

 

Posted

Don't worry. I've sorted it to a degree. I was using my machine as a hotspot. I switched to my router, which has improved it dramatically but still has some stutters and network delays. I think that can only be resolved with a dedicated gaming router. That's something I am not willing to fork out for to try out VD with DCS.

Posted
3 minutes ago, slughead said:

Don't worry. I've sorted it to a degree. I was using my machine as a hotspot. I switched to my router, which has improved it dramatically but still has some stutters and network delays. I think that can only be resolved with a dedicated gaming router. That's something I am not willing to fork out for to try out VD with DCS.

What do your latencies look like? 

I use a dedicated router which cost me about £40 in Amazon. 

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.

IMG_0114.jpeg

 

Posted

Here are my settings in case they help. It does sound like a network issue.

 

e3c37339fef9aac6accc64b8fedfd241_0.png

d4bfc2860c48484239c7a555485ab9c0_0.png

  • Like 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.

IMG_0114.jpeg

 

Posted
1 hour ago, slughead said:

Yeah, my networking is 17ms and upwards. I'd need a dedicated router. What router are you using?

This is the one I got. It was a bit cheaper when I bought it.

Mercusys AX1800 Dual-Band Wi-Fi 6 Router, WiFi Speed up to 1201Mbps/5GHz+574Mbps/2.4GHz, 3 Gigabit LAN Ports, Ideal for Gaming Xbox/PS4/Steam & 4K (MR70X), Black https://amzn.eu/d/fyLGzKR

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.

IMG_0114.jpeg

 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...