[REPORTED]2.5.6 Performance

[SignorMagnifico]

How do you force Physx to cpu only?

 

See instructions here https://www.evga.com/support/faq/FAQdetails.aspx?faqid=59024

[speed-of-heat]

in the NVidia control panel...

 

im certainly not seeing that difference substantial difference ?

[imacken]

I see the opposite effect. In my standard test, i.e. cold start Hornet Super Carrier, I get 25-27fps with PhysZ on GPU, and a solid 22fps when set to CPU.

[Vertigo72]

Like I said, I dont really see how it could help, as Im pretty sure physx isnt used and isnt usable for DCS. ED doesnt support even nVidia's gameworks API in areas where it could be massively useful (hint: VR!) and at the same time physx, if still at all useful, is generally only used for for particle/smoke/cloth and other visual effects.

 

Its more likely you are seeing DCS' inherently variable performance. If you turn off your computer and put it upside down dont be surprised to see see a similar performance boost. Or drop. Try a few orientations and see what works best ;)

 

That said, @imacken, a 5 GHz i7, 2080Ti 32 GB, and 25 FPS.

Ouch.

Edited June 23, 2020 by Vertigo72

[imacken]

Like I said, I dont really see how it could help, as Im pretty sure physx isnt used and isnt usable for DCS. ED doesnt support even nVidia's gameworks API in areas where it could be massively useful (hint: VR!) and at the same time physx, if still at all useful, is generally only used for for particle/smoke/cloth and other visual effects.

 

Its more likely you are seeing DCS' inherently variable performance. If you turn off your computer and put it upside down dont be surprised to see see a similar performance boost. Or drop. Try a few orientations and see what works best ;)

 

That said, @imacken, a 5 GHz i7, 2080Ti 32 GB, and 25 FPS.

Ouch.

 

The 25 is VR on deck Supercarrier. The worst case scenario by a long way, except for over towns in the Channel map!

 

Pretty solid 45 everywhere else.

[SignorMagnifico]

Like I said, I dont really see how it could help, as Im pretty sure physx isnt used and isnt usable for DCS. ED doesnt support even nVidia's gameworks API in areas where it could be massively useful (hint: VR!) and at the same time physx, if still at all useful, is generally only used for for particle/smoke/cloth and other visual effects.

 

Its more likely you are seeing DCS' inherently variable performance. If you turn off your computer and put it upside down dont be surprised to see see a similar performance boost. Or drop. Try a few orientations and see what works best ;)

 

That said, @imacken, a 5 GHz i7, 2080Ti 32 GB, and 25 FPS.

Ouch.

 

There is something going on with PhysX and DCS. When set to CPU, the MiG21 frame rate bug goes away. With PhysX set to GPU, my FPS drops to 30 or less, with CPU I can maintain 80. Doesn’t have as big of an effect on other modules, though, but something is going on there.

[Vertigo72]

IIRC that mig problem was limited to the latest nvidia driver. So maybe nvidia screwed something up there that you are "unscrewing" with changing that setting.

[SignorMagnifico]

There is something going on with PhysX and DCS. When set to CPU, the MiG21 frame rate bug goes away. With PhysX set to GPU, my FPS drops to 30 or less, with CPU I can maintain 80. Doesn’t have as big of an effect on other modules, though, but something is going on there.

 

Updated to nVidia drivers 451.48. MiG-21 FPS bug is now present regardless of PhysX CPU or GPU preference setting. Makes no difference in FPS in other modules. Oh well.

[Mr. Big.Biggs]

I was tooling along great today in the aerobatics server. All was great then suddenly stutter city. I noticed at that moment my “VID” % usage dropped and my “BUS” usage spiked. Only way to make things “normal” was to reboot machine. Anybody take away anything from this observation?

Thanks

[Reflected]

I was tooling along great today in the aerobatics server. All was great then suddenly stutter city. I noticed at that moment my “VID” % usage dropped and my “BUS” usage spiked. Only way to make things “normal” was to reboot machine. Anybody take away anything from this observation?

Thanks

 

 

Yes, see here:

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

[Shadoware]

How is current open beta quality compared to 2.5.6 available on Steam?

 

Should I move to Open Beta or stay in current version?

[mrmat01]

I'm just getting Piss poor frame rates in general.

I was getting excellent FPS solid 50 FPS before the the last couple of updates now OB is just unplayable.

Averaging 15 FPS & THIS SUX :cry: I cant fly the P-47.

I have a module that I paid for that I can not fly. I think this started when the lighting for the cockpit was updated. Fairdinkum why would you release something this broken. :mad:

 

My PC specs

Intel 8700k

32GB DD4

GeForce RTX 2060

Dedicated 500gb SSD

 

It should not be running this bad. :furious:

Edited July 1, 2020 by mrmat01

[mrmat01]

How is current open beta quality compared to 2.5.6 available on Steam?

 

Should I move to Open Beta or stay in current version?

 

 

Stay on stable OB is very broken

[bell_rj]

Are you playing single player or multiplayer? VR or non-VR?

 

What is your graphics resolution?

 

What are your graphical settings?

 

I run a 1070ti and get much better frames than you with the latest open beta build. Therefore, I suggest the problem is not necessarily the code as such (not withstanding that it could be better optimised). Please post your settings and we may be able to help you.

[mrmat01]

Are you playing single player or multiplayer? VR or non-VR?

 

What is your graphics resolution?

 

What are your graphical settings?

 

I run a 1070ti and get much better frames than you with the latest open beta build. Therefore, I suggest the problem is not necessarily the code as such (not withstanding that it could be better optimized). Please post your settings and we may be able to help you.

 

 

Single player No VR

Pretty high Graphics setting been running the same setting for over a year.

resolution 2560x1440

 

