fearlessfrog

A wishlist item: If the VR performance shader changes in here: ..can't be added to the product, then the next best thing would be some IC special rule that could be added to make them pass a MP Servers IC check. The shaders make a big performance impact in VR, and the IC friendly versions of the mods are less efficient. This wishlist item could help resolve that. Thanks!

+1

EDIT: In a lot more testing with 2.7 I'm starting to think this is a hardware issue on my side. My 2080 voltage is dropping under load and it could be causing this. I'm trying out a longer soak test with a GPU stress app to make sure. Hopefully it's the case where it's not a DCS -> SteamVR issue but just something local for me, and that putting reprojection on triggered it.

For my testing in narrowing down what caused DCS to crash with reprojection, I left the WMR settings file alone and just did the changes in the steps to my forum post here, e.g. just within the UI in VR for WMR using my hand controller. If you've changed your default.vrsettings file then you could rename it and get Steam to verify files, and it will write out a new default one. My default.vrsettings is here, just ensure we're talking about the same thing X:\Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings

So just to be clearer, it doesn't cause the issue at the moment of changing the setting. Once it has been changed though, then within DCS doing what you're describing (module swapping etc) or playing for 10 mins+ will then trigger it 100% for me. With no reprojection on it works fine (or at the very least a lot less often, as I've only found this out a day or so ago). Yep, I agree it's probably a general timeout bug and probably not this setting specifically, but for me and my system the use of VR reprojection being on and then playing DCS allows me to recreate it every time. It's

I think I can recreate it without reinstalling Steam. Reinstalling Steam didn't fix it, it was more the settings going back to default. It seems like for me and my system, I can reliably recreate the issue by turning VR reprojection on. I've put the full steps to recreate here (I did try to post this here but had issues with images/text mixing and couldn't figure it out quickly): https://forums.mudspike.com/t/dcs-vr-steamvr-has-encountered-a-critical-error-solved/12314/67?u=fearlessfrog (this is a bit of a dupe with here, but put here as well for completeness:

I think I can recreate it without reinstalling Steam. Reinstalling Steam didn't fix it, it was more the settings going back to default. It seems like for me and my system, I can reliably recreate the issue by turning VR reprojection on. I've put the full steps to recreate here (I did try to post this here but had issues with images/text mixing and couldn't figure it out quickly): https://forums.mudspike.com/t/dcs-vr-steamvr-has-encountered-a-critical-error-solved/12314/67?u=fearlessfrog

That sounds great - thanks! Not long now.. So with my edit above, I am happy to report a full Steam uninstall and clean out files (not just SteamVR, the whole of Steam) solved this issue for me. I tried a lot of other things, so surprised that worked, but my best guess is that some sort of older VR overlay sort of utilities I must have used over the years 'broke' vrserver.exe in a way that DCS would tend to trigger - but hard to tell now it's working. I think it's still possible to get SteamVR to freeze out (like you said, jumping cockpits a lot etc, in WMR bringing up the menu if

Just to follow up on this I have some success fixing it (or at least I believe, after playing for an hour it now seems ok after days of crashes). I had to uninstall, clean out and install Steam again. As in, no files left behind at all and a fresh Steam client installation (for me on another drive). I've left the SteamVR settings all as defaults (which has defaulted back to the resolution I was using at 'Custom' before) and am using the non-beta versions of SteamVR and WMR for SteamVR. Speculation on what was causing vrserver.exe to crash with DCS like that:

@Pikey - Does your experience with the upcoming DCS 2.7 help with any of this? I realize you might not be able to say in detail, but I could do with some hope on this EDIT: Just to follow up on this I have some success fixing it (or at least I believe, after playing for an hour it now seems ok after days of crashes). I had to uninstall, clean out and install Steam again. As in, no files left behind at all and a fresh Steam client installation (for me on another drive). I've left the SteamVR settings all as defaults (which has defaulted back to

Just to add that I am also having this issue. Specs: i9-9900K, 32GB, Nv2080 Win10 latest, Reverb G1. Things I've tried: - Updating from Nvidia driver 457.30 (which works pretty sweet on a 2080 still) to 465.39. Cleared DCS shader cache. - Verified all files in DCS Open Beta using 'slow verify', plus removed all mods. - Tried SteamVR latest beta and non-beta. Also WMR for SteamVR beta and non-beta. Fresh installs and reset settings. - Tried a SteamVR build from 13 months ago (v1.10.32) and SteamVR public branch for v1.15.12, both crash the same

EDIT: Just seems to be the same info as earlier in the topic. SteamVR will crash out when DCS is under load, with steps hard to reproduce.

No. They'll update here when there's a something fixed or improved: https://docs.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/mixed-reality-software#release-history

So frame timing is just sort of another way of expressing performance. If your headset is 90 Hz then that's 90 frames per second, so that's a budget of 11.1 milliseconds to render a frame (1000 / 90 = 11.1r) so you don't see a disconnect to where you are looking and DCS is drawing. DCS on more or less any system struggles to work in a budget of 11ms, as it's either the GPU struggling doing something expensive like MSAA or the CPU main thread being blocked with lots of draw calls. As you've seen, it's more realistic to try to aim for some sort of reprojection, where the budget will be 22.