sleighzy

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.

Sorry for the delay, vacation for a couple of days. Will try get a beta release to you in the next few days, will DM you the link.

I may have found a potential cause, I'll make a change for a future release. Whilst not yet reported by other folk it may crop up in the future given you have encountered a problem. If it's currently working on your desktop then you may just need to use from there until such time as I've made a change which means it potentially works for you from another location. I'm happy to make a change and release a beta to you if you wanted to try it out prior to a full release down the path, will at least help verify that it resolves it. Up to you.

Ahh, looks like not in the packaged zip. You can download it directly from GitHub if you're after it, use the "Download raw file" button (WhisperAttack/WhisperAttack - VA Profile.vap at main · nikoelt/WhisperAttack) Note, the example VA profile is just a basic example. If you're after integration with Vaicom for use in DCS then you can follow the instructions here for use in your VAICOM PRO profile. WhisperAttack/VAICOM PRO/VAICOM_INTEGRATION.md at main · nikoelt/WhisperAttack Interesting. I'd probably have to look through Google to see if there is any particular reason for this. Shouldn't be specific to WhisperAttack.

Sounds like possibly your registry change wasn’t right…. Try using the ParkControl software to disable core parking. You are using Windows 11 right? Turning off all your E-cores sounds like a bad idea. You’ve basically spent money on a good CPU, and then turned off half its power. No, you’d add it as an parameter on the end of your DCS shortcut command.

I'll try replicate this today for you. Can you try this with having the WhisperAttack folder in a different location, i.e. don't have under Saved Games\DCS in case the elevated user that is running WA does not have access to read those files under that user profile (C:\Users\username) . I haven't tried with it under Saved Games\DCS before so I'll see if I can replicate this, but would be my first recommendation to move it somewhere else. EDIT: I've tried this with it in my Saved Games\DCS folder as well and worked as expected. I do have this DCS folder excluded from my anti-virus, but don't know what other differences we may have. If you close and reopen the folder is everything still there? And opening WhisperAttack still fails?

So it's fixed now? Uninstall and reinstall should have done the same thing as running a slow repair with the option to remove extra files ticked. Neither repairs or uninstall/reinstall will touch the Saved Games\DCS folder (reinstall may update anything missing/defaults), so would have been the same as renaming it like I mentioned. Oh well, if it's fixed now then all good.