Limaro

Currently the realtion between wind and roughness of sea seems a bit unrealistig. espacially on marianas, I dont expect the ocean to be as quite as a lake, just because I don't setup a storm. Maybe it would be greate to just separate both options, or better, to have a minimum roughness for the see depending on the wind, but being able to make maximum roughness, with moderate wind.

I saw btw. that my settings were only to "Ryzen Balanced" but also on MaxPower, leads to identical results. @impalor I tried a lower multiplier for the RAM, down from 3200 to 1600. but this had no effect on my side.

I still cannot believe they dont care. But priorization is always a tricky thing. that's why I asked in this thread again everyone to follow the advice from ED, to make a own thread, to allow better tracking of the different aspects. I also made some hopefully last tests, but I think they point on the issue, in one or another way. I truely believe that most damage caused something with shadows and resolution. Here is my last data: - I run everything with settings from @impalor (mostly everything is set to low). - Then i've changed specific settings - Run both versions (stable 2.7.6 and OB 2.7.8) - I calculated the total loss compared to the "original run" - I made the tests in the order listed here. The text in bold is the changed setting. And there are two very outstanding impacs: My original Track, Impalor settings (Origial Run to compare settings changes with) 2.7.6 Average framerate : 116.0 FPS 2.7.8 Average framerate : 115.6 FPS > 2.7.6 vs. 2.7.8: -0,34% My Track, Impalor Settings, + Low Shadows (previously off) 2.7.6 Average framerate : 103.0 FPS -11,2% 2.7.6 Average framerate : 97.8 FPS -15,4% > 2.7.6 vs. 2.7.8: -5,0% My Track, Impalor Settings, + Low Shadows + Terrain High, Shadow Terrain Default, Global Illu - Performs better than the previous, I guess because of terrain shadow. I mentioned this effect in another thread) 2.7.6 Average framerate : 103.4 FPS -10,9% 2.7.8 Average framerate : 100.8 FPS -12,8% > 2.7.6 vs. 2.7.8: -2,5% My Track, Impalor Settings, + Low Shadows + Terrain High, Shadow Terrain Default, Global Illu - @ 4k 2.7.6 Average framerate : 83.9 FPS -27,7% 2.7.8 Average framerate : 74.5 FPS -35,6% > 2.7.6 vs. 2.7.8: -11,2%

I run some additional tests, comparing settings, resolution and track files. this is the outcome: impalor track, original settings from impalor (1080p Settings) 2.7.6 Average framerate : 112.0 FPS 2.7.8 Average framerate : 111.4 FPS impalor track, 1440p Settings impalor 2.7.6 Average framerate : 109.6 FPS 2.7.8 Average framerate : 108.1 FPS impalor track, Own Settinges @ 1440p 2.7.6 Average framerate : 86.1 FPS 2.7.8 Average framerate : 84.8 FPS impalor track, Own Settinges @ 1400p Only recorded Under Clouds 2.7.6 Average framerate : 76.3 FPS 2.7.8 Average framerate : 74.3 FPS My original track, Own settings 1440p 2.7.6 Average framerate : 106.2 FPS 2.7.8 Average framerate : 101.2 FPS My original track, Own settings 4k 2.7.6 Average framerate : 84.9 FPS 2.7.8 Average framerate : 75.8 FPS impalor track, Own settings 4k 2.7.6 Average framerate : 79.7 FPS 2.7.8 Average framerate : 73.3 FPS impalor track, Own settings 1080p 2.7.6 Average framerate : 87.7 FPS 2.7.8 Average framerate : 86.6 FPS My original Track, Impalor settings: 2.7.6 Average framerate : 116.0 FPS 2.7.8 Average framerate : 115.6 FPS Espacially last run, of my track and @impalor settings, shows, that somehow it is settings related. However, I also assume that resolution has special impact comparing 2.7.6 and 2.7.8. But also the other tackfile shows less differences in general, comparing the versions... this is all odd EDIT: my settings are on my initial post.

