DflippinK

I dont even know if it is possible,... but partly cloudy Thunderstorms would be amazing... unfortunately mission editor cuts off Thunderstorm options below Density level 9... i just went brain dead trying to find anything relative to weather other than textures in the main folder... is it even possible???

I think ive mentioned this before, but was hoping to get a little more insight on it... I am curious what the difference to hardware is when running Fullscreen vs. Borderless Windowed mode.. It is apparent via monitoring hardware utilization, that when in Fullscreen mode, there is an approximate increase in CPU utilization of about 5-10% and GPU utilization is approximately 10-15% less vs Windowed mode.. L-alt Enter into Windowed mode, CPU utilization drops and GPU load increases.. In the past, i had noticed some stutters would happen in fullscreen mode where they didn't in Windowed mode... now they both run silky smooth, but the utilization variances between the two still remain.. Makes me wonder what is going on internally and weather or not it could be advantageous for some users to run the game one way or another.. Would love to hear some thoughts on this..

Wow!!.. up to 6!!... or 1.6??.. figure 6 would cause some issues!!

thanks for replying guys... its been bugging the crap out of me... swear it was not that way in the previous update... i dont think i like it...

is this normal now?... i just re installed everything a while ago but now my front canopy has an orangish tint to it.. its like Summer up front and Spring on the sides... wtf??

did the front glass of the canopy around the hud get an orange tint??.... or did i screw up a .lua????

in the main DCS folder: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Config you can open the graphics.lua and tweak some of the settings in there and also edit the distance factors for each visibility range setting (Low, Medium, High, ect..) at line 330.. just be sure to backup the original graphics.lua so you can easily revert any changes.

ah yeah... the old 60,120,144hz dispute!!!.. there is no doubt a difference can be seen...Lol, lot of tense feelings about how critical it is though.. im good with a solid 60 though... its consistent... and until hardware or developers make it so we can lock it at 120 or 144.. thats probably where ill stay..

im guessing you are probably chasing MAX fps.. that will always bottleneck one of the two(CPU/GPU).. in 4k, around 75-80fps with all high settings and no MSAA, the 1080 ti is pretty close to reaching its threshold with DCS... if you tell it to go as fast as it can, it will try... 100%.. but if you set an acceptable goal for it,.. say 60fps (Vsync)... it will just do it... easily.. at about 70-85% load range with headroom to spare, and no lags or stutters of any kind.. and thats without the mod... with the mod, it will bring that down to 45-68% load range... but without setting any sort of frame limit (Vsync),.. it will always be pushing the card to its threshold... and manifesting the drawbacks that come along with doing so (variable frame rates, stutters, throttling, lags, ect)..

i use any of a few, but most often just have CAM and Task Manager or sometimes Afterburner open on my reference display as it gives me a basic and decent display of graphs... there are alot of options out there, mostly just revisions of Riva Tuner though..

yeah... i have fullscreen unchecked on my setup.. but i do see micro-stuttering and an increase cpu usage if i Lalt+enter into fullscreen mode while flying.. less so in the latest update,... but still there... in borderless windowed mode it runs smooth as silk though...

sure... i mean that sounds reasonable... im seeing an approximate 15% load reduction on a 1080ti..

well... the mod works... but you may indeed have other problems..

hit Lalt+Enter enter while flying and see if the stutter disappears.

perhaps you should try to repair or re install dcs... and then apply the mod.

try this 1. set settings to 2. exit game.. 3. default nvidia control panel.. 4. delete contents of fxo and metashader2 folders under C:\Users\Username\Saved Games\DCS.openbeta 5. set refresh rate to 60hz 6. start DCS.. fly!! if on 4k screen should be a solid 60fps if on 2560x1440, you can enable MSAAx2 and results will be approximately the same.. if on 1920x1080, and you have any issues, something else is wrong. Edit.. Be sure that Fullscreen is not enabled in game...

Nothing anyone has said here is incorrect... not as far as task scheduling, the way the game is actually composed of two "execution threads", or or weather or not those two "execution threads" can be processed by more than two cores... all of these things are true and always have been... the purpose of this was to bring attention to the fact that "we can" offload some of what the primary core often gets saturated with to another core therefore increasing its headroom and avoiding full core saturation.. obviously we can not break up the physics engine... but we dont have to... the system runs flawlessly with approximately 20% of the primary cores "execution thread" diverted to a different core..

dont know if you already saw this,, but here is a good hud mod for the hornet.. https://www.digitalcombatsimulator.com/en/files/3301130/

ok.. but what gets mitigated is primary core saturation... you want to not oversaturate the primary core... and this effectively achieves that.

nice!!

totally agree... im not posting this as a question really.. just to bring attention to things that are likely inhibiting peoples performance in hope that we can get some better results and smoother flights.. personally, i have no problems running the sim... except i like it when it more effectively utilizes the hardware that i have... which it does!!!... just have to tell it to... but for those who are running into massive lags when their primary core gets oversaturated or flatlined, the consideration of default affinity and core utilization might want a little tweaking..:thumbup:

well.... i would tend to disagree with that based on various experimentation and results... I have had DCS fully saturating one primary core and barely saturating the second (commonly default affinity)... and i have had DCS primarily utilize 6 cores drastically dropping the saturation of what would be the primary core effectively distributing the load... the result... no flatline on any core in heavily populated missions as can sometimes happen when the system runs DCS in its default affinity.. basically, it just does work on more cores... extremely well... but you have to tell it to at this point.

agreed... thats like trying to play DCS with a calculator... never gonna work.

i also noticed this with heavy fog.. and the same 'bubble' affects the grass as well... believe it has something to do with the adjustments in the atmosphere2 and tonemapping files of the mod but cant remember what i changed to mitigate the 'grassmosphere' issue while flying NOE in the gazelle..

thanks for lookin that up Floyd.. that is some good info... and it would suggest that ED does not even need to rework the core engine as it could likely be scripted to assign current particular tasks to a certain core...