Gryzor

Stability is not everything. Please return back the performance fps level of 2.5.5. Beta is unplayable. Stable version would be at least the same fps level of previos branch.

Then, I will not even try the beta today´s update. Very bad news, more than one month with this fps reduction without fixes it worries me a lot.

Thanks for the quick update, I hope that performance of today´s patch returns at least at same 2.5.5 levels, especially with preloading terrain stuttering (not present in 2.5.5. In 2.5.6, its very noticeable on MFD maverick or TGP weapons usage, specially in caucasus when pointing those sensors at the horizon).

I reverted back to the latest openbeta 2.5.5.41962. I hope some fix in the near future. Having such performance loses its a serious situation (even taking account its a beta branch). Seriously ED, maybe it would wise to hire some expert in code development - software optimization, according reddit post and "spaguetti" code, please consider it the hightest priority now. In my case, I invest more than 700 € since 2011, high end pc in all modules / scenary / campaign etc... I don´t remember having such huge downgrade in performance (appart from graphic corruption in VR like no L eye light rendering) in DCS history. Even alpha 2.0 version were quite similar in performance terms compared with 1.5 3-4 years ago (having now a reduction of 30-40% in performance... in other situations with many unit, to single fps digits, even with my pc high end VR-PC). I hope 2.5.6 would be at least the same performance of 2.5.5 (now, after many years of waiting, I´m not very optimistic in performance optimization). Sincerely, I hope solutions, focused primaly in the core sim.

I thing that some sort of terrain preloading occours when zooiming sensors, then stuttering happens

To point: "- The VR performance difference between 2.5.5 and 2.5.6 is small to none in empty missions with little to no AI action.", try to use some sensors TV or Su-25T/KA-50 SVAKL in caucasus, it´s a stutter fest specially when those sensors points to the horizon.

Please devs fix asap or at least return performance levels of 2.5.5. Downgrade is not acceptable in my opinion, specially performance drops of a -60% level

Caucasus is the worst fps for me too, since 2.5.6

With 2.5.6 in caucasus is terrible. With su-25t or a-10c, tgp ON, totally unplayable (full stuttering when tv looks at horizon). I realized that in Persian Gulf this doesn´s happen, maybe some change in cache or precaching data has bugged caucasus region?