This is really nice work and thorough test results. I was really curious why you have nearlly no frame drop. so I've tried your exact settings and run your track and these are the results: 22-11-2021, 14:30:08 DCS.exe (Stable 2.7.6) benchmark completed, 7342 frames rendered in 65.515 s Average framerate : 112.0 FPS Minimum framerate : 87.9 FPS Maximum framerate : 138.8 FPS 1% low framerate : 25.5 FPS 0.1% low framerate : 3.7 FPS 22-11-2021, 14:34:27 DCS.exe (Open Beta 2.7.8) benchmark completed, 7354 frames rendered in 65.985 s Average framerate : 111.4 FPS Minimum framerate : 89.0 FPS Maximum framerate : 136.8 FPS 1% low framerate : 39.9 FPS 0.1% low framerate : 3.7 FPS The averate framerate just drop by .6 FPS!! It's the first time, I've seen nearly the same data in both versions. I will repeat the tests again , to exclude the propability that I missed something.

That does not matter. I've made most of my tests having 2.7.6 on my HDD, but it was still faster.

You mean it does not start any more? Thats why i meant to install the other Version. OB when you normally run Stable, or visa versa.

Dear everyone, as you may have notices, the thread to the performance loss has been closed, due to endless discussions. I opend this one, as ED asked that everyone having issues, should open his own thread, posting as much data as possible to support the ED developer team. Even though the thread being set to "reported" as a ED tester could have reproduced it, I asked the question, if it is still whished, that everyone having the problem should share his experiances in a own thread - and this was answerd true. I truely believe, that this has only advantages: - First of all, there would be a reliable number of affected people. Espacially because data will be a bit better prepaired. - And it offers an easy way fo ED to "collect" the benchmars, dxdiags,.. (nobody wants to crawl through the pages of a thread). - It would also give ED the possibility to give individual feedback. So I kindly ask everyone of you, to not overload this thread, as I tried to share data here, that is ment to help ED finding a solution. And If i find something new, I'd like that it does not get lost. @impalor: You said you did not feal strong performance difference from 2.7.6 to 2.7.7. That is very interesing for me. Do you have the possibility to install the 2.7.6 again (maybe using stable or OB, which one you dont use) and make a real benchmark? And if there is really no difference, please share then you dxdiag and settings.That would really make me curious

I know. Very "thanks" for that reminder... I just don't have fun, making endless runs arround a airfield, typeing in coordinates spottet by the TGP into the HSI and UFC... this is NOT replacing it.

Dear ED-team, could you pleeeeeaase finally fix this bug: It's now there since 2.7.1, and it makes using of TOO modes for JDAM very very painful, as it takes you the possibility to attack multiple targets without the need of slewing the TGP all the time. In short: When undesignate the target, it wipes out all the TOO coordinates from all stations, TOO1 and TOO2.

Status Update 2.7.8 Average at one try ~76.0 FPS, attached the geforce results. So It it recovered maybe 2~3 frames, but is definetely not on 2.7.6 level. 2.7.8_Flight_Caucasus.csv dcs.log

I ve tried what you described. But i have no moment where fps reaches more than when not pressing alt+tab

I'd like to share one last but very important information, thats why I just not updated my previous reply: On my wifes computer, there are - no modules. - It's a very blank installation - with its own DCS account, and there are - no devices beside mouse and keyboard. I still cannot understand, how it can be, that this does not happen to all. What I consider a big problem, is, that not all people may have noticed the issue - and/or they don't take the effort to really compare different versions, making rollbacks and dedicated comparisons - espacially now that stable is also on that version. So the real number of affected people could be underestimated easily. And: People not having the problem, shared not much data so far. So I beg ED to not give it up, finding a solution! And in that spirit, I repeat my offer to make more verbose test, when I am getting asked. I have two different computers available. Just give us intermediate build versions, zipped shaders, special configs files, or whatever could lead to valuable knowledge. ..as software developer I am used to debugging

I am adding "new" information. I have tried everything again, but that time on my wifes computer. And I am getting the same results, resp. same drop of FPS. 2.7.6.13436: 74.0 FPS 2.7.7.15038: 61.5 FPS She has a totally different PC than I do. Only common thing are the windows language, and the nvidia driver version. In a nutshell: Win 10 Pro, i5-4670, 16 GB Ram, GTX 980 So again, attached you will find: - trackfile and a mission - two geforce performance logs - two dcs logs - dxdiag - screenshot of settings (different to mine, as pc is slower) Some prosa to the installed situation: - I have first installed DCS open beta - I created the track file and mission - Then I measured - switched to 2.7.6 and measured again. And it was better! - then I switched back to 2.7.7 and it was bad again. dcs performance drop.zip DxDiag.txt

