2.5 Not smooth

[chardly38]

The only way to get the game to run smooth is to look only at the sky. My FPS are 40 to 60. Before 2.5 game runs great when I dont get a Freeze.

[Sideslip]

I hate to break it to you, but you are probably out of luck. You're running a 6 year old video card to drive almost 4K resolution. It's likely your system just can't handle the newer graphics in 2.5. I used to use two 7950s in crossfire so I know for a fact your GPU is about 1/4 as powerful as 1080. I wouldn't expect very good performance at 4k with a 1080... 40-60 fps is actually not bad, which leads me to believe you've already lowered all the settings possible.

 

Maybe they have more optimizations to do that will help, but at some point they have to stop supporting old hardware to be able to optimize performance on new hardware. Not that DCS has been known to be buttery smooth.

 

Unless your signature is way out of date?

[chardly38]

I have an RX 580 (just updated signature) 2.2 NTTR Im having good performance. 2.2 and 2.5 are to my understanding are the same. Looks like Im not the only one with game FPS low.

[Oceandar]

Have you tried this. It's from IronMike from another thread. This trick gives me 10 to 15 fps boost. I still use MSAA 2x thou

 

Good luck

Edited February 3, 2018 by Oceandar

[Dav IRL]

I have an RX 580 (just updated signature) 2.2 NTTR Im having good performance. 2.2 and 2.5 are to my understanding are the same. Looks like Im not the only one with game FPS low.

 

DCS World contains 3 maps currently, the map that runs the best is Nevada but only because of the lack of trees in the desert. You will not get the same performance in Caucasus as you will in Nevada, not by a mile, you need a GPU that caters for all terrains, your CPU is out dated and your GPU is really old. The above poster who mentioned upgrading is correct, let it go man it's not doing the business anymore, there is only so much you can squeeze out of an old rig.

[chardly38]

let it go man

? Real mature. NTTR in 2.2 run great. 2.5 NTTR no so. There the same engine. New updates are known the have problems.

Oceandar did that.

[BitMaster]

I flew MP on VA-Server last night after unpacking the gear...and WOOOWWWW I am blown away.

 

Constant 100+ fps with HIGH settings, trees max, grass max, everything to the RIGHT side and it just flies.

 

No stutter, no glitches, just smooth as butter.

 

I flew Ka-50, UH-1 and Mi-8 for like 1.5h. No lag, nada, all good on my end.

 

 

Thank you ED Team, amazing achievement for a beta ! Vulkan will boost us even higher

[chardly38]

Thanks BitMaster for your help?. RX 580 is not an old card.

[Sideslip]

No it's not that old, but it's also not very high performance. It is similar to the GTX970, which is almost 4 years old and wasn't the top of the line at the time.

 

http://gpu.userbenchmark.com/Compare/Nvidia-GTX-970-vs-AMD-RX-580/2577vs3923

 

You seem to be ignoring the fact that you are running almost 4k of resolution on a card that isn't expected to be able to do so well. And as stated above, a desert map with no trees is not the same thing as the Caucasus map. Have you set trees to 0%? There may have been some small changes to NTTR too. And no it's not supposed to be the same engine. 2.5 has new effects that didn't exist in 2.2.

 

 

Also, the 280X is the minimum requirement for 2.5 and the 580 is only 50% faster. That would mean you could expect good performance at a typical 1080p resolution being 50% above the MINIMUM. By simple math, you'd be bellow the minimum to run even just 2 1080p screens with that card. Resolution and GPU power scale almost perfectly together.

Edited February 3, 2018 by Sideslip

[jejsus]

Frames are not as stable as in 1.5 and it's stuttering more.

[Azrayen]

I suggest to see if you've 8GB RAM what's it's usage (perfmon+DCS). You're probably toping it. https://forums.eagle.ru/showthread.php?t=200822

 

No such issues here (i5 2500K, 16GB RAM, GTX1060 @ 6GB, 2560x1440 x1).

 

