sleighzy

Running a slow repair of the game, as well as ticking the remove extra files option, will get it back to a clean slate with needing to reinstall everything. Rename the Saved Games\DCS as has been mentioned previously as a repair or reinstall will not touch that location in case there are any issues there. Can you also drop your DCS log file here for further review. Make sure to load completely into a mission.

Could you drop your log file here as well. Do you run Quad Views (this has turbo mode enabled by default in case this is messing with the measurements that Qcumber is mentioning)? This would show up in the DCS log file to. EDIT: I see in your VR settings screenshot that Quad Views is toggled on, and that there is an exclamation mark beside it. The exclamation mark is fine, but indicates you have OpenXR API layers installed. So possibly you have Quad Views installed, will wait for your confirmation. You can use the Tallymouse companion app to turn off turbo mode vs. manually in the QVF config settings file https://github.com/TallyMouse/QuadViewsCompanion. That screenshot also shows you have Bloom Effect enabled, turn that off if using Quad Views. A lot of the Quad Views functionality replaces OpenXR Toolkit so you could remove OXRTK vs. running them both together. Possibly unrelated but there are known performance issues with later versions of the Nvidia driver and 5000 cards. A number of people have been dropping back to the 566.36 version so could try that as well (could use DDU on the drivers prior to installing 566.36 to ensure clean).

The logs show this is crashing really early on, not long after your peripherals are loaded. You mentioned that a clean saved games works but crashes after putting back your inputs config and options. I would highly recommend adding back just one input at a time in case one of those is causing the crash. Then do the same with the options.lua file. Will help narrow down if there is one in particular. If you find it's just one of them then try rebinding again manually. Running a repair of the game doesn't touch your saved games folder so it's likely this is one of them if it works when clean and crashes when not. I also note that the vJoy shows as being forcefeedback, not sure where that it set but could try setting that to off as well. The DxDiag report in the zip file also shows you have blue screen events occurring on your system. This is the output from the log analyzer: Your system crashes with Bluescreens. The following kernel-events have been detected: VIDEO_TDR_FAILURE,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. For the SCF and DISM checks you can run the below commands using a command prompt run as administrator. Run each command separately and then restart your PC. sfc /scannow dism /online /cleanup-image /restorehealth The error trace also references VCRUNTIME140. Not saying that this is the issue but you could try repairing that as well. Is a 1 minute job. Just download the latest C++ distributables from the Microsoft site and run the repair option. https://aka.ms/vs/17/release/vc_redist.x64.exe The link above is the direct download of the x64 version from the Microsoft site if you're worried about running that exe: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

Remove all your custom mods and run a slow repair of the game, choosing the option to remove other files. You only have 32Gb of RAM. Add a custom page file on your fastest SDD, remove any system managed ones, with Initial and Max values of 32768, click Apply, and restart your PC. Turn off / remove TacView. You have a low spec'd machine and this will be a performance hit. In addition to this your TacView is currently writing to a OneDrive folder which if synch'ing to the cloud could have other performance issues. Drop your Preload Radius from 100000 to 30000 - 60000. Delete your C:\Users\username\Saved Games\DCS\fxo and metashaders2 folders. This is from within VR. Does it work fine in 2D?

What's the gold shield in that VD overlay beside the bitrate? Do you have like secure encrypted network connections enabled (I can't remember the specific VD setting). Turn that off, or whatever you have enabled that is causing that shield to be displayed.

Thanks for the log @onib89, much appreciated. Renaming the Saved Games\DCS folder as mentioned by JoniHH will confirm that TacView isn't an issue as this will ensure that the scripts and hooks/exports aren't being used. Few points: Your Preload Radius in the DCS settings is currently maxed at 150000. Drop this back to 60000 - 10000 to save yourself some VRAM / RAM Your currently have a core affinity set on your PC, are you using Process Lasso? Try disabling that (or if you are doing this via other means, e.g. registry.) There are currently known performance issues with later versions of the Nvidia drivers on 5000 series GPU cards, which you're on. Trying rolling back to 566.36. You may need to use DDU to completely clear the Nvidia driver prior to rolling it back. Ensure that you aren't running the DCS.exe or shortcut as admin. Right-click your shortcut and under the compatibility tab make sure Run as administrator isn't checked. This applies to however you're currently starting DCS, so let me know if it's just via a shortcut. I say this as I noticed you have a number of peripherals, your Winwing one is a known serious performance issue if DCS is run as admin. You're also running DCS from the bin-mt directory. Run it from the bin directory instead. DCS is now all multithreaded so no need to run from bin-mt (and some people have mentioned problems). You also stated that you're using the PimaxPlay, this OpenXR runtime is also confirmed in the logs. You could instead use the original PimaxXR runtime instead as folk have had better experiences with this. This is what the PimaxPlay one is based on, although comments are that this original one is somewhat more performant. Not saying it's going to fix your problem, probably unrelated, but just something to keep in mind: https://github.com/mbucchia/Pimax-OpenXR/wiki