This is true. But since Flappie could reproduce it, and the bug got the state reported, I guess many think, that it does not worth to find additional parameters anymore. But this may be also wrong and a question to @BIGNEWY or @Flappie. Is ED still "collecting data" for that problem? I am refering to this, where you asked everyone to create a topic for each ones specific problem/circumstances (Link) Btw.: I've also tried the shader cache size from NVIdia Control Panel, but this has influence i could measure.

@Hiob I now tried it as well, and renamed the directory dcs.openbeta from Saved Games - which is then re-created. After setting up the right settings, and running my track, I have still my reduced framerate.

Really interesting. I will try that later. When it "works" i will then copy one file after another, this shall then show it, as soon as performance changes.

You are definetly too fast, I wanted to share the link too Now let's all cross the fingers

Hi @Flappie, wow this is really great news to read, thanks for givin this update ! I will share this answer to the other - more frequented - thread, this will lead to many reliefs

Hi Flappie, you should find the exact versions and many oder informations in the attached zip, as they contain the dcs Log files. I believe 2.7.7.15038 and 2.7.6.13436

Updating from 2.7.6 to 2.7.7, first in Open Beta, then in stable, my frames per seconds decreased significantly - arround 10 to 15 %. As wished from the other thread, this one is specific to me, for my settings and not meant for discussion. I also posted all my things here and here My attached zip contains - Two Trackfiles, flying in Beirut and Caucasus - Screenshots of in-game settings - Report Summary Excel - For all versions (2.7.6, 2.7.7, 2.7.7 cleared) - Verbose NVidia reports - Logfiles Easiest way I found to reproduce: - Create new mission in caucasus and start directly (camera is over Anapa, and the frames are 145 vs 119 FPS) My PC in short: Ryzen 7 3700X, RTX 2080 Super, Windows 10 Some prosa from all my testings: - I first have compared freshly installed stable (before patch) with OB. After stable was also changed to 2.7.7, the loss also occured there. I then downgraded stable back to 2.7.6, and the nicer performance came back. - I have tested with deactivation of all modues on both sides - I removed all Scripts and cleaned the metashader2 and fxo - I run cleanup and repair - I have tested many many settings combinations. But the loss seems to maintain the 10 - 15% drop rate. -> from 60 to 52 or from 145 to 119... - I also tried the last 3 NVidia drivers. - I have tested many different nVidia graphic settings - I have tried deactivation of Geforce Experiance - I did not observe hugh differences for GPU in voltage, temperature or usage - I have tested with and without using multiple screens. Most tests were with only one screen. - At the beginning I had issues using different nvidia driver, but was not able to reproduce. I guess I also changed settings doing so. I will update this post when finding something new. @ED team: Feel free to ask me to test specific settings, track different logs, or what ever could help you to identify the root cause. DxDiag.txt 2.7.6_vs_2.7.7_Analysis.zip NVIDIA System Information 10-29-2021 15-11-31.txt

And you're running the tracks always twice, once for 2.7.6 and once for 2.7.7? (just for clearification) BTW: I dont even need any tracks at all. Best compare results I get just be creating a empty mission in caucasus or any other map, and then just start (no plane or anything). Camera starts over Anapa and I already have 145 vs 119 FPS

You activated Vertical Sync. That means that before patch you were somewhere over 60 FPS, which is then capped to 60. After the back you are below, and then it's capped to 30. Thats of course extreme situation. It confirms the drop, but not the real quantity

I've rolled back stable to 2.7.6. and the framesrates are back to "normal". Nvidia driver update did not make any differens. @BIGNEWY I can offer you to make specific tests, or try different configurations. It's very reliable reproducable and I have both, Stable 2.7.6 and Beta 2.7.7 installed ATM.

Yes, 2.7.7 (beta or stable) Loss of ~ 10 - 15 % Win 10 (Version 10.0.19043 Build 19043) 32 GB Ram Ryzen 7 3700X X570 Chip RTX 2080 Super (Driver 496.49)