GavH77

OK, so that worked! There is still a solid minute and a half or so between launching and being in the cockpit in VR, but in I am! Thank you Special K.

Hi Special K, Done that now, although as this is a wholly clean install from last night (with no modules yet added beyond base maps and the SU25 and TF51), can I assume from your reply that I can't possibly have reshader installed? I don't believe I use the OpenXR Toolkit - since using VR, I've gone with just Oculus Tray Tool and Link the headset via USB cable to the PC via the Meta Quest Link app.

On the basis that I don't know what that is, I'll say No. But I could well have installed something some time ago and long since forgotten about it! How can I confirm?

Thanks. Did as asked and got the 'Waiting for another application copy to release' message for a while before it logged in. Worked OK in 2D, same thing happens again in VR though, so this hasn't fixed it. Windows Drivers are up to date and GeForce drivers are 560.94, so the most up to date 'Game Ready' version. I've attached both the log file and a screengrab of what I see on my monitor once I remove my headset. As I mentioned above, this is 100% representative of what I see each time - it does not vary and freezes in exactly the same image. dcs.log

Thanks BigNewy. See attached. dcs.log

Hi all, As the title says, I can't launch ANY missions (regardless of a/c, map, or any variation thereof) in VR. Fine in 2D, but when I try to launch the mission in VR, the loading screen instantly freezes. Eventually, I get the 'not responding' Windows notification. Oddly, I've now noticed that it freezes in exactly the same position each and every time too. Like I say, no such problem in 2D other than the fact I don't play in 2D... I've tried changing video settings; removing the Chinook module (just after installing it is when I started having this issue); amending something in the logbook; deleting the mission editor folder; trying to roll back my Meta Quest 2 to an older version with the files that are part of a previous fix that's elsewhere on this forum - all to absolutely no avail. Last night, I completely uninstalled DCS and went with a fresh install. I tried it again before adding any of the modules I have (so basically, a 'bare bones' install) and got EXACTLY the same problem. So I'm now thinking it's the Meta Quest issue which I know we've had before. There have been DCS updates in the time since I first started getting this problem and updates to the Quest too, so I'm a bit stuck on this one. As much as I'd like to ditch Meta, I can't afford to just go out and buy a new VR headset and in any case, the Quest 2 works perfectly well on MSFS and the various racing games I use it for. So at the minute, a new VR headset would be just good money after bad. At the moment, I've conducted one flight over Afghanistan (a place I served in twice in 2009 and 2012 and was looking forward to getting back to, albeit virtually!) in the AH64 and none at all in the CH-47: both of which I paid for pre-release and both of which are currently a complete waste of cash. Any ideas? If anyone needs a logfile, can you also tell me how to generate one and I'll link it up?

Winner! Thank you - that did indeed work a treat.

Meta Quest Link App Version 64.0.0.359.367 (64.0.0.359.367) I'm on W11, all the latest updates and Meta Quest Link App Version 64.0.0.359.367 and as soon as I try to enable VR in the game, the restart fails just after the '15 years of DCS' splash screen loads. As a side issue, does anyone know what file I need to find and amend to turn that off so I can at least open the game in pancake mode?