MattCri

thank you, issue solved

i tried but the page isn't working for me, there is no button to create the ticket

im having the same issue, the modules i got from steam are deactivated

With my old amd rx580 the performance penality is huge, im losing 30 to 40% of the fps i had with 2.7 2.8 with no shadows is slower than 2.7 with flat shadows for me

i have no changes in caucasus bug a very noticeable drop in persian gulf

today patch lowed framerate even more for me

Im referring to this and the others few 2.7.6 to 2.7.7 performance degradation discussions, i was one of the affected guys reporting. After today's update the issue is solved for me, i will do some more detailed testing in the next days but i have at least 90% the fps i had back in 2.7.6. Im curious of other people reports and i would love some tech explaination of the solution from the developers (if possible) Anyway, big thanks for listening to us!

im in the same boat and my system is worse considering the degradation i have with the recent patches i can barely fly the ka50

the problem here is the lack of communication really, profiling two different build of a software for general perfomance is a few hours of work if you dont need to reproduce/trigger some obscure behaviour in my opinion this is like 2.5 to 2.6 again: the degradation is part of a large code refactoring effort and cant be undone in isolation this is the new baseline boys

not sure if this is worth a new thread i just want to report that in today openbeta 2.7.8 the degradation in performance is still present

can i aks your system specs and resolution/msaa/ssaa?

i have no perfomance loss on windows 11 in 2.7.6. Havent tried 2.7.7 on windows 10 so i cant compare but everything else runs just the same for me on 11.

in my case my gpu can draw 150watt max but is hovering around 100-120w in dcs, even at costant 100% usage and +25% powerlimit well, if im right there is no pattern but the issue should be visible easily if they run a gpu profiler and trace a few frames.

can you look at the gpu power? in very optimized games i can see your gpu drawing over 350watts, i can be wrong here but i bet it is drawing significantly less in dcs

not plain wrong, id say partially you should consider that a gpu is not a monolithic thing, you can bottleneck a single part (say memory bandwidth with 4k and msaa) and have room to spare in other blocks (like compute and shaders)

this is because if you are running a strong gpu, say a 2080 or the newer 30xx series most of the time you are VERY cpu limited with gpu headroom to spare, so any increase of gpu render time,up to a certain point, is basically invisible in your performance profile there is no vodoo magic here in my case it is immediately visible because my system (ryzen 3600 rx480) is gpu bound 90% of the time

i believe everyone has it and those who don't see the issue are just bruteforcing through seeing reports of no perfomance loss in 2d but necessity to lower the pixel density on vr to regain performance on the same system should point to a gpu bottleneck

well, marianas is pretty new and basically a work in progress, cant exclude some optimization introduced in 2.7 other maps werent touched, so the performance loss is consistent and reproducible

and that is exactly my experience and what i have reported the more your system is being pushed, the less the degradation is visible. Until you reach a point where already existing bottlenecks are taking over. im pretty sure if you do your tests on caucasus and without msaa/lower res the loss will be even higher

It's just observation at this stage but in my opinion it is not a gpu bottleneck or the new water im my experience the degradation is minimal to zero in very heavy scenes and huge in very simple frames (no clouds only sky f2 camera) If i have to guess its something related to memory/cache on the cpu side or bandwitdth related on the gpu that gets watered down if you are already pushing a lot of data for high res and msaa.

guys, it is not a windows issue if we can have the usual fps just reverting back the patch in my opinion if you cant see the degradation you are possibly running 1440p with msaa or 4k with msaa on a very recent gpu, even less if 60hz or capped at 60fps basically you dont see anything because your bottleneck is elsewhere

well, just reuploading, im open to share any information necessary DxDiag.txt dcs.log test patch 2810.trk

hope this doesnt become permanent we had a similar situation when 2.5.6 rolled. People updating from 2.5.5 complained of performance degradation same huge thread on the forum, lots of testing, lots of discussion and then 2.5.6 was pushed to stable "as it" and perfomance never recovered.

well, most of the times performance issues in dcs are not because of outdated hardware, is because they tend to brute force everything everything run on 2 cores so we have to resort to dumb 5ghz+ overclocks with 80% of our cpus doing literally nothing we need huge amounts of ram because without a modern streaming logic we have to preload as much stuff as possible to reduce stuttering and storage bottlenecks to have good image quality we have to brute force resolution and incredibly expensive 4x msaa and supersampling. Just look at other engines, TAA implementation is almost 10 years old, very light to run and the image quality is even superior. DLSS is amazing if you have a rtx card, amd's FSR is worse but works on every gpu. They are pushing incredibly high quality assets on a old fountation.

