Boosterdog

Thanks Limaro and Flappie.

And Limaro with his thorough efforts. Thank you!

Didn’t say it was a solution. I simply reported what occurred. It may work for some or for no one. Just figured it was something to try instead of pontificating about shit on a stick as I normally do.

@BIGNEWYit wasnt. I went ahead and downloaded the stable update. General performance accross missions with no change and identical settings between beta and open and identical stock saved games folders (carried over form the old stable) etc has resulted in a consistent 8-10fps INCREASE across the board. Still about 10fps short of the old stable but now on par if not slightly over with the 2.7.6 Beta. So somat is different or (uneducated and wild speculation) sommat is misfiring within the update that isnt being picked up with a repair.

@BIGNEWY. I now also have my original I5 machine plus a new, virginal Ryzen one if there is anything a comparison of hardware or old v new OS may help with. Should be up and running with both from Monday.

Some of us have given you this already. I assume we dont need to further clog the forum with individual examples. I can fully appreciate the frustration on your part but equally, without any meaningful direction from ED (other than the ususual advice for a botched update fix), threads such as this will always wander and become bloated piles of hoodoo sadly.

....and without an acknowledged or understood reason.

@BIGNEWYsame here

The hind is I think the only Helo I dont have any curves on. I know different set ups produce different experiences but my T50 with a 100mm extension gives me nice stable control. The tutorials on rotor theory by CASMO have made a huge difference to successfully completing my trips too. Unlike the Huey which, in my hands remains a Bucking Bronco!

Thank you for this. If nothing else ive learned something new.

Yes Beta 20% across the board compared to pre patched Stable 2D, 1080P GTX 1080, 32GB RAM, I5 6600K @ 4.3ghz, latest drivers, W10. Logs, trks and dxdiag submitted to ED EDIT - regained approx 10% (8-10 fps) in the current 2.7.7 STABLE over the current 2.7.714 BETA, which is equal, if not marinally more than the 2.7.6 Beta but still 8-10 fps shy of the 2.7.6 Stable

Ive recently heard that staring at the winter solstace from inside a goats arse will recover the the lost fps and gain you 30 more. What is so hard about sticking to the subject of the original thread and providing ED with the files and logs they requesed?

I believe even DDU describes itself as being a bit of a nuclear option. Ive used it for years without any apparent ill effects but I do use it sparingly even so. Its a very useful program for fubar'd installs. Most installs however usually work just fine using the nvidia software.

No difference for me and my old 1080. Well youre posting in the wrong thread for a start...

Anything other that terrain shadows set to default will cause this. Been this way since as long as I can remember

100% agree with the sole caveat that this forum as a whole is hardly a representive sample size of all dcs players either. But big or small, if you report a bug and are asked for data, please provide it. I do have to wonder if its something outside of DCS in the OS, botchedOC (my botched I hasten to add) or even the hardware. Ill soon be upgradng the unsexy part of my system (MB, Chip, fresh OS and RAM) and will be curious to see how and if that alters the metric on an unbutchered OS.

I do remember being awed that my first DVD could step though the action at one frame per second. Less impressed with the same feature in DCS when I drop a bomb.

Still is for many in DCS

Merci Gentlemen Well thats somewhat disheartening.

As Im about to change my system for a new windows 10 install on a new Ryzen system, I went ahead and nuked the windows registry as per the guides from AdamX etc that are floating around here. Usuall optimisation and registry alterations but without enabling the game bar or GPU scheduling. Using the Mi24 weapons range Caucauses as a comparator the results did take me somewhat by surprise (firstly because the claimed increase in performace actually did, partially, transpire and b because of the difference between Stable and OB) Pre tweak the OB put out 70fps - post it still put out 70fps @ 1080P on mid range settings Pre Tweak Stable put out 84 fps - post it puts out 92fps using the same settings. Im a numpty but what it says to me is that windows liked DCS better a couple of months ago and that, somewhere, Ive lost a lot more than I first thought (about 25% in raw frames rate) even though i never knew i had it in the first place. Its a doozy Im not seeing any announcment - link??

Interesting but it has nothing to do with this thread. Performance loss is affecting Win10 users, VR users, 2D users, users with big specs, users with small specs, AMD and intel. For some its even a back breaking straw laid atop an already staggering camel. Its being reported in various threads under various guises, not just this one and its now conspiring with existing issies such as the fps hit with craters to make any meaningful play impossible. There comes a point where there simply isnt any more track left on which the Choo Choo can run. Whats worse, the track has stopped dead in the middle of scalper country. There does appear to be a valid and pressing argument for more track either over, or alongside, better Choo Choo at present, albeit for a period. Better Choo Choo alone isnt going anywhere for many of us.

One of the first things tried. Made no difference for me at the time. Will try again. EDIT - No apparent difference. 2D.

If you mean craters etc its a global DCS issue

Id recommend using Chuck's guides for quick familiarisation, especially in trials

This I presume https://www.digitalcombatsimulator.com/en/files/2019359/ Not EDs monkey, Not EDs problem...