Ahhh…Bummer….Jack Sparrow Carrier Ops were great fun last year
2 Likes
try reducing:
Res of Cockpit Displays 512x or 512 Every Frame
Scr. Space Shadows Off
Visibility Range Medium
Civ Traffic Off
Forrest and Scenery Details to .50ish,
Forrest Visibility to 50%
Clutter and Grass Slider to 1/3 from 2/3
Anistropic Filtering to 16x
If those fix some / all of the stuttering then it’s an object/draw count issue w/ DirectX
3 Likes
What? My impression was that screen shadows don’t care about object count? I thought they just draw shadows into the “flat picture” (screen space, as opposed to 3D voxel space)
1 Like
Anything Screen Space adds significant load to post process passes which in turn affects latency / frame time.
MSAA 2x/4x, Screen Space Shadows, Screen Space Reflections, Screen Space Ambient Occlusion.
2 Likes
Thanks for the help, Skate! Your settings are pretty close to the VR preset. They do work better but still a bit stuttery in the AH-64 Scud Busting mission–primarily (and understandably) at the beginning and near the target. It’s a mission that worked well for me in 2.8 with even higher settings so I think there might be something else that’s gone astray with my install. Because if others here were experiencing what I am experiencing, the pitchforks would be out for sure. I’ll try to repair with your app and maybe reinstall if that fails.
1 Like
theres Higher level LODs from some objects.
Of ED Added the C-RAM to that mission,
plus moving grass and foilage etc.
That must be it, at least partially. “C-RAM”. I had to look that up!
you dont wanna be on the opposite side with C-RAMs in the area.
Decreasing Clutter to minimum may help.
C-RAM, C-RAM, C-RAM, C-RAM, C-RAM, C-RAM, C-RAM, C-RAM
Lovely C-RAM! Wonderful C-RAM!
Lovely C-RAM! Wonderful C-RAM
C-Ra-a-a-a-a-a-a-am
C-Ra-a-a-a-a-a-a-am
C-Ra-a-a-a-a-a-a-am
C-Ra-a-a-a-a-a-a-am
Lovely C-RAM! (Wonderful C-RAM!)
Lovely C-RAM! (Wonderful C-RAM!)
Lovely C-RAM!
C-RAM, C-RAM, C-RAM, C-RAM!
2 Likes
Status update on the stuttering issue. One of my viewers left a comment on my comparison vid with possible solution:
You need to launch the DCS in multithreading mod, than start flight on the runway/on the parking apron, pause the game, open task manager, right click on DCS > click on Go to details > right click on Set Affinity > disable half of the cores, click ok > resume game, again pause game, enable all disabled cores and disable other half of cores click ok, resume game, pause game again and enable all of cores click ok resume game and it shoul be working without stutter, for me it’s also working whan I only disable and enable the last core
I applied this method and weirdly enough DCS 2.9 works buttery smooth for me now 
3 Likes
Ugh.
3 Likes
I see what ya did there!! 
1 Like
Holy mother of c-rams and other gods! That is the most convoluted thing I have ever read on Mudspike!
But…being a loyal Mudspiker, I can’t wait to try!
[EDIT]: Yep, works! I just do what @damson did (1 core off, go to game, core back on, go to game).
3 Likes
Holy Carp that’s bizarre. Thanks for sharing, I will give it a try next time.
The things we do for love DCS…
3 Likes
This worked for me, I found that I need only to disable the last core and then enable it back again, also there’s no game pausing needed. After that no stutters. Seems like thread scheduling seems broken in DCS? The only caveat is that I need to perform this “fix” each time I load a mission. I can live with that for now. Hope it will be fixed soon.
2 Likes
does your CPU have E cores?
the stuck thread 08 and such is being looked into.
1 Like
No, my CPU doesn’t have E cores, it’s Intel Core i5-6600K.
As a public service announcement, because this happened to me when I upgraded to my i7-12700k, for anyone with an Intel CPU with both P- and E-cores:
RUN WINDOWS 11.
Windows 10 does not have the updated CPU scheduler that allows it to use E cores effectively. What 10 will do is throw stuff to the E-cores that it should not.
When I first tried gaming I noticed stuttering, hitching, and generally frustrating unpleasantness. After researching it and discovering it was a Win10/E-core thing, I disabled my E-cores in the mobo BIOS until I upgraded to Win11.
Win 10 running only on P-cores is a better experience than with both. Win 11 with both P- and E-cores is better than P-cores only.
4 Likes
just tried the F18 … deployed gear at about 500kn … gear came down fine, but lost main gear doors (not sure what happened to them but a georgian farmer may have some new holes in barn roof )
gear then functioned normally, retracting fine apart form annoying buzzer telling me that the main gear doors were open…(or more likely in a field somewhere) … then deployed and landed fine
5 Likes