reverted to 2.7.6 UTIL GPU SCLK GPU MCLK GPU TEMP GPU PWR GPU FAN GPU UTIL. VRAM GPU FPS UTIL. CPU UTIL. RAM 94.54.00 1333.17.00 2000.00.00 71.08.00 123.39.00 1265.30.00 6218.00.00 73.34.00 15.24 17.01 100 1342 2000 64 122 776 6150 64 16.01 17.00 100 1342 2000 65 119 803 6166 59 13.28 17.00 100 1342 2000 65 119 816 6170 63 16.08 17.00 100 1342 2000 66 121 843 6169 64 13.31 17.00 100 1342 2000 67 124 875 6153 66 13.31 17.00 100 1342 2000 67 123 910 6153 67 16.39 17.01 100 1342 2000 68 125 946 6153 67 16.18 17.37 100 1342 2000 68 125 986 6153 67 13.18 17.37 100 1342 2000 69 127 1027 6153 66 16.19 17.38 100 1342 2000 69 124 1071 6155 66 14.28 17.38 63 1342 2000 70 126 1121 6155 66 14.00 17.38 100 1342 2000 70 129 1144 6156 66 15.20 17.38 100 1342 2000 71 132 1165 6156 60 13.02 17.39 100 1342 2000 71 134 1209 6166 57 15.05 17.01 100 1342 2000 72 131 1250 6226 57 14.01 17.01 100 1342 2000 72 131 1301 6226 58 14.45 17.01 100 1342 2000 72 128 1343 6226 59 12.50 17.01 100 1342 2000 72 127 1374 6226 61 14.03 17.02 100 1342 2000 72 127 1379 6228 69 16.10 17.02 100 1342 2000 72 128 1404 6228 69 16.04 17.02 100 1342 2000 72 126 1409 6233 68 15.31 17.02 100 1342 2000 72 130 1411 6234 76 14.16 17.02 99 1342 2000 73 129 1414 6239 89 14.23 17.03 100 1342 2000 72 113 1412 6244 95 16.24 17.04 99 1342 2000 71 110 1412 6258 139 15.40 17.04 100 1342 2000 71 110 1413 6258 142 16.42 17.04 100 1342 2000 72 129 1412 6258 134 14.23 17.04 100 1342 2000 73 129 1408 6258 72 13.25 17.04 83 1342 2000 73 129 1409 6258 73 13.56 17.05 66 1342 2000 72 124 1410 6258 72 15.07 17.05 100 1342 2000 73 124 1436 6258 70 15.39 17.05 100 1342 2000 73 128 1442 6258 69 15.39 17.05 100 1342 2000 73 128 1442 6259 62 15.03 17.06 100 1342 2000 73 130 1450 6259 62 16.12 17.06 100 1342 2000 73 123 1460 6259 70 15.42 17.06 100 1342 2000 73 127 1464 6261 72 16.37 17.07 100 1342 2000 73 125 1463 6261 71 15.19 17.07 100 1342 2000 73 124 1460 6264 69 15.29 17.07 66 1342 2000 73 125 1458 6264 69 14.32 17.07 100 1342 2000 73 125 1458 6264 71 19.37 17.37 0 980 2000 65 32 1475 6265 91 15.24 17.13 Latest Openbeta UTIL GPU SCLK GPU MCLK GPU TEMP GPU PWR GPU FAN GPU UTIL. VRAM GPU FPS UTIL. CPU UTIL. RAM 98.30.00 1342.00.00 2000.00.00 68.42.00 117.06.00 1161.00.00 6314.10.00 57.40.00 13.26 16.48 100 1342 2000 61 115 740 6244 53 14.24 16.51 95 1342 2000 61 115 761 6263 50 16.02 16.51 100 1342 2000 62 114 779 6267 52 15.57 16.52 100 1342 2000 63 118 790 6267 52 14.58 16.50 99 1342 2000 63 115 810 6251 53 13.21 16.50 100 1342 2000 64 116 832 6251 54 14.26 16.50 100 1342 2000 65 115 850 6251 55 14.23 16.47 100 1342 2000 65 117 880 6251 55 12.54 16.48 100 1342 2000 66 117 903 6251 54 13.29 16.48 100 1342 2000 66 117 931 6252 54 13.16 16.42 100 1342 2000 67 117 966 6252 54 12.48 16.42 100 1342 2000 67 116 1007 6253 54 13.28 16.43 100 1342 2000 68 124 1040 6253 51 14.20 16.43 100 1342 2000 69 122 1082 6263 48 14.40 16.46 100 1342 2000 69 123 1126 6323 48 13.10 16.46 100 1342 2000 69 123 1161 6323 49 13.11 16.46 100 1342 2000 70 123 1212 6323 49 12.39 16.46 98 1342 2000 70 118 1251 6323 51 13.09 16.47 100 1342 2000 70 123 1284 6323 55 13.40 16.47 100 1342 2000 70 121 1315 6326 56 12.36 16.47 100 1342 2000 70 118 1325 6330 56 14.04 16.47 100 1342 2000 70 119 1324 6331 56 13.10 16.48 100 1342 2000 70 119 1348 6336 67 12.14 16.49 100 1342 2000 70 106 1357 6341 65 11.52 16.49 100 1342 2000 69 101 1332 6354 89 13.50 16.49 100 1342 2000 69 101 1330 6354 93 14.05 16.49 62 1342 2000 68 102 1313 6354 91 13.20 16.49 100 1342 2000 70 121 1298 6355 60 11.23 16.49 100 1342 2000 70 120 1294 6355 57 12.01 16.49 100 1342 2000 71 117 1318 6355 57 13.01 16.49 100 1342 2000 71 118 1328 6355 57 13.38 16.50 100 1342 2000 71 118 1326 6355 57 13.00 16.50 100 1342 2000 71 123 1326 6355 52 12.48 16.50 100 1342 2000 72 120 1353 6357 51 13.24 16.50 100 1342 2000 71 118 1358 6357 56 13.19 16.50 62 1342 2000 71 118 1358 6357 57 13.40 16.50 100 1342 2000 72 118 1357 6357 58 13.12 16.50 100 1342 2000 72 119 1357 6358 57 14.16 16.50 100 1342 2000 72 117 1359 6361 56 14.04 16.50 100 1342 2000 72 118 1359 6361 57 16.14 16.50 Average in new updates dropped from 73 to 57 fps, -22% Max fps from 142 to 93, -34.5% Min fps from 57 to 48, -7.7% No changes in system, tests made literally 15 minutes one from another on windows 11