Jump to content

Extreme frame drops (80=>1) after about 8-10 minutes


M0RKILLZ

Recommended Posts

 

 

The text below is pasted from a reddit thread I posted in r/hoggit. here is a link to the thread.

 

 

In addition the the information provided below, in the comments I posted a screenshot of my RTSS overlay once the stutters happened.

 

 

I also tried halving the preload, which seemed to postpone the onset of the issue but did not stop it from occuring altogether.

 

 

There is also a log file attached to this post, hopefully it will give you some insight better than I can.  Any help would be appreciated!

 

 

 

Basically, the problem is that, after 8-10 minutes of playing the game, my FPS will go from a steady 60 to an unsteady 2. Most of the time, it's more like .25, and it makes the game absolutely unplayable. This happens on the Caucausus map, when playing the default mission. I am flying the SU-25. The tutorial missions worked fine, however, there was next to nothing happening on them.

Specs: the deep dive:

CPU: 2700x

-OC'd to about 4ghz.
-Currently restricting DCS to running on processors # 12 and 14 using process lasso.
Was previously allowing them to use all cores, but the issue existed then as well.
-Cooled by an H100iv2 AIO.

GPU: MSI GTX 1080 Gaming X:

-OC'd to 1936MHz
-Running around 62C
-Running latest drivers (461.9)
-Drops to about 2% utilization after 8-10 mins apparently

RAM: 32gb Trident Z 3000:
-Running at 933MHz according to task manager
-OC'd to around 3200MHz IIRC

Storage: 860 Evo SATA III SSD:
-Has around 23GB free

