No visuals in my Quest pro after DCS update

[Digitalvole]

TLDR: Quest pro (quad views installed, using a link cable) has sound and tracking but no visuals (just spinning hour glass) when DCS loads in after updating DCS.

I turned DCS on for the first time in over a year the other day (having finally got through the worst two years of my life, haha) and it all worked fine. So I updated DCS (and windows, the PC hadn’t been turned on since I last played DCS, and now I get sound, tracking (can see on the monitor that head tracking is working) but no visuals. I have quad views installed and OpenXR (though i noticed the eye tracking wasn’t working even before I updated DCS.

Apologies if this seems lazy, but it’s been a while and I’m not sure where to start. I’m hoping there’s something obvious that I’m missing due to my absence from DCS for so long.

Any help/advice would be greatly appreciated, thanks.

(Quest Pro (link cable), Quad views, OpenXR, 4090, 5900x 64gb Ram)

[Mr_sukebe]

Please take a scan here:

 

[Digitalvole]

Thanks, I’ll take a look when the kids are in bed

[VR Flight Guy in PJ Pants]

Noob first thoughts: have you cleared those "fxo" and "metashader2" folders after updated and before starting?

[Digitalvole]

2 hours ago, VR Flight Guy in PJ Pants said:

Noob first thoughts: have you cleared those "fxo" and "metashader2" folders after updated and before starting?

That’s a jolly good idea, I hadn’t done that yet. It’s been a while and I’m clearly forgetting the basics!

[VR Flight Guy in PJ Pants]

Good luck. There are multiple factors which may contribute to visual problems which may require a lot more details, anyway.

[sleighzy]

Drop your DCS log file here after replicating and we'll see if anything obvious jumps out.

Quote

but no visuals (just spinning hour glass)

Doesn't even get to the main in-game menu I'm assuming? I've seen the hour glass once before (this is the one at the bottom right of the headset, like from the headset itself and not a Windows thing?) but wasn't anything permanent like you mentioned.

[ChariotOfFLAME]

It could also be improperly ordered OpenXR layers. That’s what it was for me when I installed Win11 recently

[Digitalvole]

Thanks for the help chaps, very much appreciated. I’ve made some progress, it seems there’s something afoot with quad views. I turned off turbo mode and hey presto! I can see!

Problem is, Turbo mode really helps smooth things out and I kinda need it. Also the Eye tracking isn’t working. There’s something fishy going on with quad views, but at least now I have a starting point for further investigations.

Any known issues with quad views that have cropped up over the last year? 

42 minutes ago, ChariotOfFLAME said:

It could also be improperly ordered OpenXR layers. That’s what it was for me when I installed Win11 recently

hmm, could this affect quad views?

 

On 10/21/2025 at 8:14 PM, sleighzy said:

Drop your DCS log file here after replicating and we'll see if anything obvious jumps out.

Doesn't even get to the main in-game menu I'm assuming? I've seen the hour glass once before (this is the one at the bottom right of the headset, like from the headset itself and not a Windows thing?) but wasn't anything permanent like you mentioned.

Thank you, but I’m not sure how to do that. I could of course Google it, but I seem to have narrowed down the culprit.

Thanks

Edit: I’ve found a thread from earlier in the year that may yield some results, fingers crossed.

Edited Thursday at 03:27 PM by Digitalvole

[Phantom711]

vor 3 Stunden schrieb Digitalvole:

Any known issues with quad views that have cropped up over the last year

Well…not an issue with QVFR really, but until recently it only worked with my Quest Pro when Eye-tracking was actually disabled in the DCS settings. It was counter-intuitive, but that‘s how it worked. Now last week I had to activate that option in order to have eye-tracking and hence QVFR working. 
 

Other than that I agree, that your issue might be the order of layers. There is an app called „XR Layer Manager“ or something like that. It will even recognize errors in the layer order by itself and offer a solution.

[sleighzy]

3 hours ago, Digitalvole said:

Thanks for the help chaps, very much appreciated. I’ve made some progress, it seems there’s something afoot with quad views. I turned off turbo mode and hey presto! I can see!

Problem is, Turbo mode really helps smooth things out and I kinda need it. Also the Eye tracking isn’t working. There’s something fishy going on with quad views, but at least now I have a starting point for further investigations.

Any known issues with quad views that have cropped up over the last year? 

hmm, could this affect quad views?

 

Thank you, but I’m not sure how to do that. I could of course Google it, but I seem to have narrowed down the culprit.

Thanks

Edit: I’ve found a thread from earlier in the year that may yield some results, fingers crossed.

You can install this tool and send us a screenshot so we can see what layers are installed and in what order. https://github.com/fredemmott/OpenXR-API-Layers-GUI 

[Phantom711]

That‘s the one I was talking about as well….

[sleighzy]

55 minutes ago, Phantom711 said:

That‘s the one I was talking about as well….

Yeah, I whacked enter on my response, then saw your comment from a few secs before pop up  Oh well, great minds and all that jazz, and he has a link now too.

[Digitalvole]

Thank you both, I’ve got a couple of things to try from the other thread I found, but if that doesn’t work the above link will be most useful

Edited Friday at 08:28 AM by Digitalvole

[Digitalvole]

Feeling a bit stumped, I've tried the suggestions in this thread but to no avail.

 

I also used the OpenXR layer manager but that seems pretty normal from what i can tell. The quad views log says "no data received from eye tracker" despite having eye tracking on in the oculus desktop app, phone app and the headset. I've re calibrated the eye tracking in the headset and that all works fine. Turbo mode seems to be ok now, its just the eye tracking that wont work. I've attached pics of the quad views log and OpenXR layer manager and what i think is my DCS log file.

Its all very odd and I'm all out of ideas at this point, so any further help or suggestions would be very much appreciated.

Edit: Just noticed my headset software needs updating, I'm still on v73 by the looks of it. Perhaps this is the problem....

 

 

dcs.log

Edited Friday at 12:16 PM by Digitalvole

[Phantom711]

Just to recheck on that: Have you turned on eye-tracking and Quad-Views in the DCS settings also?

[sleighzy]

13 hours ago, Digitalvole said:

Feeling a bit stumped, I've tried the suggestions in this thread but to no avail.

 

I also used the OpenXR layer manager but that seems pretty normal from what i can tell. The quad views log says "no data received from eye tracker" despite having eye tracking on in the oculus desktop app, phone app and the headset. I've re calibrated the eye tracking in the headset and that all works fine. Turbo mode seems to be ok now, its just the eye tracking that wont work. I've attached pics of the quad views log and OpenXR layer manager and what i think is my DCS log file.

Its all very odd and I'm all out of ideas at this point, so any further help or suggestions would be very much appreciated.

Edit: Just noticed my headset software needs updating, I'm still on v73 by the looks of it. Perhaps this is the problem....

 

 

dcs.log 115.63 kB · 4 downloads

Hmmm, the DCS log file shows the OpenXR Toolkit layer in there. I wouldn't have expected that this would be the case with that disabled. Can you uninstall the Toolkit completely and then drop another log file. In addition to this you're running DCS from the bin-mt folder. Run it from the bin folder instead. They're both multithreaded and the bin-mt folder and associated shortcut will be removed in the future.

 

[Digitalvole]

Ok chaps, it’s with egg on my face that I can confirm it was the headset itself not having been updated for a year that was the problem. It hadn’t connected to my Wi-Fi automatically for some reason, but it should have been one of the first things I checked. Sorry for wasting your time, I’m both a numpty and and a baffoon.

In an unexpected plot twist I think I prefer quad views without the eye tracking for a couple of reasons that I shan’t bore you with. Thanks very much for taking the time to help this simpleton, I promise to try harder in future.

23 hours ago, Phantom711 said:

Just to recheck on that: Have you turned on eye-tracking and Quad-Views in the DCS settings also?

I had. Thank you for taking the time to help me.

17 hours ago, sleighzy said:

Hmmm, the DCS log file shows the OpenXR Toolkit layer in there. I wouldn't have expected that this would be the case with that disabled. Can you uninstall the Toolkit completely and then drop another log file. In addition to this you're running DCS from the bin-mt folder. Run it from the bin folder instead. They're both multithreaded and the bin-mt folder and associated shortcut will be removed in the future.

 

Yeah I was mucking about with various things, including turning on OpenXR toolkit to see if it had any effect. As for the bin-mt folder, that must be the .exe extension from before it was only mt(?) (I can feel myself getting my out of my depth here.)
Again, thank you for taking the time to help me.

Now I’m off to bother the mission makers with my incompetence, I need to learn how to make a dynamic WW2 mission.

[Phantom711]

No worries. Glad you got it sorted out.

[sleighzy]

2 hours ago, Digitalvole said:

As for the bin-mt folder, that must be the .exe extension from before it was only mt(?) (I can feel myself getting my out of my depth here.)

Nah, not getting out of your depth here. That’s exactly correct. So now both multithreaded ED will remove bin-mt at some stage in the future, they’re just trying to get everybody using the bin one so they’re not confused why their shortcuts stop working when it’s finally removed.