sleighzy

The driver won't matter. 566.36 did not contain the DLSS4 K preset, but the latest DCS ships with the DLSS4 dll so will have that preset. Note, if you've changed NVPI setting to override the dll used then it won't apply for 566.36

I don't see the antifreeze issue in that log. The DX11BACKEND errors in the logs may be a redherring, I get these in my logs as well and are common to other users. About the web browsers etc. trying turning off Hardware Accelerated Graphics (HAGS) on your PC if you haven't already. Installing the Steam version won't change anything, the Standalone and Steam versions are identical.

Not sure what 6 attributes you mean, is only 2. The config file is in Saved Games so won’t be overridden. Those config changes were also made public on some channels by ED themselves so should be safe.

The DxDiag report contains a number of LiveKernelEvent errors with error code 117. This is also indicative of corrupted GPU drivers based on internet references. The DCS log analyzer also had the following to say about the DxDiag report: Windows Error Reporting (WER) Your system crashes with Bluescreens. The following kernel-events have been detected: DPC_WATCHDOG_VIOLATION,VIDEO_TDR_TIMEOUT_DETECTED Remove any overclocking (including XMP)., Run SFC and DISM to check your Windows., Check for any updates of your BIOS or chipset drivers., Application Errors DCS.exe: c0000005 (d3d11.dll) Generic Windows or Hardware Issues Remove any overclocking (including XMP)., Run SFC and DISM to check your Windows., Check for any updates of your BIOS or chipset drivers. For the SFC and DISM references you would need to open a command prompt as administrator and then run the two commands below, these are run separately and then restart your PC. dism /online /cleanup-image /restorehealth sfc /scannow

This error is normally indicative of GPU drivers issue. See https://www.digitalcombatsimulator.com/en/support/faq/startup/#3312253 for more info. Use DDU to remove your existing video cared driver and install the latest one. (Installing an older stable 566.36 driver release may also be an option). Drop another log if this is still occurring following on from that. I'd recommend removing your mods as well to ensure you're testing this with a clean base, you can put them back afterwards. This is an interesting error from the logs that repeats for this issue which I haven't seen before, a clean driver may resolve this. I'm assuming that you've made no other changes to other settings in your system, e.g. Nivida Profile Inspector, which could have triggered this? Potentially revert those as well. Failed to NVSDK_NGX_D3D11_EvaluateFeature for DLSS, code = 0xbad00002, info: N Your friend's issues are possibly completely unrelated so they should raise a separate issue and attach their logs and crash log zip to that.

Please replicate the issue and then attach your C:\Users\username\Saved Games\DCS\Logs\dcs.log file (just a text document named "dcs" if your Windows is hiding file extensions).

Not needed anymore. Natively supported in DCS now. Add the below line to your C:\Users\Saved Games\DCS\Config\autoexec.cfg file (create it if it doesn’t exist) to set the preset for DCS DLSS_Preset = "K" You can add this line as well if you don’t want DLSS applied to MFDs and HUD to keep them sharp with no ghosting for greater control. HUD_MFD_after_DLSS = true

Awesome-sauce. Yup, log analyzer tool is amazing, would have been the first thing I would have done with your log before digging in further

May be minutely GPU hit compared to using nothing at all. Yes, this is “hidden” away (should have been better documented in release notes). The second option is not everybody wants DLSS for MFDs due to the ghosting it can cause with cursors etc on radar screens and other things. I reckon it’s a great addition and compromise. Youre right though, it could have defaulted to K instead of C and people could override if they wanted to. The K (and J) presets are going to be a little less performant than some others.

The autoexec.cfg file is just flat lines, v.s. a lua like syntax, so just the below: DLSS_Preset = 'K' HUD_MFD_after_DLSS = true

Can you also enable the debug flag in Vaicom and the VA window will then show when the tx button is pressed and released. With DCS running, but viewing the VA window, can you see if holding down the mic button and talking shows the tx press line, but doesn’t show the tx release line until you finish talking and release it…or if the release is being triggered immediately.

I’m away for a couple of days so can’t dig in too much right now sorry. Can you confirm that you don’t have the radios bound to your hotas in the DCS controls settings for that plane. Based on that log for 80bytes the stop command looks to be occurring at the same time, or a few milliseconds after the start command. Can you drop a screenshot of your VA Vaicom profile that is expanded to show all the press and release plugin actions for your tx buttons. Can you also let me know which plane and tx button you’re using On a side note, in your last couple of commands you won’t need (and VA won’t recognize) using the sender in the command, eg Enfield11

