DflippinK

when installed correctly, the first start of DCS will take a very long time to load as it rebuilds new shaders in the FXO and metashaders2 folders.. it will hang for about 5-10 min on the first DCS splash screen... and it will hang on the first mission loading splash screen... after the first DCS session with new shaders built, it will load at normal speeds...

yeah... problem seemed to have disappeared.. might have happened with last update.. in any case, all is well now.

Its all about affinity... desaturate that primary core... spread it out... even if it means inducing thread hopping.. contrary to popular belief,... it will run better than saturating that one core that it does by default.. Process Lasso can work well at times... but i have found that deselecting all cores in task manager and then selecting 3 three consecutive cores will evenly divide the load across the 3.. then re-enabling all cores will yield 4 cores running at half the saturation of the default 2... works very nicely and handles heavy battlefields well... hopefully sooner than later DCS will get properly scheduled to more cores.. but for now, just force it.

yes that is approximately correct.. cpu seems low, but it is heavily saturating one core while doing mostly nothing with the others.. this will likely be the cause of most of your stutters... either that one core getting overly saturated, or your GPU running at its limits.. both can be mitigated with a bit of work though.

just with them loaded.. stutter city. havent tested them on the last update yet though.

i concur... while there are hardware issues and config issues, time and time again i have watched performance degrade over time to ultimately be remedied by a install repair or a clean install...

totally agree... was tryin to tell people this a while ago... but a lot of folks seem to demand that they need 99% GPU for some odd reason... Rather have 100% solid FPS at 50% GPU utilization running cool and comfy than havin 50% variable FPS at 100% GPU runnin at 90c... hahaha.. Just set your refresh to 60hz in nvcp and turn on vsync in game... solid 60 fps with everything pretty much maxed out..

welp.. not sure i understand that logic.. 99% means you really have no headroom left for whatever the game might throw at the GPU... i would prefer 480fps, maxed out settings, and 14% GPU utilization..... @45c... might have to wait for some optimizations though.. Lol.... :)

you cant set a refresh of 60hz on a 144hz gsync monitor in nvidia cp right next to resolution settings???

noticed with no other variables on the same mission, DCS is stuttering terribly when the hornet is loaded with a couple of AGM-65's... but smooth as silk without them.. any ideas??

For 4k.. 1080ti run flat shadows for both "shadows" and "terrain object shadows" high everything else MSAA=Off DepthOfField=Off Lens Effects=Optional Motion Blur=Off SSAA=Off Max out all sliders AF=16x Cockpit Global Illum=Optional VSYNC=ON--- either in game or via Nvidia CP-- set to 60fps refresh. Provided you have adequate airflow, your GPU will never go above 60c and your frames will never drop below 60fps. GPU load will average around 70-75%...:thumbup:

you will easily get 60fps on a 4k screen, vsynced, with everything pretty much maxed out, flat shadows, and no MSAA... with MSAAx2, you will get mostly 60fps with an occasional dip due to GPU... on the ground, you may see frames drop here and there while taxing around the airfield due to CPU.. if you use kegety's mod, you will easily run the game at the cost of some visual fidelity which is easily forgettable.. i expect you to have no problems... this is my experience on a 1080ti and a R7 1800x w/ 32gb ram...

could it be shadows cast by the clouds?

lot of new lines in the Decoder.hlsl file from the update...

yep.... should be a loadout option in fast mission without having to go to mission editor... every time it creates a mission with no weapons... well.. you do have the canon.. but nothing else, and no "fast" way to mitigate that..

yep.. ps3 eye... also.. you dont even have to remove the filter.. just get some red and blue color gels and place them in front of the lens... will filter out just about everything except ir.. you can cut a hole in a bottle cap and stack the gels inside of it to make a quick removable ir filter to just place over the lens.

i use Opentrack with a clip.... works extremely well.

yes.. the instructions within the readme.txt of the mod are all accurate and work every time.. just do it in a procedural manner.. also, i think people may be getting confused or forgetting steps when trying to implement with Ovgme.. but you can always refer back to the readme.txt for reference.

well.. at one point i screwed up a new install by overwriting its new Bazar file folder with the old one from the previous build... other than a corrupted install, i cant really imagine why it isn't working... unless somehow your mod files are corrupted... or if you have something in the saved games folder that may be somehow affecting it.. did you clear out your fxo and metashader2 folders before re installing the mod?

GOA,.. forget everything... 1. set refreshrate to 60hz in nvidia control panel 2. turn off any gsync features. 3. do not use nvidia cp vsync settings... yet. 4. set nvidia CP options to default. 5. check Vsync in game 6. uncheck fullscreen in game 7. Test flight... you should be locked at 60fps with zero stutters..

Hey Neal,.. try disabling all mods.. and doing a repair of the dcs install.. then start dcs in stock form and make sure all is working correctly... then exit and re enable the mod...

well... you stated previously that you had different readings between afterburner and Task manager.. but you shouldn't.. i dont run all the apps at the same time.. actually, sometimes i do.. but each has its own set of functions and uses... either way, you cant have two different CPU readings that are supposed mean the same thing... so.. your numbers need to match up between whatever you are using to measure.. otherwise, its not an accurate measurement.. could be do to sensor id's or conflict between or among tools.. thats all i mean.:)

afterburner is ok.. as long as all your numbers match up... otherwise you have a conflict or one of your monitoring tools has an invalid sensor assignment... I also use HWmonitor and Aida64.. but all my numbers match up in each.. so i cant really argue with that.. but i run all of this on a reference monitor.. for OSD on my main screen ill just use CAM from time to time... usually just have all my monitoring running on the monitor to the left though.:pilotfly:

it does look like a difference in your OSD and TM values... could just be different sensors being averaged between the two... and yes, sorry.. Precision X does only report GPU usage... but also reports the GPU load the same as TM and CAM..

just checked.... but on my system, im not seeing any variances between monitoring softwares... task manager shows the same result as CAM monitor and Precision X.. CPU high/GPU low in fullscreen, and CPU low/GPU high in windowed..