sleighzy

Thanks for that. Yes if you could attach a full log that would much appreciated. Can you also confirm whether or not you have Motion Blur enabled, and turn this off if you do and try again.

Quad Views companion will still work if you’re still using Quad-Views-Foveated. Nothing has changed there. PimaxPlay has a new OpenXR Quad Views option as well though (this is unrelated to just using the Pimax OpenXR runtime). If you select that option, and remove Quad-Views-Foveated, then you won’t be able to use the companion app anymore, it only works with Quad-Views-Foveated.

By “OpenXR” do you actually mean the OpenXR Toolkit? They’re not the same thing, OpenXR is the API/runtime used by DCS and the runtime for your headset. Meta have an OpenXR runtime, which is typically what Oculus headsets use, but don’t have their own version of the OpenXR Toolkit. From the dxdiag.txt file you provided there was one crash from Tacview, about 3 from Corsair Link 4, and another couple from the NVidia Container. This last one I’m not familiar with so don’t have any insights at this time.

I see a mention of UH-60L as well. This log also doesn’t contain a DCS game crash. If this was supposed to be a crash then it may be Windows killing the process… If this was definitely a crash, and even if not, then run the Windows dxdiag tool, save the entire report, and drop it here. This may aid in identifying the last few crashes of processes on your system. I realise this original post was for somebody else, so your problem may be unrelated and may need a different posting unless you can replicate and provide a log containing this.

Awesome! Glad we got it sorted. Happy flying.

You’re a brave person disabling your antivirus checking on your Downloads folder.

These logs show a large number of custom mods, including integrity check failures and errors in scripts. You've stated that the clients all crashed at once, and that you cannot replicate in SP. Have there been any other changes made, no matter how insignificant (including DCS upgrade), recently? This mission has always worked in the past and is just a recent crash, or is the first time you've used this mission in a multiplayer context?

You only have 32Gb of RAM, and your preload radius is quite high, as well as a few other things you could drop. The below information is from the DCS log analyser: Advice Change your pagefile to at least 32768 MB (initial size). Tuning Tips Turn off SSLR. Turn off SSAO. Set Preload Radius to max. 60000. Disable civil traffic. Tuning tips are recommendations for better FPS based on your CPU, GPU and RAM. They might result in slightly decreased display quality. Looking at your page file the log says 9,216Mb which would imply a Windows system managed one. You should add a custom page file with an Initial and Max values of 32768, click Set, Apply, and restart your PC. Make sure that the page file is created on your fastest SSD (preferably NVMe), and that you remove any other page files so you only have a single one.

The QuadViews companion app can’t be used to adjust the fixed focal area so you’ll need to use the config file for that. Don’t use the companion app as well as editing the config file, the companion app will overwrite all your settings. Make sure to tick the Quad Views box in DCS as well, this was newly added and is required for this to work.

I also noticed you're using Varjo-Foveated. Worthwhile checking but DCS added a "Quad Views" option under the VR settings that enables/disables Quad Views a patch (or two) ago. This is off by default, so worth checking this to make sure it's on if you haven't done so already.

Still need your dcs.log file from the "C:\Users\username\Saved Games\DCS\Log" directory, may just be a text document named "dcs" if Windows is hiding file extensions. Make sure this is taken after you experience stuttering issues, if possible, without starting the game again.

From the DCS log analyser. Note, it is showing that you still have a bunch of mods there, including an error. Ignore the mention of an out-dated log. null null

Yeah, a lot of people still use it for that reason. Interestingly the Quad-Views-Foveated docs actually state that the FOV in OXRTK shouldn't be used with it. (Although, apologies, I've made an assumption here that you're using both)