No longer required either. Add the below line to your C:\Users\Saved Games\DCS\Config\autoexec.cfg file (create it if it doesn’t exist) to set the preset for DCS DLSS_Preset = "K" You can add this line as well if you don’t want DLSS applied to MFDs and HUD to keep them sharp with no ghosting for greater control. HUD_MFD_after_DLSS = true

Based on your comment I’m assuming you have set up a Meta developer account then and have hand tracking enabled. The drop-down will only display the Hands option if you are in VR and in the actual game, ie not from within the launcher or 2d. Is this the case?

Follow the steps in the link @Art-J provided. There is also steps for enabling the hud overlay to display the preset, Ive never used NVCleanInstall but that might be fine instead. There are other versions of the NVPI which may enable that overlay as well. If it still doesn’t work then drop a screenshot of the things you’re changing on the Nvidia Profile Inspector, including the selected profile.

Drop a DCS log file here and we can have a look at your current DCS graphics settings. With your specs you should be able to pump things up. Confirm also that the Pixel Density (PD) setting in DCS under the VR tab is set to 1.0 as some of the recommendations, e.g. additional VR tools, we can provide will depend on that. Within Virtual Desktop (the settings in the headset) what is your resolution set to? Godlike? And what is your VD codec and bitrate set to as well. With respect to the Nvidia settings I've attach a document with some recommendations from the VR4DCS Discord server (the #nvidia-gpu-discuss channel)NVCP_Settings_V3.2_WIP.pdf

The general reason the log analyzer has that message is that the recommendation is to use Windows 11 (and disable core parking) as this has better support for hybrid CPUs (P/E cores). This will be more performant as DCS will select the best cores to run things on, and Windows 10 may mis-report these which is why people sometimes get stutters (and use Process Lasso so that they can set which cores should be used).

Nice! Fixed after renaming the file? If so then somehow the config file got corrupted so was preventing things from starting up correctly.

Some additional items I noticed from your log. It shows that you have core parking enabled for your CPU. You should use something like ParkControl to unpark your cores. You preload radius is set at 100 which will mean it will be loading in assets frequently while you’re flying, may or may not cause visible stutters. With your RAM I’d change that to 30000 instead.

Your config is corrupt. Rename your Saved Games\DCS\Config\options.lua to options.lua.old and then restart DCS. It should regenerate new config again, you’ll need to reapply your graphics settings etc afterwards (it won’t lose your control bindings) You also have errors in the logs for it trying to start in VR and not finding an OpenXR runtime. In those cases it will just open in 2D. Can resolve that later if you do want to use VR.

Similar feedback from other folk re: the triggers. In all honesty DCS does not really support VR (quest) controllers for flying planes all that well. You'll have nowhere near enough buttons for the hotas controls. If you don't have a hotas then use an Xbox or PS controller. Look on Youtube for videos by Tuuvas on how to set that up and all the profiles for all the planes. Really simple and how many of us started off before getting a proper hotas.

This post is about cores reaching 100%, is this what you are experiencing? Your log is filled with errors from your mods and terrains. Remove those (including saved games mods/terrains) and run a repair. You can put them back, check the log to see which ones are causing errors each time, eg zip driver failing to open them Also what @scommander2 said, remove that process affinity mask from your shortcut, you’re killing off 3 cores (which seems like a weird number) making them not available. Recommend upgrading to Windows 11 as well to make better use of your cores. Run DCS from bin instead of bin-mt as well, they’re both multithreaded and bin-mt is going away. Ensure that DCS is also not being run as admin If you’re not using TacView then remove that as well as can cause additional performance issues.

Running UAC at lowest is bad. The description for it is a little wrong. The lowest setting will silently run some things as admin, even though they would run as non admin. This is possibly why you are getting this message.

The hard wiring is needed for the Ethernet connection between your PC and the router that you are connecting to with your headset. They recommend a dedicated router close to your play space. In the diagram above the dedicated router is on the right hand side, and the blue line has an Ethernet cable connected from that to your PC. Basically your existing router is just providing internet…which doesn’t matter as Virtual Desktop just needs a fast connection to your headset, it doesn’t use internet. Virtual Desktop guide for Internet Connection Sharing: https://github.com/Crayphish/vrdocs/wiki/Internet-Connection-Sharing

Not sure how your PC currently gets it's internet based on the distance between it and the router. Would this network configuration work for you? (Taken from the Virtual Desktop Discord for alternative network setups). I can post a link to the setup guide if needed. null