DflippinK

ok it sounds like you are doing well with settings... and no you do not need anything faster than an 850evo... and sorry i thought you were on win 10.. when you re installed your Nvidia driver, did you use DDU from Wagnardsoft? https://www.wagnardsoft.com/

what happens if you do not use Nvidia gsync or vsync settings and set refresh rate to 60hz, enable DCS in game vsync and run in Borderless windowed mode?

for a standard monitor, you should be running 60hz.. 1.do you have an Eco mode switch on your power supply? 2.when was the last time you updated your chipset and motherboard drivers? 3.are you running any monitoring software for GPU (MSI Afterburner or Precision XOC)? 4.Which driver are you running for the 1070 and how was it installed? 5.Are you using Nvidia Geforce Experience or any of its features? 6.what are your settings in Nvidia control panel? 7.What are your power options set to in Windows 10? 8.Which build of Windows 10 are you running 9.How many processes do you usally have running on your system? 10.When was the last time you uninstalled and re-installed DCS open beta completely including removing it from your user/saved games folder?

does your laptop have an iGpu in addition to the 980m?

i understand.. just racking my brain on what aspect of win10, nvidia, or DCS would be causing the conflict... is your in game resolution set to your actual display resolution of 1080p... or are you attempting to scale a different resolution to fullscreen?... if you are scaling resolution you could be causing a conflict with win10 display settings... also attempting to use nvidia DSR scaling can have similar effects.

What happens if you run DCS at full resolution Borderless Windowed Mode (aka Fullscreen Un-checked in game)?

Agreed... but credit for drivers in this thread must go to @David OC... and completely agree with that advice as well.. DDU is the optimum means of clean driver installs...

uh oh... insider build... did you try a repair of dcs install?

your setting look to be pretty achievable... might also want to 1.try maxing out your preload radius... 2.and maybe getting rid of motion blur and dirt and flare temporarily.. if that doesnt yield any better results, you may want to 3.Repair DCS Open Beta, 4.Reset Nvidia Control Panel options to default, 5.delete fxo and metashaders2 files and let dcs rebuild them the next time you start it... and then test setting again... 6.and sometimes, its just a good idea to uninstall and re-install DCS.. but id say try it in that order... one by one. also, i would recommend using Vsync unless you are trying for higher than 60fps for some reason. additionally... as stated by the previous three posts, the Shadows are bitchy... go with flat.

[quote=Gripes323;3531364 The minor stuttering that I used to have on my rig disappeared when I uninstalled Intel's turbo boost or it might have been just a coincidence. wonder if it had anything to do with HPET high precision event timer..

This is my setup... 50" 4k main & 1440p reference.. with opentrack tracking setup.. spotting might be difficult.. and the zoom warp is not pleasing.. but other than that, its pretty damn sweet.. srry for the terrible pic.. tablet camera doesnt do the screen justice.

interesting... seems like if i attempt to push through a turn at sub 400knts or stall the f-15c, it will bash my virtual eyeballs over every surface of the cockpit..

K... cool... i thought maybe i was trippin... but it does seem absurd... tried to modify the shake amplitude in the F-15C .lua file where it says "do not edit".... didn't work... barf.

been flyin the Hornet since the last update.. but jut went to do a flight in the F-15 and noticed its simulated shake is seemingly violent now... anyone else notice that?

Yep.. that looks about the same as what im getting... that primary core takin the heat.. thanks for the vid Beasty.:thumbup:

nice find!!

Sounds about right... would prefer less saturation on one core though.. at times my prumary core is completely saturated and all others are basically sitting idle... with the hornet, it is much more so than with ither modules... but it seems we have different result on other systems.

I observed the same..

well.. DCS supposedly runs on 2 cores, but can assign usage to more cores when needed if understand correctly.. Tools like process lasso can in some cases distribute utilization across more cores and and lighten the load on the primary core... On my system, with the Hornet, i have one core being pushed very hard at times processing all the game data, and one core processing audio.. but others seem to have thier load spread differently, and i imagine more optimally for the sake of performance..

Whoa!!! now that looks good... how did you manage that utilization... looks almost evenly distributed on every core!!

Interesting, it looks as if you have a bit more utilization on you other cores... but only after the primary core is completely saturated... Does it seem that DCS always uses the same core as the primary for you or does it alternate?

Just wanted to see how others CPU's are handling the Hornet.. if you can, post up a pic of your Task Manager CPU tab with graphs set to logical processors while flying a mission.. mostly want to see how saturated the Primary core gets...

:thumbup:

...well, i just run in game vsync locked at 60 and run in borderless windowed mode.. no tearing over here... but there is the strange cpu utilization that occurs if the game is run in fullscreen mode.. it just uses more cpu for some reason in fullscreen..

Hey Mack, any chance you could post up a screen cap of Task Manager CPU performance tab while in flight?... im curious how the utilization is being spread among the cores on your system.. On mine, it is using 2,.. but the primary core is more saturated as of the 2.5.2.18144 update..