Awesome, glad it helped! Yeah, Quad Views pushes a lot of the processing to the CPU, but can help significantly when configured properly to your taste. Turbo mode forces the game to render frames as fast as it can, ignoring what your runtime tells it to. This is an experimental feature, and Mbucchia has actually updated his config to have this off by default (although that hasn't been released so the default is still on), due to the problems it can cause. Basically it forces the game to render frames as fast as it can. Because it ignores what the runtime tells it to then it can mess with things like ASW/SSW which would ordinarily tell the game to lock the fps to half the refresh rate of the headset, and the headset would inject "fake" frames to get it back up to the required refresh rate, if for example you couldn't make the 72fps you'd set. Full information on this can be found here: https://mbucchia.github.io/OpenXR-Toolkit/other-features.html#turbo-mode (note that this info comes from OpenXR Toolkit, but was linked from the QVF docs as this is the same functionality added there).

DCS has supported Quad Views for a long time now. You could try installing Quad-Views-Foveated (by Mbucchia as well) and enabling this in DCS, instead of using the OpenXR Toolkit. QVF also has a turbo mode which is enabled by default, so you may see the same performance improvement, if not more.

May not show anything but you could run the Windows dxdiag tool, save the report, and then drop it in here. It should show the last 10 crashes for processes on your machine, just in case it flags something that might be related.

Yeah I'd helped another person the other day as this was crashing their VR, but showed up as a GPU error, hence mentioning it. What was the problem you experienced that by turning this off resolved it?

Nothing immediate in the log re: crash. There is one note however about disabling hot plug in your DCS CONTROLS settings. This may help with stutters as well as DCS won't be constantly scanning for new USB devices being added. You can always click the Rescan button if you plug in a new device.

No, you need to install Quad-Views-Foveated (https://github.com/mbucchia/Quad-Views-Foveated) and then tick the Quad Views box in DCS. No shortcut arguments are needed these days, everything uses OpenXR, you can remove any shortcut arguments you currently have. I'm also assuming by "openxr" you mean the OpenXR Toolkit? This shouldn't be confused with OpenXR which is actually the API/runtime. The OpenXR Toolkit is not needed, and in general they shouldn't be used together.

The DCS log analyser has the following response to this log file: There is a GPU-related error Remove any overclocking from your GPU Uninstall your GPU driver with DDU and install a clean one. Can you also check if you have motion blur enabled and turn this off as well.

On the topic of AV software, what are using, just the default Windows Defender? Some AV software is really bad and should be uninstalled as they can still have issues when excluding folders.

32Gb is not sufficient for larger multiplayer servers. This is evidenced by your system running out of memory based on the log. From the DCS log analyser: Your System ran out of Memory Increase RAM or pagefile There is a GPU-related error Remove any overclocking from your GPU. Uninstall your GPU driver with DDU and install a clean one. Advice Change your pagefile to at least 32768 MB (initial size). Tuning Tips Enable Full Screen mode. Turn off SSAO. Consider using TAA instead of MSAA. Turn off SSLR. Set Shadows to Medium. Disable civil traffic. Set Water to Low. Decrease Terrain Textures. Turn down MSAA to 2x. For the page file issue (note that the below is a bandaid fix to give your system an additional 32Gb without actually adding an extra 32Gb physical RAM): You only have a 5Gb page file, so I'm assuming a default Windows system managed one Set a custom page file with Initial and Max values of 32768, click Set and Apply, and then restart your PC Make sure you have a single page file and it's on your fastest SSD and remove any other page files

I refer to the runtimes as OpenXR runtimes as this is a) how the runtime apps refer to them, e.g. "default OpenXR runtime", b) the terminology as detailed by Mbucchia, c) the fact that both Oculus and SteamVR both provide runtimes for supporting other implementations, e.g. the Oculus OVR runtime and the SteamVR OpenVR runtime.

It’s not active per se, just available. No need to disable anything, you’re not using the runtime so nothing being used. The log does show OpenXR Toolkit (no mention of Necksafer) but there are no issues with it and won’t be causing your issue as far as I’m aware, you can disable it using the Companion app to confirm anyway.

Your log shows that have the Virtual Desktop API layer but you’re using the Meta OpenXR runtime. Do you not use Virtual Desktop and it’s VDXR runtime (which will be more performant than the Steam one, and even Oculus unless you’ve switched to using the cable… even then though )?