sleighzy

HeatBlur (makers of the module) stated on their Discord server that this is a false positive, apologised for inconvenience to users, and provided the same workaround of excluding the DCS game folder in your anti-virus software and running a repair.null

Yup, all your settings will remain. Just need to put back the new DLSS4 310.x.x. dll again that has those fancy presets.

Did you update your DCS today? It will replace the dll files with the original ones and you need to replace them again. ...if that was the case for you.

I've dropped your logs into the DCS log analyzer which had the following to say: There is a GPU-related error Remove any overclocking from your GPU. Uninstall your GPU driver with DDU and install a clean one. Some GPUs come with factory overclocking, so use something like MSI Afterburner to check for this and remove it if reinstalling your GPU driver doesn't resolve this. This aligns with the massive amount of spam of DX11BACKEND (9500): failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED See this DCS FAQ on this: https://www.digitalcombatsimulator.com/en/support/faq/startup/#3312253 In addition to this: Hot plug Events Disable hot plug in your CONTROLS section. It also states that you should turn off core isolation. It also looks like you're running a version of DCS that is a few patches behind. WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores) You should also turn off core parking.

No need for Nvidia App (which you should probably avoid) or DLSS Swapper. Just installing the latest Nvidia driver and Nvidia Profile Inspector (https://github.com/Orbmu2k/nvidiaProfileInspector/releases) is enough. Just enable the DLSS DLL Override and set the DLSS Preset to your preset of choice, or latest (which is currently K), in NVPI and you're good to go.

Yeah that 1Gb saving is nice. For smaller spec'd machines we even advise users to drop it to 30000, which would mean even greater savings. For folk on 8GB cards (or even more) that's a decent saving and hopefully performance increase with less need to page in and out of RAM. I agree that the 1ms is likely not an issue, and folk would be probably be vastly happier to get back 1+Gbs of VRAM vs. a 1ms saving somewhere (doubtful if noticed). Thanks heaps for the testing and posting of your results @Qcumber , was good to see some actual physical numbers around this and less feels.

Unrelated to your bench marks but if you drop your Preload Radius from 150000 (which is really high) to about 60000 you'll save yourself a bunch of RAM and give you more headroom for both RAM and VRAM (stops paging to disk when you start hitting limits). Will also speed up load times as you're not loading a whole bunch of potentially redundant stuff into memory.

WhisperAttack v1.1.0 has just been released and now supports dark mode. Release v1.1.0 · nikoelt/WhisperAttack null

I've dropped your log into the DCS log analyser which had the following to say. Note that your preload radius is 100000 and is really high for the amount of RAM you have. This will be loading a lot of unnecessary stuff when the mission loads. Set Preload Radius to 30000 Disable civil traffic Upgrade your RAM to at least 16 GB to play DCS multiplayer. Change your pagefile to at least 24576 MB (initial size). Create a single custom page file, remove any system managed ones, with Initial and Max values of 24576, click Set, Apply and restart your PC. Ensure that Game Mode disabled Ensure that Hardware accelerated GPU scheduling disabled You also have the OH-6 gunner export hook installed. Remove this as has been known to cause performance issues. It doesn't look like you have the OH-6 mod anymore, but the export hook still exists in your Saved Games\DCS\Scripts\Hooks directory.

Attach your dcs.log file here as well. C:\Users\username\Saved Games\DCS\Logs\dcs.log (may just be a text document named "dcs" if Windows is hiding file extensions). Also when you say you use Park Control you are using this to unpark your cores? What Windows version as well?

The logs are stored in C:\Users\username\Saved Games\DCS\Logs. These logs are kept even after restarting your PC. They only get overwritten when you start DCS up again, so grab the logs after it crashes before starting the game again. The log file will be dcs.log , or a text document named just "dcs" if your Windows is hiding file extensions. There may also be a zip file created in that directory which contains additional information so attach both here.

Don't know if related to your issue but your log shows you have a Vive hand tracking OpenXR API layer installed. Have you tried without this? You can use the https://github.com/fredemmott/OpenXR-API-Layers-GUI tool to list all your OpenXR API layers, and from there you can disable them to see what impact they may be having.

In my experience no two systems are really alike, and a lot of people have a different combinations of setups and tools. The "best" Quest 3 DCS settings will differ for lots of people, and existing lists and videos get out of date really quickly...and in a bunch of cases it's wrong and really people should not be following them. In general, "it depends". Need a lot of logs, screenshots, and other info from each person to get an accurate picture and provide feedback that works for them. In my humble opinion folk are more likely to get better feedback by jumping into the #dcs-vr-chat room of the DCS Eagle Dynamics discord server, or the VR channels in the VR4DCS discord server. You'll get more up-to-date and the latest approaches as well as a wealth of feedback from people who tune, and help others tune, on a daily basis. Also immediate turn around times with q'n'a and requests for info. The Eagle Dynamics one also has a #dcs-log-analyzer channel that is really good for dropping your DCS log into and it will highlight issues and provide tuning advice. As per your comment re: putting everything on high and seeing how it goes, the DCS log analyzer channel is good for that and helping you know which things you could turn down. Set a solid baseline, only increase resolution in one place, and then start applying tools on top to eek out a little more performance. I find these DCS Forum threads good for specific questions and issues, but as soon as you get into general tuning recommendations for all you get heaps of people jumping in with numerous problems and "me too" and everything gets lost in the noise when you're asking for logs, screenshots, etc. etc. For example, the constant "I get stutters" has no one definitive answer, it can be for numerous different reasons. Without analysis of that one system it's hard to say what it is. My mantra is generally "It's always the simple things that cause the most problems" ... it's just a matter of finding that thing. Sorry for the wall of text, and I didn't entirely answer your question. Recommend the Discord servers I mentioned above. NOTE: for people using the "VR" button in DCS, this sets a Preload Radius of 100000, which is far too high. Generally set it to your physical RAM size or lower, e.g. 30000 or 60000. If you only have 32Gb RAM then immediately create a custom page file, only a single one (remove all other system managed ones), with Initial and Max values of 32768, click Set, Apply, and restart your machine. Make sure you aren't parking your cores. Turn off SSLR and SSAO. If using DLSS then make sure to use DLSS4 with either J or K presets. Only increase resolution in one place, e.g. Meta app, Quad Views, etc, leave PD at 1.0 in DCS. Set your headset at a refresh rate you're realistically gonna hit, this is pretty much 72hz in most every case. ....many many many more items.

Yes that is correct. I'm a bit confused. I see DLSSv3 v310.2.1 as well. But that is DLSS v3 and not DLSS v4. Is there any way to use DLSS v4 as of now? Many thanks in advance for any suggestion. The numbering is weird yes. 310.x.x.x is actually DLSS4.

Some people have noted that their anti-virus has quarantined the WhisperAttack executable, this also happened for me this morning. This is a false positive and a known issue for some Python applications built using PyInstaller (which we use) or py2exe. You can add an exclusion to your antivirus software, e.g. Windows Defender, to prevent this from occurring. nullThere is another executable builder which apparently does not exhibit this issue so I will be investigating that for later releases. Apologies in advance if this has happened to you as well.

Just the default of 0.4

Yeah, try it the other way round and see how the clarity vs. performance balance goes. For example, I run quad views at 1.4 (try it lower if it's bad) and DCS at 1.0 although my specs are different than yours so YMMV.

Bitrate setting in VD is in the menu in the headset. There's a slider, under the Streaming tab I think, that will show how much it thinks you can give it based on your network at the time. You can adjust as you like. Stutters can be due to numerous reasons. You can drop your DCS log here if you like and we can see if anything obvious jumps out. What do you set the PD in DCS to? Recommend leaving that at 1.0 and just increasing the resolution in QVF, otherwise you end up multiplying things multiple times.

Correct. OpenXR Toolkit not needed.

VirtualDesktop has SSW which is its version of ASW. Meta link app is an OpenXR runtime as well so nothing needs to change there, there are no conflicts.

Yeah Quad-Views-Foveated will still be there but DCS just won’t send it the 4 views per frame. It just ignores that part. I’m not 100% certain if it still ignores turbo mode though, there’s been a few convos on that topics including with the dev. Haven’t tried myself as I run quad views with turbo disabled as I use VirtualDesktop and VDXR doesn’t need the turbo.

Yeah try turning off in settings.cfg (don’t know how you were disabling QVF in your previous steps, eg using the OpenXR-API-Layers-GUI tool).

Have a look in your settings.cfg file and make sure the path and name is correctly pointing at where your VoiceAttack application is. This is for the voiceattack_location value.

You mentioned you are using Quad-Views-Foveated and OpenXR Toolkit. Have you tried disabling turbo mode in both of those? It’s on by default in QVF. It is documented that this can mess with ASW (or other motion smoothing implementation).

You can delete the entire folder of your previous version. Python is no longer required for running this so that can be uninstalled if you wish. I’ll drop a command here for the folk who want to keep Python but no longer need the libraries we used.