Rather than having it buried in this thread (not sure if you were going to drop it here) would you be able to either create a new post, or perhaps add to that other post you created a few days on performance which also had charts of this nature.

Yup disabling core parking is good, and wasn't flagged in the analyzer so looks all good there. Remove the Process Lasso stuff though, you're reducing what your CPU has available for performing certain tasks. Given that you mentioned you noticed no difference you definitely don't need it. I noted also you're on version 572.60 of the Nvidia driver. There had been reports of performance issues with these latest versions on 50xx series cards and people have been rolling back to 566.63. You could use DDU to remove the driver prior to installing another version to ensure that all remnants of the previous driver are removed. You mentioned you have tried older driver versions, not sure how far back you went so though could give that a shot as well. Turn off SSLR as well in DCS settings, this can be a performance hit with little benefit. Delete your C:\Users\username\Saved Games\DCS\fxo and metashaders2 folders. These will be recreated, may be slightly longer load time etc. first time around as they get recompiled, but will be a clean start. Check also and try disabling the below in Windows if you haven't already: * Game Mode * Hardware accelerated GPU scheduling After performing the above replicate the issue again and drop another log file.

The logs show that you've disabled half your CPU? system affinity mask: 11111111111111111111111111111111 process affinity mask: 1111111111111111 ... unavailable cores: {16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31} The DCS log analyzer states the following: Remove the core-affinity mask from your CPU. One of the support folk in the DCS channel commented on the following, as I noticed that the log didn't contain Process Lasso messages: "In this specific case, their CPU doesn't use any of the E cores as IO cores but uses the other pools for it." Have you applied an affinity to DCS either via registry setting, adding this config to your DCS autoexec.cfg file, passed these params in your shortcut to the DCS.exe, Process Lasso, etc.?

You still haven’t provided a DCS log file, in case it offers some insights.

Attach your C:\Users\username\Saved Games\DCS\Logs\dcs.log file (may just be a text document named "dcs" in your Windows is hiding file extensions). Make sure to jump into a mission before grabbing the log. What version of Windows are you on?

What DLSS level do you use in DCS, e.g. Quality, Balanced, etc.? I noticed you have ForceDLAA enabled, this won't be taking effect as you also have DLSSQualityLevels enabled. Instead of setting all the presets and then copying the DLSSTweaks config file beside the DCS executables you can just set the GlobalForcedPreset to the one you want, no need for copying config files over. Copying config files makes sense if overriding the quality ratios though for the one you use in DCS if you want to tweak it a little. Also the DLSSTweaks dxgi.dll file needs to be renamed regardless, this doesn't work as a bunch of DCS patches ago, so needs to be named something like nvngx.dll (or other examples you mentioned, although I haven't tested those options). This is documented as a known issue in the DLSSTweaks GitHub repo. Interesting point about the performance gain though. Been a few folk rolling back to the 566 (December) driver version given performance issues with the latest Nvidia drivers. I was a long time DLSSTweaks user (been using NVPI more recently for the preset change) so maybe I'll switch back to an older driver, and then use DLSS Swapper and DLSSTweaks to still gain the DLSS4 benefits.

Not at this stage. WA starts listening/recording when the tx button is pressed and stops when it is released. There is no functionality for a short press/release to start this, and then a subsequent short press/release to stop it. Broadcast Parallel is currently your only option.

Works for me. It's the steps I posted on 28th Feb on page 11 of this thread. Note that the steps re: DLSSTweaks and the debug overlay there are completely optional. It's just a way of verifying now (and in the future) if it's on the right version/preset.

No need for dll swapping. https://forum.dcs.world/topic/368163-dlss-4/page/11/#findComment-5611147

I believe TacView has an uninstaller, although I don't know if it completely removes everything. In your C:\Users\username\Saved Games\DCS\Scripts\Hooks directory remove any TacView files (back them up first). In your C:\Users\username\Saved Games\DCS\Scripts\Export.lua file remove the TacView line (back it up first). It may look something the below. Use something like Notepad++ to do this. local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') Check in the DCS settings (under the Special tab) and select Tacview on the left hand side if it is there. Untick the Tacview Module Enabled box.

This video doesn't show Quad Views. For Quad Views you want to install the below two items and tick the Quad Views box in DCS: https://github.com/mbucchia/Quad-Views-Foveated https://github.com/TallyMouse/QuadViewsCompanion

@onib89, please attach your DCS log file after loading into a mission and replicating the issue. The file is C:\Users\username\Saved Games\DCS\Logs\dcs.log (may just be a text document named "dcs" if your Windows is hiding file extensions).

@PatientSquire27, what happened when you tried without TacView enabled (given both the performance hit and your files going to OneDrive)? Removed from Scripts\Hooks and commented out/removed the line from the export.lua file?

Drop your log here, or just go directly to the DCS log analyzer as you likely have more problems than just that. https://discord.gg/Nqu5n5Sb

