solved Stutters & jerky movement

[MadKreator]

22 minutes ago, Reflected said:

@MadKreatorThanks, so it’s not that it can’t go higher, it’s just not needed? I never had a computer this powerful so maybe I’m just surprised to see a cpu not running at max. 
 

as for the pagefile I have no idea, somebody told me once…but now I set it to 32. 

Yup you will rarely catch it running full bore. Usually it will only boost for a few seconds if it needs it here and there. I thought the same when I finally upgraded mine too…. Wait a minute it only runs at 15%?!?! .. Doing 3d rendering, rendering videos/ movies and things like that, you will prob see some pretty high clock speeds though…  BTW I just saw a video of yours about how you think about and make campaigns. Very impressed at your thought process and thoroughness. I’m usually not a campaign kind of guy but after seeing that video, I bought all of yours that you have out

Edited September 3, 2023 by MadKreator

[Reflected]

Many thanks, I really appreciate the support!

I've been checking the usage % and it does go above 15% periodically - when needed I guess.

[speed-of-heat]

so usage and clock speeds are not really directly connected.  You can have a high clock speed and a low usage... (indeed depending on your cooling solution/etc...  as the number of cores utilised increases the clock speed is likely to decrease due to thermal throttling of the processor) in the performance tab of the task manager for example, the usage is about the number of cores being utilised, the speed is how fast an individual core will run when its working. 

[vgilsoler]

On 9/1/2023 at 11:23 AM, vgilsoler said:

I did a test yesterday with a simple mission I use for aiming training (a FW190D9 VS a B17G)

Usually I get some stutters when B17G gunners start to fire for first time. With MultiThread the FPS drop, but in SingleThread the issue is with sound.

I tested the config provided by Reflected adjusted to my rig

-GPU scheduler OFF

- Vsync off in game

- Vsinc on in NVCP

- Triple buffering on

- Limited my FPS to 60 in the NVCP

I deleted fxo and metashaders2 folders.

After that the first time I launched the mission in MT the stutters went away, but the second time I launched the mission they came back again.

Later today or during weekend I'll repeat the mission to confirm the results.

It seems the general result is a smoother game.

[Reflected]

After having limited my FPS to 59, DCS is silky smooth, except when the mission starts. Around the airfield it seems like it spikes when loading textures. After 5-10 minutes these spikes go away. See below. What can cause this?

 

EDIT: it seems to be directly related to preload radius. If I set it as low as 20-25k, then I don't get any of these spikes. But that's weird, I have 32GB RAM and a 32GB page file, so what's up with it?

 

Edited September 14, 2023 by Reflected

[speed-of-heat]

im not sure, but do you get spikes if you move into those areas? Have you set up XMP profile for your RAM ? 

[Reflected]

1 hour ago, speed-of-heat said:

im not sure, but do you get spikes if you move into those areas? Have you set up XMP profile for your RAM ? 

I haven’t heard of xmp profiles. Should I set one up?

I get spikes for a few minutes after spawning and looking around. Then once I cross the channel for example and reach France, new areas new textures. Over water I have zero spikes

[speed-of-heat]

How to enable XMP to run your RAM at full speed | PCWorld for more information, usually you need to go into BIOS and set the profile to XMP

[Reflected]

I have no xmp in BIOS, it’s an asus laptop though.

Edited September 14, 2023 by Reflected

[Reflected]

Update: I tried disabling Hyperthreading in the BIOS, it made it a lot worse.

Then I tried to set preload radius to max, and surprisingly, the initial spikes were gone...weird...

[speed-of-heat]

obviously sacrificing the chicken worked ... 

[zildac]

obviously sacrificing the chicken worked ... 

[Flappie]

3 hours ago, Reflected said:

Then I tried to set preload radius to max, and surprisingly, the initial spikes were gone...weird...

This might point to a sluggish drive, for I believe the point of the Preload Radius is to load a larger portion of the map into RAM, to avoid frequent copy from drive to RAM.