It was running fantastically a couple of weeks ago before the update I was getting 40-50 FPS on the Super Carrier. Now I get from 5-15 & its just as bad on Caucuses map

I get a solid 50 FPS on stable With the same settings Its the OB.

[Eaglewings]

Single player No VR

 

Pretty high Graphics setting been running the same setting for over a year.

 

resolution 2560x1440

 

 

 

It was running fantastically a couple of weeks ago before the update I was getting 40-50 FPS on the Super Carrier. Now I get from 5-15 & its just as bad on Caucuses map

 

I get a solid 50 FPS on stable With the same settings Its the OB.

15fps is pretty low for that resolution.

Some bug fixing are in the works. Let hope major issues like fps issues are addressed in July open update.

You could check your nvidia graphic settings and see if settings are good.

2d play gives very good frame for me on gtx 1060 (60-122fps depending on situations).I get by in vr fine on low settings.

Check SSLR is off in dcs graphic setting. SSLR was introduced fairly recently. SSLR is an fps eater.

Edited July 1, 2020 by Eaglewings

[mrmat01]

15fps is pretty low for that resolution.

Some bug fixing are in the works. Let hope major issues like fps issues are addressed in July open update.

 

Yep its off uploaded an old screen shot.

Nvidia setting are good haven't changed them either.

Well they better bloody fix it because it is unplayable at the moment.

Wouldn't hurt if ED rolled it back so its not so broken.

Hopefully this sort of thing will stop now that they aren't just throwing updates out there & hoping for the best.

I hate coming down on ED like this but they really dropped the ball on the last couple of updates.

[speed-of-heat]

15fps is pretty low for that resolution.

Some bug fixing are in the works. Let hope major issues like fps issues are addressed in July open update.

 

Yep its off uploaded an old screen shot.

Nvidia setting are good haven't changed them either.

Well they better bloody fix it because it is unplayable at the moment.

Wouldn't hurt if ED rolled it back so its not so broken.

Hopefully this sort of thing will stop now that they aren't just throwing updates out there & hoping for the best.

I hate coming down on ED like this but they really dropped the ball on the last couple of updates.

 

Visbility Range to High

Shadows - > Off

SSAA -> Off

Chimney smoke -> 1 or off

 

should make the world of difference to your perf...

[mrmat01]

 

Visbility Range to High

Shadows - > Off

SSAA -> Off

Chimney smoke -> 1 or off

 

should make the world of difference to your perf...

 

Thanks mate I will give it a crack

But like I said earlier I have been running the same settings for the last year & getting really good FPS.

[speed-of-heat]

understood :)

 

but shadows seem to have been a bit of a hit in 256 SSAA costs mega perf, i cant run it reliably, though a lot depends on your headset ...

 

also be aware the channel and 47 are in early dev... so YMMV

[SignorMagnifico]

15fps is pretty low for that resolution.

Some bug fixing are in the works. Let hope major issues like fps issues are addressed in July open update.

 

Yep its off uploaded an old screen shot.

Nvidia setting are good haven't changed them either.

Well they better bloody fix it because it is unplayable at the moment.

Wouldn't hurt if ED rolled it back so its not so broken.

Hopefully this sort of thing will stop now that they aren't just throwing updates out there & hoping for the best.

I hate coming down on ED like this but they really dropped the ball on the last couple of updates.

 

Here's a screenshot of the settings I'm using now. SSAA is unreliable at the moment and I find that MSAAx4 with MFAA enabled in nVidia control panel looks better and costs less. I get about 100 FPS at altitude, 80FPS on the deck in most cases. In supercarrier, FPS drops to about 30 - 40, and in the MiG-21 with radar on my FPS is lol.

[Charly314159]

Yes maybe that to have VR running properly we should all turn off shadows, that would save ED the burden of optimizing their code.

And maybe also we should turn off clouds and AI since they have a negative impact on performance. Also I noticed than MP was more stuttery than SP so we should stick to the second. And who would need proper anti aliasing when it removes all the shine and sparkles of this beautiful undersampled game...

Edited July 3, 2020 by Charly314159

[BIGNEWY]

Make sure you have SSLR and MSAA off, they are frame killers, after that try with shadows off or reduced.

 

I have a new machine now, and performance is great for me, it is obviously a pretty beefy machine, but I am getting a solid 45FPS near the ground and 80+ in the air.

 

Edited July 3, 2020 by BIGNEWY

[30mikemike]

 

Here's a screenshot of the settings I'm using now. SSAA is unreliable at the moment and I find that MSAAx4 with MFAA enabled in nVidia control panel looks better and costs less. I get about 100 FPS at altitude, 80FPS on the deck in most cases. In supercarrier, FPS drops to about 30 - 40, and in the MiG-21 with radar on my FPS is lol.

 

I’m running MSAA x2 & SSAA at 1.5. Do you think it’s worth me trying your method of MFAA instead? I’ve never tried it to be fair. Does it still sharpen things up nicely like SSAA?

[SignorMagnifico]

 

I’m running MSAA x2 & SSAA at 1.5. Do you think it’s worth me trying your method of MFAA instead? I’ve never tried it to be fair. Does it still sharpen things up nicely like SSAA?

 

 

Really you should only be using one form of antialiasing at a time. MSAAx4 with MFAA enabled looks better to me and costs less than SSAA at 1.5 or 2x. Mixing antialiasing results in significant performance loss. The only one that makes sense to combine would be FXAA, since it has a minimal performance cost, but I don't like how FXAA looks and leave it off. MFAA basically reduces the cost of MSAA by 50%, so MSAA x4 with MFAA enabled has the performance hit of MSAA x2.

 

https://www.nvidia.com/en-us/geforce/news/multi-frame-sampled-anti-aliasing-delivers-better-performance-and-superior-image-quality/