You have a number of issues going on there. Whilst motion blur may be a trigger like some other reporters it still appears to be a GPU issue. The log also indicates memory timing issues. Process Lasso detected Process Lasso can cause issues with DCS World. Consider disabling it. Memory Timing Issues Remove any overclocking (XMP) from your RAM. There is a GPU-related error (Re-)install the latest GPU drivers. Don't overclock your GPU or RAM. Additional tuning info: Remove the core-affinity mask from your CPU. Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled Core Isolation disabled Disable Tacview for performance reasons. Disable civil traffic. Consider using DLAA. Enable Full Screen mode.

Your log is spammed with USB unplug/plug events. Check to make sure your have Hot plugging disabled in your DCS controls settings. If it is then you may have a USB power management issue. Make sure you're using a powered USB hub, and also turn off power management on your USB controllers in Windows Device Manager. The final ones occur around the time it has issues with your OpenXR runtime. 2025-04-05 14:05:34.254 INFO APP (Main): Device unplugged: [USB] Realtek USB2.0 Audio 2025-04-05 14:05:34.265 WARNING LOG (12756): 2 duplicate message(s) skipped. 2025-04-05 14:05:34.265 INFO APP (Main): Device unplugged: [HID] HID-compliant consumer control device 2025-04-05 14:05:34.276 INFO APP (Main): Device unplugged: [HID] HID-compliant phone 2025-04-05 14:05:34.287 INFO APP (Main): Device unplugged: [USB] USB Composite Device 2025-04-05 14:05:34.298 INFO APP (Main): Device unplugged: [HID] HID-compliant vendor-defined device 2025-04-05 14:05:34.309 INFO APP (Main): Device unplugged: [USB] USB Input Device 2025-04-05 14:05:35.429 INFO VISUALIZER (Main): [16:05:35.631][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_FOCUSED->XR_SESSION_STATE_VISIBLE session=2 time=145625803405200 2025-04-05 14:05:35.429 INFO VISUALIZER (Main): [16:05:35.631][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_VISIBLE->XR_SESSION_STATE_SYNCHRONIZED session=2 time=145625803410900 2025-04-05 14:05:35.429 INFO VISUALIZER (Main): [16:05:35.631][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_SYNCHRONIZED->XR_SESSION_STATE_STOPPING session=2 time=145625803413400 2025-04-05 14:05:35.445 INFO VISUALIZER (Main): [16:05:35.646][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_STOPPING->XR_SESSION_STATE_IDLE session=2 time=145625827904300 2025-04-05 14:05:35.445 INFO VISUALIZER (Main): [16:05:35.646][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_IDLE->XR_SESSION_STATE_EXITING session=2 time=145625827909200 2025-04-05 14:05:35.445 INFO VISUALIZER (Main): OpenXR: request exit 2025-04-05 14:05:35.453 ERROR ED_SOUND (17788): IAudioClient::GetCurrentPadding failed: 0x88890004 (AUDCLNT_E_DEVICE_INVALIDATED) This also shows the same behaviour for your displays, headset and monitor 2025-04-05 14:05:38.011 INFO EDCORE (Main): (dDispatcher)enterToState_:3 2025-04-05 14:05:38.277 INFO APP (Main): Device unplugged: [DISPLAY] Mixed Reality headset 2025-04-05 14:05:38.278 INFO APP (Main): Device unplugged: [DISPLAY] Generic Non-PnP Monitor 2025-04-05 14:05:38.279 WARNING LOG (12756): 2 duplicate message(s) skipped. 2025-04-05 14:05:38.279 INFO APP (Main): Device unplugged: [USB] Generic USB Hub 2025-04-05 14:05:38.281 INFO EDCORE (Main): (dDispatcher)enterToState_:5

Attach your DCS log file. C:\Users\username\Saved Games\DCS\Logs\dcs.log (may just be a text document be named "dcs" if your Windows is hiding file extensions). And just to confirm, moving your head also moves the image on the mirror as though you were actually in VR?

One thing to be aware of that MSI Afterburner itself can cause micro-stutters in the game on AMD chips. This is due to the polling it does. The Power and Power Percent options there may potentially be the primary reason (folk can try turning those off), but just a heads-up in general. Overlays in general are bad.

@OMAR , there doesn't appear to be a game crash in the logs, may be Windows killing the process. Can you run the Windows DxDiag tool, save the report, and attach here as well. I see you also have some MFDs and ICP in there as well. Whilst there was a previous known issue with the Winwing ones (yours may be Cougar?), double check that you aren't running DCS as administrator. Can right-click on both the DCS.exe file and your shortcut you use to launch this and make sure "Run as administrator" is unchecked in the compatibility tab. I also see that your TacView is exporting files to your OneDrive. Disable TacView completely as well just to rule it out. Can't recall if TacView exports to this file as you fly, but might want to configure this to export to a different location in case it causes perf issues if it's synching to the cloud. Drop another log when it crashes again after taking those steps plus the ones from silverdevil. Check in your DCS logs directory as well to see if you have any dcs-logs-<timestamp>.zip files as they will have more info if DCS does crash, and not just Windows killing it.