sleighzy

Hey mate, sorry for the late response. PC died so haven't gotten to it yet, working on getting it back up and running again.

Possibly related to this older post:

There is no crash in this log so is possibly Windows killing the process. Run the Windows DxDiag tool and then save the report and attach here. You also have a huge page file. With 64gb of RAM you don’t need that and could reduce that a lot. Looks like you have core parking enabled as well. You can use the ParkControl program to turn off core parking.

A number of people (of the ones I've assisted or seen in the DCS Discord + Reddit) including myself have experienced an issue over the last months whereby the throttle for the F16 does not work. Looking at the Thrust axis in the controls bindings it shows as a double-bind. This is however not accurate as there is no double-bind with other axises in the F16 or elsewhere. Rescanning devices, restarting DCS and PC have no effect. The current workaround for this is: Clear the binding Save change Restart DCS Add the binding again Save change Restart DCS null

If you are using DLSS then add the below line to your C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file to set the DLSS preset, this is still C by default. You will need to create this file if it does not already exist. This uses the latest presets which will reduce some blurriness/ghosting. The second line is optional but means that DLSS will not be applied to your MFDs or HUD to reduce the ghosting that DLSS can introduce on those. DLSS_Preset = 'K' HUD_MFD_after_DLSS = true

Yeah doesn't sound like a WhisperAttack issue. I'll test it on my end in the coming days when I get a chance to see if the notepad is just broken in DCS, or if it's something else.

DLSS can be a cause of blurriness. Are you using this, and/or DLAA? There are ways to make this better although won’t be perfect. Any blurriness in the cockpit as well?

Sorry for the delayed response. The failed VR load contains the below in the log. This is it not finding a connected headset. I’d have a look into this first as doesn’t seem to be a DCS problem based on that log, eg connection issue between PC and headset etc. 14:59:13.459][Warning] OpenXR: waiting for HMD to warm up... 2025-08-03 21:59:23.107 ERROR VISUALIZER (Main): OpenXR failure XrResult failure [XR_ERROR_FORM_FACTOR_UNAVAILABLE] Origin: xr Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:558 On a side note you should run DCS from the bin folder now, the bin-mt folder is being removed in the future. DCS is all multithreaded now, the exes in both folders are identical.

Can you also try renaming (DCS will create a new one) your Saved Games\DCS\launcher.sqlite3 file and starting DCS again.

We aren’t doing anything special, we just automate the paste function for the DCS key binds to do this. If you write this as one line in a text editor, eg Notepad, and then copy and paste it into here do you get the same thing?

Correct. In addition to this also delete the shader caches Saved Games\DCS\fxo and metashaders2 folders to ensure that these are recompiled correctly with changes due to mods.

Yup, the issue with the launcher.sqlite3 file also causes the problem with module names being displayed in Chinese. Same workaround, rename it.

I used to use Nvidia Profile Inspector, but now that you can configure it in DCS I rolled back the NVPI overrides and just use the DCS autoexec.cfg config file for it. No other extra software for my VR for this. In theory it should just work, maybe you have a problem with your Nvidia driver? Could try cleaning it out and reinstalling it.

You setting the preset via the DCS autoexec.cfg file, or some other method?

Please attach your C:\Users\username\Saved Games\DCD\Logs\dcs.log file. It may just be a text document named "dcs" if your Windows is hiding file extensions. DCS will overwrite the log file each time, so needs to be one from a failed launch and one from a successful one.

Please attach your C:\Users\username\Saved Games\DCD\Logs\dcs.log file. It may just be a text document named "dcs" if your Windows is hiding file extensions.

Old news. DCS natively supports this now. Add the below line to your C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file to set the DLSS preset, this is still C by default. You will need to create this file if it does not already exist. 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

Likely won’t resolve your problem but you should be running DCS from the bin directory and not the bin-mt directory. They are identical, bin-mt is being removed in the near future.

Issues with the launcher will likely be due to some files in the Saved Games\DCS folder. This won't be touched when reinstallng the game. Backup your Saved Games\DCS\launcher.sqlite3 file and then remove the original. DCS will recreate this when it starts up. Failing that rename Saved Games\DCS to DCS.old (rename, don't delete, so that you can copy back your bindings from the Config\Input folder) and start DCS. You mentioned "cleanup" but I don't know entirely what that entailed. You should delete your Saved Games\DCS\fxo and metashaders2 folders after updates. In addition to this your log file shows you running DCS from the bin-mt folder. This will be removed in the future. Run DCS from the bin folder. If using the standard shortcuts use the non-MT one, they are identical now.

Reinstall doesn't touch Saved Games\DCS folder, where the problem lies. Backup your Saved Games\DCS\launcher.sqlite3 file and then remove the original. DCS will recreate this when it starts up. Failing that rename Saved Games\DCS to DCS.old (rename, don't delete, so that you can copy back your bindings from the Config\Input folder) and start DCS.

Never trust ChatGPT.

There shouldn't be a signification performance impact, you can use the "tiny.en" model in your settings file as well (this is what I use) to reduce VRAM even further. For the configuration stuff follow the instructions, i.e. installing WhisperAttack and the VoiceAttack plugin. You can skip the other profile stuff though and just use the VAICOM instructions for updating your existing Vaicom profile.

DM’d you link for download.

If you haven’t already then add the below lines to your C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file, create it if it doesn’t exist. DLSS_Preset = 'K' HUD_MFD_after_DLSS = true This will use the latest DLSS preset, which will reduce some of the ghosting. DCS currently uses C by default even though it’s on one of the latest DLSS versions. The second line will mean that DLSS is not applied to the MFDs / HUD so you don’t get the ghosting there that DLSS can introduce. Try with DLAA as well.

Replicate the issue and then attach your DCS log file so we can see if there are any issues with it starting up the OpenXR runtime. Attach your Virtual Desktop log as well.