++

Az'

Edited February 4, 2018 by Azrayen

[jejsus]

i7 4790k, 16gb, 1070, 960EVO. Hitting 100% Vram and GPU proc. See the settings in images attached. I think I'm not exaggerating.

[Balzarog]

? Real mature. NTTR in 2.2 run great. 2.5 NTTR no so. There the same engine. New updates are known the have problems.

Oceandar did that.

 

If you post about a problem with FPS on the forum, and responses are that your GPU is very old or at best minimal for the game, and you should replace it, the best response is "Thank out for your suggestion," and not to argue about it with the people who're trying to help you. That serves no purpose other than to encourage the helpers to ignore your questions.

Edited February 4, 2018 by Balzarog

[jejsus]

After switching off deffered shading like mentioned earlier in this post it runs smooth as ever was, but the trees are now light greyish, like volcanic ash hit them :). So much fun :joystick:

[monkie]

I thought it was the DS that was causing the slowdown in FPS but I think it was more the MSAA. Flying over a forest with DS off gave me a huge hit but with DS on it is now smooth. I run DS on but MSAA off, G-synch and I'm getting 60FPS and only occasional pauses as scenery loads.

 

 

Yes without DS I agree the tree shading doesn't look right, DS is a must, it's just a matter of them tweaking the lighting effects.

[chardly38]

Exactly Balzarog im use to running 40 to 60 FPS with the game running smooth with 4 monitors for years. I guess FPS should not have been stated. Im not looking for more FPS just to run smooth. Telling some one to just go buy a new computer with a snide remark does not help but thats ok. Just a fact the 2.2 is still good for me. 2.5 not so. Ill wait for the next update. And thanks for your help.

[Oban]

You can hardly blame the responses you received, when you state the only way you can see smoothness is by looking at the sky, so you began with a hyperbolic statement really.

 

I to have a 970, 16GB RAM and I see an improvement over 2.2/1.58 but that's maybe down to doing a fresh install, and no relics left over from the other 2 versions, and it runs pretty smooth for me, with more or less everything bar civilian traffic ramped up to high.

 

Forcing the screen resolutions well above the card standard of course will have some sort of impact, especially when it's not an upgrade per say, but a brand new map..

 

Your course of action to see where the best performance for 2.5 for you personally, is to scale everything back to low, and standard resolution, and increase bit by bit till you find that acceptable smoothness perhaps?

[METEOP]

Exactly Balzarog im use to running 40 to 60 FPS with the game running smooth with 4 monitors for years. I guess FPS should not have been stated. Im not looking for more FPS just to run smooth. Telling some one to just go buy a new computer with a snide remark does not help but thats ok. Just a fact the 2.2 is still good for me. 2.5 not so. Ill wait for the next update. And thanks for your help.

 

 

chardly38 I have a thread were I am investigating this issue :

 

https://forums.eagle.ru/showthread.php?t=201162

 

'change your computer' is an easy answer, from my perspective it's more like :

 

- if you have low fps, that's fine but should be smooth / consistent

- the same plane, the same map, the same graphic settings should give a similar performance between 2.2 and 2.5 IMO, but it does not.

- We are in BETA release, so let's helpl the devs and ourselve by hammering at these issues till they are ironed out!

 

One thing that seems to stand out between the stutters / no stutters camp is 16GB ram vs 32Gb ram, still investigating...

[docWilly]

Personal finding on my system: reducing shadows to "flat" reduces stuttering almost completely with all other sliders maxxed out.

 

MSAA 8

AF 16

DF on

global cockpit illumination on

no Lens/flare

preload radius full

visibility high

water high

textures etc high

 

increasing Grass to full does not affect frames nor stuttering,

trees at 87% (increasing more has no visual effect)

 

with vsync on (= frames locked to Monitor) I get steady 60 fps without stuttering.

 

Specs below

[Mustang]

global cockpit illumination on

 