[Reflected]

5 hours ago, speed-of-heat said:

obviously sacrificing the chicken worked ... 

I knew it!!!

4 hours ago, Flappie said:

This might point to a sluggish drive, for I believe the point of the Preload Radius is to load a larger portion of the map into RAM, to avoid frequent copy from drive to RAM.

Anything I can do about that? Is ot my C drive where my saved games folder is or my D drive where DcS is installed?

Edited September 14, 2023 by Reflected

[Flappie]

7 minutes ago, Reflected said:

Anything I can do about that? 

Run CrystalDiskInfo on your system drive, then on your DCS drive. Take screenshots of the results and post them here, with your dxdiag log. We'll see if your drives speeds are normal.

Edited September 14, 2023 by Flappie

[Reflected]

3 hours ago, Flappie said:

Run CrystalDiskInfo on your system drive, then on your DCS drive. Take screenshots of the results and post them here, with your dxdiag log. We'll see if your drives speeds are normal.

 

Here you go:

 

DxDiag.txt

Also:

[Reflected]

And btw the stutters are back and actually worse with preload on max. I'm out of ideas. It wasn't this bad on my previous laptop but now that I have a lot of FPS, it stutters...

[Reflected]

Here are my Nvidia settings:

null

 

[Glide]

Try Shader Cache Size Unlimited.  Try HAGS on.  Try setting maxfps to 60 in your autoexec.cfg (see graphics.readme in Config)

Try increasing Virtual Page File size.

INCREASE THE VIRTUAL MEMORY (PAGEFILE) ON YOUR SYSTEM

• In the Windows Search bar, type Advanced system settings and open the Control Panel.
• Make sure you're on the Advanced tab.
• Click the Settings button from under the Performance
• On the Performance Options box, go to the Advanced tab > Performance
• Click on Settings
• On the Virtual Memory box, uncheck the Automatically manage paging file size for all drives
• Click to select the drive on which Windows 10 is installed (by default C:)
• Click to select the Custom size radio button.
• In the now-enabled fields, type the minimum and maximum size of the Pagefile in megabytes (MB) according to the physical memory present in your computer.
• Click Set and then click OK.
• Restart your computer.

Mine is min 5120 max 32768

Edited September 15, 2023 by Glide

[Flappie]

I second @Glide on this.

Your dxdiag shows you have 32GB of RAM which is not enough for DCS unless you have a good pagefile. Try these settings for the pagefile:

Init size: 32768 (32GB)

Max size: 32768 (32GB)

And don't forget to lower your Preload Radius setting in DCS (default is 60000 or 65000).

[Reflected]

I already have a 32 page file. My previous laptop also had 32GB RAM and it didn't stutter.

I turned HAGS on, no joy. Most places recommend turning it off?

I lowered my preload - doesn't change anything

What about fullscreen mode? Should it be on or off?

Edited September 15, 2023 by Reflected

[Flappie]

47 minutes ago, Reflected said:

I already have a 32 page file. My previous laptop also had 32GB RAM and it didn't stutter.

Sorry, I misread the numbers:

Page File: 8047MB used, 57148MB available

It amounts to 64 GB (at the time your dxdiag log was generated) which seems too much. You should stick to 32GB.

Maybe you have 2 pagefiles on 2 separate drives. Please run this command in a "cmd" window, and paste the result here:

wmic  pagefile list full

 

55 minutes ago, Reflected said:

What about fullscreen mode? Should it be on or off?

Fullscreen (or the absence of it) is not known to cause stuttering. I let it off because I Alt+Tab very often when testing things.

 

[Glide]

Try one of the canned missions like Hot Start from Batumi in the TF-51D.  That would rule out the map and the modules in your test mission.

[Reflected]

null

 

but

null

[Glide]

One other thing you may already know, but just in case, to clear the Nvidia Shader cache, set Shader Cache to disabled in the NCP, reboot and either run the cleanup util or do it by hand.  Shader cache files that are "in use" can't be deleted.