Display: Dell S2716DG 1440p, 144hz
-G-Sync: Off (was on before, didn't help)
-V-Sync: On

Display 2: HP 22cwa:
-Disabled, was enabled before but still doesn't help

Windows version: 10, latest build.

Game version: Latest, Steam Edition, Installed for first time yesterday
-Textures, Terr. Textures, Water, Visib. Range set to high
-Heat blur, MSAA, DoF, MB, SSAA, SSLR, Cockpit Illum, VSync, Droplets set to OFF
-Civ traffic set to medium
-Anis Filtering set to 8x
-1440p
-Fullscreen on
-Clutter: 0
-Trees vis: 50%
-Preload radius: Max
-Chimney smoke density: 4
-Display res: 512
-Shadows: low

I have tried the following:
- Disable windows antivirus
- Add exception for DCS in Avast antivirus
- Disable hotplug
- Turn off MSAA
- Limit frames to 60
- Used process lasso to try and maximize DCS' utilization of 2 cores
- Delete the fxo and other files

The end result is always the same. Sudden onset, unending massive frame drops that absolutely eliminate the game's playability. Also, SU-25's autopilot seems to be nonfunctional.

Any ideas? I have a Oculus Rift S on the way, was hoping to use it for this game. However, as unplayable as it is currently, I might have to go back to WT.

 

dcs.log


Edited by M0RKILLZ
  • Like 1
Link to comment
Share on other sites

Try lassoing 4 cores... and make sure they are physical cores, dcs normally tries to use 3 or maybe 4, whenever I tried to limit to 2core my perf was always less... also no matter what the process lasso marketing says, the only useful thing you can do with it is turn off the logical cores from being used by a particular app; unless you have a damaged core and you want to avoid it...Trying to do cpu scheduling by hand is a complete mugs game.

 

physical cores start at 0,  then 2 then 4 etc... 

 

also check your temps, it’s possible you are overheating, if the AIO is new then it might be something wasn’t installed correctly?

 

finally your ram looks odd, but just try setting it to the xmp profile? 

 

SYSTEM SPECS: Hardware Intel Corei7-12700KF @ 5.1/5.3p & 3.8e GHz, 64Gb RAM, 4090 FE, Dell S2716DG, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

YOUTUBE CHANNEL: @speed-of-heat

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

Link to comment
Share on other sites

25 minutes ago, speed-of-heat said:

Try lassoing 4 cores... and make sure they are physical cores, dcs normally tries to use 3 or maybe 4, whenever I tried to limit to 2core my perf was always less... also no matter what the process lasso marketing says, the only useful thing you can do with it is turn off the logical cores from being used by a particular app; unless you have a damaged core and you want to avoid it...Trying to do cpu scheduling by hand is a complete mugs game.

 

physical cores start at 0,  then 2 then 4 etc... 

 

also check your temps, it’s possible you are overheating, if the AIO is new then it might be something wasn’t installed correctly?

 

finally your ram looks odd, but just try setting it to the xmp profile? 

 

All of your suggestions were covered in the thread. They aren't a factor.

Link to comment
Share on other sites

Hi @M0RKILLZ. Your log shows the symptoms of a heavy slowdown, indeed:

 

2021-01-24 00:53:56.885 ERROR   SOUND: render time = 0.133350s exceeded allowed slice of 0.022000s
2021-01-24 00:53:57.030 ERROR   SOUND: render time = 0.051869s exceeded allowed slice of 0.020000s
2021-01-24 00:53:57.811 ERROR   SOUND: render time = 0.057093s exceeded allowed slice of 0.022000s
2021-01-24 00:53:58.245 ERROR   SOUND: render time = 0.099105s exceeded allowed slice of 0.010000s
2021-01-24 00:53:58.395 ERROR   SOUND: render time = 0.069681s exceeded allowed slice of 0.022000s
2021-01-24 00:53:58.455 ERROR   SOUND: render time = 0.018959s exceeded allowed slice of 0.010000s
2021-01-24 00:53:58.501 ERROR   SOUND: render time = 0.023831s exceeded allowed slice of 0.020000s
2021-01-24 00:53:58.732 ERROR   SOUND: render time = 0.137215s exceeded allowed slice of 0.010000s
2021-01-24 00:53:58.749 ERROR   SOUND: render time = 0.015680s exceeded allowed slice of 0.012000s
2021-01-24 00:53:58.907 ERROR   SOUND: render time = 0.056401s exceeded allowed slice of 0.022000s
2021-01-24 00:53:59.109 ERROR   SOUND: render time = 0.071972s exceeded allowed slice of 0.010000s
2021-01-24 00:53:59.156 ERROR   SOUND: render time = 0.045848s exceeded allowed slice of 0.012000s
2021-01-24 00:53:59.446 ERROR   SOUND: render time = 0.112379s exceeded allowed slice of 0.022000s

 

It might be a storage and/or pagefile issue. Please provide the following things:

  • dxdiag log (here's how to make one)
  • Launch "cmd" utility, run the following command and paste the result here: wmic pagefile list /format:list
  • Last but not least, run the Windows Resource Manager (command "resmon"), maximize the window, go to the "Disk" tab, launch an instant action mission, Alt+Tab to the Resource Manager, tick "DCS.exe" in the above list, take a few screenshots and post them here.
  • Like 1
  • Thanks 1

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

@Flappie

 

Result of command prompt:

 

AllocatedBaseSize=4096
CurrentUsage=97
Description=C:\pagefile.sys
InstallDate=20210110110425.008750-360
Name=C:\pagefile.sys
PeakUsage=356
Status=
TempPageFile=FALSE

 

 

I also have the screenshots you requested, in addition to a repost of a RTSS screenshot I had of my system during stuttering last night. The final pic is what the cockpit view looks like. It's worth noting that I flew over other towns prior to this one with no issue.

Thanks for the help and good luck!

On the ramp

after takeoff, prestutter.png

After takeoff but before stutter onset

on ramp.png

Stuttering occurs

stuttering.png

testing.png

in the air.png

DxDiag.txt


Edited by M0RKILLZ
Link to comment
Share on other sites

Thank you. Your disks response times are OK (~2ms).

Now:

 

1/ Try the same thing without ticking DCS.exe app (you'll get the full list), and see if another process is actively accessing your DCS files when stutters are here.

2/ Nothing? Then try the "CPU" tab and see who eats up all the CPU.

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...