sleighzy

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.

A few users been getting this. Rename your C:\Users\username\Saved Games\DCS folder to DCS.old (rename it and not delete so you can copy back your bindings from the Config\Input folder). The DCS folder will get recreated when you start DCS again. Something unknown at this stage is getting corrupted.

Sweet. Can you drop the answer here as well, just in case somebody else hits it and they find this thread.

As posted on the DLSS Swapper Reddit this is a known issue. Nvidia App runs behind on the latest versions, so performing overrides in it will not use the latest, ie the one you got from DLSS Swapper.

This sounds like a question better supported in the the official Virtual Desktop Discord server: https://discord.gg/YuXnEYfj I'll have a look as vaguely rings a bell there, but jump onto that Discord server and they should solve it in a few minutes. Also attach a screenshot here of your sound settings in the Options tab of the Windows Virtual Desktop streamer app. They'll likely ask for this in the Discord server as well.

See my comment here for setting the preset and overriding the HUD and MFDs in the DCS settings. https://forum.dcs.world/topic/368163-dlss-4/page/15/#findComment-5649561

This mod here https://www.digitalcombatsimulator.com/en/files/3336353/

If you are using DLSS, or decide to try it, then use the DCS config for controlling the preset, and the ability to not have this applied to MFDs. Add the below line to the C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file, create it if it doesn't already exist. DLSS_Preset = 'K' The additional optional line below can also be added to that file. This will bypass the HUD and MFD for DLSS, means greater control if you'd like to use DLSS4 for the game, but hate ghosting on the MFDs and don't want to apply to those. Best of both worlds. HUD_MFD_after_DLSS = true Check your Meta app as well to see what you've set the resolution slider to, and increase that as needed, e.g. 1.3, 1.5 etc. The fact that can hardly see the MFDs sounds like your settings haven't been tuned / pumped up.

As already mentioned, if using wifi then definitely get Virtual Desktop, I've always found AirLink to be garbage.

