chumpnut1323

I updated to 1809 when it released and couldn't play DCS in full screen since, so I went back to an earlier version, 1803 I believe. Well I updated once again to 1809 today and have the same problem. ALT+ENTER does not work. FN+F11 does work but then the keyboard locks. Anyone else have this issue?

I believe its mission 3, where you have to escort the SU-25's. I completed this mission multiple times and it never advances the campaign. The last time this occurred was today with a "successful completion" message and no downed SU-25's. I RTB and quit the mission and then ended the mission and the campaign does to advance. Any input would be helpful. Thanks.

Yes it is. Beta build is beautiful even on Normandy. Multiplayer will have the typical loading pauses when others are connecting and what not yet. Single player is pretty flawless. I was very critical on the stuttering in the past, because it was very immersion breaking. I was surprised as hell with the latest beta build.

In the recent 2.5.4 beta build I can only search on my C: drive for key bindings, I have all my maps on my E: drive. Stable build seems to be fine, I can search every drive. Also, in 2.5.4 beta I edited the "maxfps" in notepad to 60fps but doesn't appear to have an affect in game. Stable build is fine. Other than that very impressed with the performance on the 2.5.4 beta build, well done!

I've felt the same way as you franx since I got into DCS, did everything from tweaking bios settings to nv control panel, to in game settings, to process lasso with absolutely no improvement. HOWEVER, I seen someone's post regarding the current beta build 2.5.4 maxing out 2 cores on the cpu. Learning that I quick updated the beta and jumped in thinking we'll just give this a try not expecting any change. To my surprise, not one noticeable stutter during a quick action mission. Check it out, and let me know what you think.

Can't confirm fps improvement or not, but there's definite improvement with stuttering. I actually haven't noticed any during my single player test's so far. ED deserves my money now :)