I wouldn't use that, enabling this setting turns off neat effects like when the cockpit goes dim when you fly into a shadowed valley or behind and object or building.

[docWilly]

I wouldn't use that, enabling this setting turns off neat effects like when the cockpit goes dim when you fly into a shadowed valley or behind and object or building.

 

thanks Mustang check it out....always wondering what it does as it has no effect for example on the way too dark cpt illumination in most ac

[Sideslip]

...One thing that seems to stand out between the stutters / no stutters camp is 16GB ram vs 32Gb ram, still investigating...

 

No stutters (well no regular stutters) with 16GB ram. Game only uses 7.5GB so I don't see how more than 16GB would matter. Haven't tried multiplayer though. You are more likely to find an issue with 4GB vs 6GB of VRAM (I see 5.5GB out of my 8GB ). Then there is the Nvidia drivers VS AMD drivers thing.

Edited February 6, 2018 by Sideslip

[Sideslip]

Personal finding on my system: reducing shadows to "flat" reduces stuttering almost completely with all other sliders maxxed out.

 

MSAA 8

AF 16

DF on

global cockpit illumination on

no Lens/flare

preload radius full

visibility high

water high

textures etc high

 

increasing Grass to full does not affect frames nor stuttering,

trees at 87% (increasing more has no visual effect)

 

with vsync on (= frames locked to Monitor) I get steady 60 fps without stuttering.

 

Specs below

 

Wow, 8 X MSAA? You must be running 1080p because there is no way I could get away with that at 3440X1440 with trees enabled. I've decided to use FXAA instead of 2 X MSAA because they look 90% the same (way better than the jaggies) but I get a 33% increase in FPS and can have every single setting maxed out (except civ traffic because... wtf civ traffic).

 

8 X MSAA was what I used in 1.5.8 but 2.5 maxed out I would estimate requires around 3 or 4 times the GPU power (100fps at 80% GPU VS 40FPS at 99% GPU). CPU is much less of a bottle neck though.

[Kev2go]

No it's not that old, but it's also not very high performance. It is similar to the GTX970, which is almost 4 years old and wasn't the top of the line at the time.

 

http://gpu.userbenchmark.com/Compare/Nvidia-GTX-970-vs-AMD-RX-580/2577vs3923

 

You seem to be ignoring the fact that you are running almost 4k of resolution on a card that isn't expected to be able to do so well. And as stated above, a desert map with no trees is not the same thing as the Caucasus map. Have you set trees to 0%? There may have been some small changes to NTTR too. And no it's not supposed to be the same engine. 2.5 has new effects that didn't exist in 2.2.

 

 

Also, the 280X is the minimum requirement for 2.5 and the 580 is only 50% faster. That would mean you could expect good performance at a typical 1080p resolution being 50% above the MINIMUM. By simple math, you'd be bellow the minimum to run even just 2 1080p screens with that card. Resolution and GPU power scale almost perfectly together.

 

 

Errr no.

 

The Rx580 isnt a high end card true . Mid range, but its certainly one the latest available cards in generation from AMD. Basically being a updated Polaris gen 2 ( 14Nm architechture/ updated RX480 technology) with a bit boosted performance.

 

Its not a 4 year old technology In any way, and is a superior in performance to the Nvidia 970. . the RX 580 is comparable to the PAscal generation, Specifically Nvidia Gtx 1060 6gb in dx 11 titles, whilst having superior performance in many DX12 titles compared to it, plus 2 gb additional VRAM.

 

It certainly exceeds Minimum requirements but falls short of the new 2.5 Recommended requirements, which is the 1070, or AMD VEGA 56.

Edited February 6, 2018 by Kev2go

[CNETRO]

Hi to all,

 

I have those stuttering while FPS around 45-80, depending on map.

To get rid of the stuttering I applied the xxJohnxx tips : ctrl+alt+suppr, open the task manger, go to details, right click on DCS.exe and assigne "real CPU" to the game. If not sufficient, assigned all the CPU.

 

 

B/R