July

Ok, since there have been no .trk files supplied showing off just how crazy the drag profile of the AGM-154Cs are (afaik the AGM-154A does not behave the same "broken" way) I am uploading one here. All four AGM-154Cs were released at +95NM, with all 4 hitting an arbitrarily selected waypoint just for demonstration purposes. All four also successfully completed pop-up attacks, from as low as 200 ft MSL. If you do happen to watch the .trk, please let me know what you think. (Yes, the two JSOWs that loft into 40k ft do end up smashing the same targeted waypoint.) AGM154C GLIDE.trk

Ah, it IS on. I will try turning it off and report back with findings later.

One thing I've noticed sometimes while flying is that DCS seems to make my Windows 10 think that I'm in a phone call and mutes/lowers all other sounds while in-game (Discord, Music, basically any other app) even with my communications setting in the Sounds Control Panel set to "Do Nothing". The problem is fixed through going to my sound control panel and manually cycling through the other options, then back to "Do Nothing" to get my volumes back to normal. This happens only in DCS. Has anyone else been experiencing this?

With "Head Movement by G-Forces in Cockpit" on, is there a way to change some values in a .lua somewhere (like View.lua) to reduce the amount of head movement while maneuvering? I've been able to find some threads out there from many years ago (some going back to 2010) discussing how to change the amount of head roll by editing head_roll_shaking in View.lua, but now it seems to do nothing. Also, before anyone asks, I am NOT looking to completely turn the head movement by G's off.

Track file here. https://drive.google.com/file/d/1bsNYBC-Htkz0ZgVHRMS5sBlPp2SLA_nn/view?usp=sharing Edit: I've tried to watch this .trk myself, turns out I can't due to some kind of error. Potentially because the .trk is from a multiplayer game. I have no idea how to replicate the bug, nor do I know any steps related to the bug appearing other than being in A/A mode. Hopefully this .trk works for someone else.

Bumping this thread, this behavior definitely can't be considered correct can it? As Jak as previously stated, the bar options are all shown despite no TDC placement. This leaves us unable to see what bar scan we are in for both TWS/RWS. I can attach a .trk if needed.

Whether or not this bug is tied into specific attributes like weapon loadout has yet to be seen. However, I can say that I have experienced this problem no matter the ordnance. The bug persists even on a clean aircraft.

+1 I don't have a .trk file handy atm to show but have a tacview if anyone is interested, but I have personally been able to get 120NM hits with the AGM-154Cs from doing a manual release while seeing the same behaviour stated above. I am almost certain they can go further, terrain permitting.

(OB vers. 2.5.6.59398) I've been seeing some odd AMRAAM behaviour lately (could be as a result of this new OB patch?) against targets that begin to pop chaff, the missiles in this particular case (towards the end of the .trk file) seem to have been tracking their targets fine, then all of a sudden go for chaff. In this .trk, one missile even pulls ~23.0G. Is this normal behaviour? I'd like to get some thoughts on this. Attached below are both the .trk files and tacview. https://drive.google.com/drive/folders/1CfZ_Cn6XHBQcQ5Xko9aCVnn2I_tnqQHA?usp=sharing Tacview-20201219-011251-DCS-Caucasus - Coiled Derp.zip.acmi

@glide Screenshots below.

Closing OneDrive, and uninstalling Nvidia Share seems to have gotten rid of some (maybe most?) of the stuttering. Pagefile still sees use and causes stuttering when things pop in like aircraft, trees, and buildings.

Game bar DVR has always been off. So now I feel pretty stupid for not realizing that DCS was actually using pagefile on my HDD. With pagefile disabled for my E: drive, I'm seeing improved performance across the board. Still having stutters during active pagefile usage, screenshots below. Edit: Could this be a product of not having enough RAM?

With Nvidia Share off (for real this time), the frequency and length of the stutters has lessened considerably but are still present. Significant pagefile usage here.

I'm reading online that this temp directory in my AppData that's using up my disk read/write is related to Nvidia Shadowplay/Share, I thought I had disabled it but somehow it continued running in the background. I may try uninstalling it. Will report back with results once again. Here are the relevant threads I found this info in: https://www.reddit.com/r/techsupport..._emptying_out/ https://www.reddit.com/r/techsupport...d_drive_and_i/

Testing was done on Syria, but the stuttering is consistent on Caucasus and Persian Gulf as well. **This was done with Nvidia Share both on and off, with no appreciable difference.** I have tried deleting my fxo and metashaders2 folders in the past, again, with seemingly no gain. Deleting the contents of the NV_Cache folder is something I had yet to try but after doing so I was still getting the stuttering. Edit: All screenshots were taking during or 1-2 seconds after the stuttering (which themselves lasted minimum of 2, upwards of 15 seconds) Edit 2: D: is Windows System reserved partition (which should be a part of my SSD (C: )), E: is my HDD **Turns out, Nvidia Share continued to run and record in the background despite me turning instant replay off and making sure it wasn't recording so these results are somewhat invalidated

If you mean Windows Defender, no. I have not tried with it off yet. I will try disabling it and will report back.

I have already gone into safe mode for testing as Flappie suggested. It disables networking.

I do have an HDD, but only use it to save videos/clips. I am not using a NAS. The stutters continued to be present even after disabling NVIDIA Share. Afaik, my pagefile is correctly used on my SSD.

I will try, but the stutters have been present even before I enabled Nvidia Share ~3 weeks ago. However, I will still try with Nvidia Share disabled once again. I'd like to also note that during the stutter, GPU usage drops to 0%, and in task manager a system process begins using 100% of my disk. Going into the task manager details for the process says that the process is named "System", and when I open the file location of the process it leads me to "ntoskrnl.exe". From what I've read about the process, it potentially has something to do with my pagefile?

Here's the tasklist. process_list.txt

Should I make a new thread then or continue posting here? I have tried changing the size of my pagefile manually, from setting it down to 2 GB, 4 GB, because some people on this forum have said it fixed their problems (which others say is stupid, and to continue letting windows manage it instead). I have also tried changing the pagefile size all the way up to 32 GB as well. This did not fix the problem. dcs.log

Hey, I hate to dig up a somewhat aging thread, but I've been experiencing the SAME EXACT problems as OP here and also tried all of the same solutions he has tried including some extra ones from the forums only a few of which helped alleviate the problem somewhat (again, just like OP). I am completely at a loss now. This happens in both singleplayer and multiplayer (crowded or not crowded by actual players, seems to make little difference). I used Process Lasso to change CPU affinities as per some instructions on the forum. This did not do much, and sometimes even seemed to worsen the issue. I have also tried raising the priority of DCS but also seemed to do little or nothing at all. I do not have MSI Dragon Center. My current antivirus is only Windows Defender. I do not own a WinWing HOTAS, and this issue has been occuring since before I acquired my new stick (VKB GNXT). I've also gone through the safe mode test and after ~30 mins of flying around in an SU-25T, I experienced very little stuttering (obviously). This was likely due to the low VRAM usage combined with low RAM usage from being in singleplayer with no other applications running. VRAM usage was ~7GB, RAM usage only peaked ~9.5GB (checking with Afterburner). Yes, I know my current settings are somewhat high, but I have tried extremely low preload radius settings, lowest trees visibility, all low textures, pretty much every setting on low, and while it does reduce the frequency of the stuttering somewhat, it always returns. For what? A big hit on visual fidelity for a setup that usually averages +60 FPS with the settings you see in the screenshot for most scenarios anyway (except on Growling Sidewinder). CPU: i7-7700K GPU: 1080 Ti (11GB VRAM) RAM: 16GBs GDDR4 @ 3200mhz SSD: Sandisk Z410