All of my stuttering comes from interactions or object count. Eliminating AA may mitigate the problem but definitely isn't the root cause of it. I think if anything lowering AA settings will give you a higher frame rate overall, but doesn't solve stuttering. I hope Vulkan API is the solution to it, but if it is not... DCS will end for me :(

Just curious if anyone has ever tried this for a stutter/low fps fix. I don't think it would do anything for my rig as I have 16gb of ram and even after a fresh restart when my ram cache is zilch, I get stutters during "heavier missions". Maybe it's a hotfix for those with 32gb + of ram who suffer from fps issues. Just throwing it out here. Take care.

Vulkan API It's not really a secret anymore that DCS is getting a Vulkan API patch in the coming months, but it also kind of is. I dam near gave up on DCS back in April because lack of optimization, and communication from the dev team about it. After learning about Vulkan being implemented a couple days ago, it makes sense on why the same problems still exist, because they're waiting for this new API system to be introduced and then begin the optimizations that are needed(at least that's my assumption). The fact that I had to claw and scratch my way to through forums in order to figure that information out is surprising to me. Why not come out and say that's the plan? Any way excited to learn that news, and can't wait for Vulkan to drop. Cheers

Like this thread states, loading new models or damaged models seems to a big issue. This log attached was a mission to destroy a single TU-22. These two lines right here occurred in the log towards the bottom upon splashing the bomber. 2018-05-20 14:40:37.115 ERROR GRAPHICSVISTA: Can't open model TU-22-OBLOMOK-WING-R. 2018-05-20 14:40:37.119 ERROR GRAPHICSVISTA: Can't open model TU-22-OBLOMOK-WING-L. "Can't load" models = stutters? I'm sure this has been looked at (I hope anyway), but when creating a bigger mission with multiple "splashes" it's unplayable at times. I'll refuse to buy any more content until stuff like this is ironed out. I encourage others to do the same. Until then I'll enjoy my solo sunset flights. dcsTU22cantload.zip

Your not alone, I experience this as well. It's not a hardware issue and there's no software or notepad editing you can do to fix it. This is a ED thing, and until they ditch the nice new planes and maps and focus on the quality of gameplay it's not going to happen. For me SAM sites really expose the problem, but I still get the stutters even without them. It depends on what canvas you fly on as well... Caucasus = the best performance, Nevada = a close second, and Normandy = forget Normandy it's ****in horrid. I didn't know what stutters were until DCS World haha. BTW I play 1080p with OpenTrack, not even VR.

Just want to give an update. Appreciate all the feedback. I believe the problem lies in too many units within a small range of space such as what you would get with the "create fast mission" option. That's where I first encountered the problem and that's where I've been testing the problem. I honestly think any rig would stutter or perform a badly with the "create a fast mission" option unless it spreads the units out and they're not engaging right away(which would give your system enough time to load the units properly). Now I understand Normandy is still early access, which is why the "create a fast mission" option performs the worst on it, the other maps aren't nearly as bad. I think the "create a fast mission" option is a poor option to have in the first place. I think it makes ED/DCS look bad which isn't the case, it's just too many units in too small of a space. The one thing that I believe helped was "cockpit resolution" setting to every frame, whether that be 512(my case) or 1024. Also the 2.5.1 FX helped frame rates as well. Another think I noticed was, barely any hiccups without SAM'S. I found a thread on stating the same here... https://forums.eagle.ru/showthread.php?t=206772 If I run max units without SAM's the stutters are significantly reduced. Thanks for all the help.

I believe this is the source to my problems as well. SP and MP. BETA 2.5.1 seemed to help a bit however.

For what its worth I attached another log. This time on low settings with the same stuttering problem. I chose Normandy again because it seems to be worse than any other map, but I do indeed get it on the others. dcs.zip

I attached a log where I created the problem in a quick mission in which I chose the Normandy map. I have tried the settings on low and it still stutters. I can run an easy 60fps on high settings with tree visibility maxed and shadows=low, terrain shadows=default when just flying around. As I stated before any interaction that involves weapon deployment makes it stutter. The log attached was done on the open beta 2.5.1 but that doesn't really matter just for reference. Thanks for the responses, I'm dedicated on figuring this out, like madly, insanely, unhealthy type of dedication. dcsquickmisslog.zip

I've been tweaking the nvidia control settings for months now, tried just about every combination of settings. I set everything back to global as you stated and the stutter/massive frame drops still persist. The pagefile is interesting although. I tried setting it at 1024MB, 24GB on one SSD, 24GB on two SSD's, and I've let windows manage it. Stutters still were evident. The interesting part was I had Riva Tuner running stats in the background no matter if I had a pagefile or not, small or large DCS still ran a pagefile of 12GB during single player and around 25GB in multiplayer. The size of the pagefile that DCS uses concerns me lol. Hopefully with the new memory management update, that is fixed and possibly my stutter issue. Now enlarging my pagefile to twice my RAM(16GB) helped keep me in the multiplayer sessions, otherwise it was creeping up past 16GB and crashing. But the main issue of stuttering persists.

Good catch, I moved my GPU to the top slot, PCIe is @ x16 now. Didn't affect my performance however.... I have a MSI Z97 MOBO I did recently delete the meta shaders folder as that was one of the many "quick fixes". I have a SATA SSD I did just play before and it ran good for a couple sessions then it started stuttering again. I think that was why it was hard to pinpoint on what was causing it. The majority of the times I play tho it does stutter with the smokey interactions.

Thanks for the reply. Once again if I startup any quick mission, in which they're are a lot of units in a small amount of space right infront of me; no stutters until the units start firing away. But I've also related it to flares, etc... Logs.zip

No matter what setting I turned down, even with everything on the lowest settings I get major stutters with anything related to the new smoke affects. This has been months of testing on my end. Mostly tested this out with quick missions with medium amount of units. Offline: Normandy is by far the worst performing. Caucasus is manageable with few stutters. Nevada performs the best but still has few stutters. Multiplayer: Same issues. No stutters until something/someone emits smoke, whether that be pods, sam launches, air to air launches, flares, it doesn't matter. In 1.5 I can have everthing maxed out and no stutters with the emitting of smoke. It runs pretty flawlessly. My GPU memory is around 2-3GB's of use in 1.5 though and thats where I believe the problem resides in 2.5 because it's dam near maxing out my VRAM at 6GB's. Keep in mind Iv'e done just about everything with tweaking, OCing, nvidia control panel, nvidia inspector, etc.. My conclusion is it's either my GPU causing the issue or it's the optimization on ED's part. I believe it is mostly likely my GPU. But even when I turn the settings on low my VRAM is at 2-3GB's I still get the stutters with the smoke effects. I like to keep the settings mostly on high and I can retain a constant 60fps until (you guessed it) smoke emits. So what is it? Who here has a 1080TI and what's your experience like with that badass? GTX980TI, 4790k, 16GB DDR3, EVO 500GB SSD.

Haven't seen any threads on this, so I decided to start one and see if anyone else is having this issue. This has only been aware to me since 2.5 release and has occurred on every first missile launch attempt in the SU27. (Multiplayer only/haven't tested in single player) Here's what happens... I lock onto a target get the LA indicator well within range, and the missiles do not release. This happens with both radar guided and infrared guided missiles UNTIL I switch to guns and then switch back to either missile, then they launch just fine. To my knowledge I was not being jammed. Sorry if this has been brought up and I didn't catch it or if it isn't a problem at all and I need to up my game. Thank you! ~chump

Just going to join ya'll and say SAME! Single player is beautiful tho!

Thanks Devrim for all your work. Just bought the SU-27 last night. Is your English cockpit designed to work in DCS 2 as well as 1.5?