DCS is crashing around the point of initialising the dx11 backend so does not contain any information about your video card. What card is this and driver version you installed? The DCS log analyzer identified the GPU error: There is a GPU-related error (Re-)install the latest GPU drivers. Don't overclock your GPU or RAM. Some GPU's come with a factory overclock, you can use MSI Afterburner to verify this. You may need to DDU the old drivers to make sure the new ones are clean. The Windows DxDiag report in the zip identified memory timing issues, and the GPU issue may also be effecting Nvidia GeForceExperience. Windows Error Reporting (WER) Kernel Events The following kernel-events have been detected: VIDEO_ENGINE_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 NVIDIA GeForce Experience.exe: was hung for 17.70s and killed Memory Timing Issues Remove any overclocking (XMP) from your RAM. For the SFC and DISM reference open a command prompt as administrator, run the below two commands separately and then restart your PC. dism /online /cleanup-image /restorehealth sfc /scannow You can also try the following: Try a slow repair of the game Delete Saved Games\DCS\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Next, try renaming Saved Games\DCS to DCS.old and try again. (rename, don't delete, so you can get your bindings back from the Config\Input) folder. In addition to this your page file is likely not being utilised as your disk space is really low, need at least 10% free size. After freeing up space update your page file to 32768 for the initial and max values, click Set, Ok, and restart your PC. Make sure this is on your fastest SSD (looks like you have only one) and remove any others, e.g. system managed. Some other items. Disable core parking. You can use the ParkControl software for this. Alternatively there is a registry key you can change (would need to Google for it). Disable core isolation Run DCS from the bin directory and not bin-mt. They are both multithreaded and bin-mt will be removed in the future. The log analyzer may flag more items in the future based on your specs, i.e. game settings, but not until such time as the GPU issue is resolved and shows up in the logs again.

You can do this if you're using Virtual Desktop to connect to your PC. It has native support to show a passthrough for your hands. I'm not familiar with the Rift S however as to it's camera support for passthrough for this, you may need to inquire on the Virtual Desktop Discord server. EDIT: I just enquired, no Rift S isn't supported by Virtual Desktop for hands passthrough. VD only supports standalone headsets.

No reason not to (not sure if you can individually state which should be parked and which shouldn’t). DCS doesn’t “require” it per se. However, DCS doesn’t ask an individual core to do work. It requests the OS (CPU) to do work and the OS will schedule that task onto a core, which may be currently parked in which case it needs to “wake up”.

Oculus Tray Tool or Diagnostic tool won't work for VirtualDesktop. Make sure the resolution is set high as possible in VirtualDesktop, i.e. Godlike, like diego999 mentioned. QuadViews is definitely an option, it's what I use, for cranking up the resolution as well. It'll put more load on your CPU, but you may be just fine given your current specs. Increasing the Pixel Density in the DCS VR settings may also help, it can be a performance hog though so you might need to play around with it to get results that work for you, YMMV. If you do go down that road then make sure that this is set back to 1.0 if you use Quad Views as well. I personally use Quad Views myself and get awesome performance and clarity from it. If you are using DLSS/DLAA there is now new support in DCS for disabling this on the MFDs and HUD so you can get the in-game benefits of it, but keep the blurriness (if this is actually the cause of your problem) of those down a little. Add the below line(s) to your C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file, create it if it doesn't exist. The K preset is one of the latest ones so is a good option to try out. DLSS_Preset = 'K' HUD_MFD_after_DLSS = true

Please raise your own post. Your issue is completely unrelated. Attach your logs to a new post and it can be discussed further there so that there is not two different issues being tracked and clouding things. EDIT: as an initial heads-up though, this appears to be a GPU related issue. Try reinstalling your GPU drivers, may need to DDU them to make sure clean. Remove any overclocking on the GPU, some GPUs come with a factory overclock as well so can check that with MSI Afterburner. Delete your Saved Games\DCS\fxo and metashaders2 folder. Side note; run DCS from the bin directory and not bin-mt. They're both multithreaded and bin-mt will be removed in the future.

It actually works in the inverse. The core is parked when there is less load, becomes idle, on it for power saving. As the load comes back on the core is unparked. This may be fine for normal workloads and power saving with things like laptops etc. for efficiency. However, when gaming when this happens rapidly, i.e. bursting loads, it is constantly parking and unparking the cores leading to latency issues. Disabling core parking means that the core does not "go to sleep" but is actively waiting for the next task.

Yes, the workaround will work. As part of the troubleshooting did that include the renaming of Saved Games\DCS like I mentioned above? This has resolved for other users so the launcher is still able to be used.

First off, remove your mods (there is an error with ECHO19 in the log...although likely unrelated) and run a slow repair of the game. This includes TacView, a user had a similar error resolved with disabling this. This part of the stack trace has shown up in a few recent reports: 2025-07-01 12:26:58.704 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff6bb71f554 00:00000000 2025-07-01 12:26:58.704 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'rubed' 2025-07-01 12:26:58.704 INFO EDCORE (Main): OS-Version: 10.0.26100 () 0x100-0x1 2025-07-01 12:26:58.705 INFO EDCORE (Main): 0x000000000073f554 (DCS): SW + 0x127434 2025-07-01 12:26:58.705 INFO EDCORE (Main): 0x0000000000797197 (DCS): SW + 0x17F077 2025-07-01 12:26:58.705 INFO EDCORE (Main): 0x000000000071778f (DCS): SW + 0xFF66F 2025-07-01 12:26:58.705 INFO EDCORE (Main): 0x000000000000461b (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB 2025-07-01 12:26:58.706 INFO EDCORE (Main): 0x0000000000004c42 (World): wSimCalendar::DoActionsUntil + 0x262 2025-07-01 12:26:58.706 INFO EDCORE (Main): 0x0000000000a5d46a (DCS): SW + 0x44534A 2025-07-01 12:26:58.706 INFO EDCORE (Main): 0x0000000000a5d141 (DCS): SW + 0x445021 2025-07-01 12:26:58.706 INFO EDCORE (Main): 0x0000000000a82612 (DCS): SW + 0x46A4F2 2025-07-01 12:26:58.706 INFO EDCORE (Main): 0x0000000000a368b4 (DCS): SW + 0x41E794 2025-07-01 12:26:58.706 INFO EDCORE (Main): 0x0000000000a37f73 (DCS): SW + 0x41FE53 2025-07-01 12:26:58.706 INFO EDCORE (Main): 0x000000000257d873 (DCS): AmdPowerXpressRequestHighPerformance + 0x108286F The DxDiag report from Windows contains the following: Windows Error Reporting (WER) Kernel Events The following kernel-events have been detected: VIDEO_MINIPORT_BLACK_SCREEN_LIVEDUMP,VIDEO_DXGKRNL_LIVEDUMP,VIDEO_DXGKRNL_BLACK_SCREEN_LIVEDUMP 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 AUDIODG.EXE: c0000005 (THXOutAPO-SSE2-v3.dll) For the SFC and DISM errors open a command prompt as administrator and below the below two commands separately and restart your PC. dism /online /cleanup-image /restorehealth sfc /scannow