With new update, the performance is the same (stuttering fest specially in caucasus using TV sensors or IR in A-10, K-50 and F-1. How is possible to have 20 or 30% performance lost and stuttering in loading terrain (causcauss specially). I don´t understand. In addition, rendering in one eye in VR continues, it distracts a lot (however, great lighting at night) I hope that stable version will recover the performance lost, at least, the same we had in 2.5.5. Now most missions are completely unplayable. Yes, clean version, deleted metashaders and fxo, top end PC specs, etc..

With new update, the performance is the same (stuttering fest specially in caucasus using TV sensors or IR in A-10, K-50 and F-18). How is possible to have 20 or 30% performance lost and stuttering in loading terrain (causcauss specially). I don´t understand. In addition, rendering in one eye in VR continues, it distracts a lot (however, great lighting at night) I hope that stable version will recover the performance lost, at least, the same we had in 2.5.5. Now most missions are completely unplayable. Yes, clean version, deleted metashaders and fxo, top end PC specs, etc..

At 30 fps (I´m refer you video) in VR, flying is not exactly smooth, right? maybe due low fps stutter isn´t noticed

Where do you find the options file with "tackview" false?

In addition, just to add to the thread: when you input CTRL + PAUSE to show FPS and other data used in sim, VRAM Ram usage shows everytime a "0" value. Maybe it could be related.

In my experience the performance is similar in previous version when I disabled preloading (with editing of "["preloadRadius"] = 0". VRAM totally out of control (2080ti). I bet 2 cents that It could be related with high load times we have now.

I think the fps stuttering or low performance could be related the a 2.5.6 introduced bug regarding incorrect preloading of terrain or something similar. Look at SU-25T instant mission over caucasus: every time targeting is switched on, a huge stuttering and fps happens, specially when the nose camera is oriented towards horizon. Normally, fps goes down a bit with targeting, but not a such huge (30-40 reduction in fps). The same happens with oters sensor in A-10A, A-10C; If fact, I modified preloading config in options.lua, to this: ["preloadRadius"] = 0 That modification, putting to 0, in older versions did remove the preloading limit, causing a huge impact in performance and filling all VRAM. Now, in 2.5.6, performance is the same with preloading = 0, in comparison with others values. Same stuttering, same low fps, etc... so I think that lower performance in 2.5.6 could be related to having preloading option disabled, the sims tends to preload everything (subsequently, stutterfest happens). I hope 2.5.6 performance will be, at least, the same performance we have in 2.5.5, Maybe preloading issues could be related also with F14 low performance in RIO when WCS is on (radar must "preload" all scenery, maybe???)

I think the fps stuttering or low performance could be related the a 2.5.6 introduced bug regarding incorrect preloading of terrain or something similar. Look at SU-25T instant mission over caucasus: every time targeting is switched on, a huge stuttering and fps happens, specially when the nose camera is oriented towards horizon. Normally, fps goes down a bit with targeting, but not a such huge (30-40 reduction in fps). The same happens with oters sensor in A-10A, A-10C; If fact, I modified preloading config in options.lua, to this: ["preloadRadius"] = 0 That modification, putting to 0, in older versions did remove the preloading limit, causing a huge impact in performance and filling all VRAM. Now, in 2.5.6, performance is the same with preloading = 0, in comparison with others values. Same stuttering, same low fps, etc... so I think that lower performance in 2.5.6 could be related to having preloading option disabled, the sims tends to preload everything (subsequently, stutterfest happens). I hope 2.5.6 performance will be, at least, the same performance we have in 2.5.5, Maybe preloading issues could be related also with F14 low performance in RIO when WCS is on (radar must "preload" all scenery, maybe???)

The same for me. It´s playable in some training mission (with some stutterings that previously didn´t exists, even with zero AI units), but now, every mission its a stutterfest, and multiplayer completely unplayable (for me, a experience with spikes of 15 or 10 fps is not playable. Maybe could be to others...).

As title says, now appears some distant clouds not rendered in L eye, giving a strange appearence. In addition, landing light projected on runway, and some flood cockpit light, does the same, only partial renders in L eye. Bug not present in 2.5.5.

yes, its disabled from the beginnig. Try doing some mission with more that few units or MP.

Im tired of tweaking or reporting. 50% less in fps reduction in VR (and NO-VR) in comparison with previous version 2.5.5 is no way. Reverted to 2.5.5 at least its playable, no a stutterfest. At least, its a beta version. This is how performance & optimizations will grow in 2020. Seriously, I hope devs look into code or test before realeasing a bugged version like this, instead of saying the same copy´n´paste procedures (no mods, deleted FXO/metashaders...., yes yes yes...).

same here. Completely unplayable for me :-(

It seems to some sort of disk caching due terrain loading (not present in 2.5.5) moving camera in free view at high speed causes enormous stuttering and disk usage. It seems that memory is not quite well used. In fact, if I hit CTRL+PAUSE, Video memory is 0MB.

I have a reduction from constant 45 fps VR performance (even in big cities and in VR, in 2.5.5) to lower 30 fps or less... unplayable for me. Altought lighting improved especially on night missions, I´m very disappointed about this update. It seems in my test that performance impact is huge in Caucasus, regarding terrain generation (you can test in free cam view, displacing it along the scenary causes huge stutters - not seen in 2.5.5). I believe that some dev say that will not be drop performance in 2.5.6,... maybe this reduction is some related with ground pathing or so, please devs fix it or at least, give us the same performance we had in 2.5.5 (not perfect, but playable). My specs: 32 GM DDR 3200 Mhz, 7700K at 5.1 Ghz, 2080TI, W10, Index HMD. PD. Deleted FXO/shaders many times, repaired, all mods removed, etc... without success

I have a reduction from constant 45 fps VR performance (even in big cities and in VR, in 2.5.5) to lower 30 fps or less... unplayable for me. Altought lighting improved especially on night missions, I´m very disappointed about this update. It seems in my test that performance impact is huge in Caucasus, regarding terraing generation (you can test in free cam view, displacing it along the scenary causes huge stutters - not seen in 2.5.5). I believe that some dev say that will not be drop performance in 2.5.6,... maybe this reduction is some related with ground pathing or so, please devs fix it or at least, give us the same performance we had in 2.5.5 (not perfect, but playable). My specs: 32 GM DDR 3200 Mhz, 7700K at 5.1 Ghz, 2080TI, W10, Index HMD. PD. Deleted FXO/shaders many times, no-mods, etc... without success