Comparatively horrible frame rates

[creed]

Hello everyone,

I've just updated to from DCS: A-10C 1.1.1.1 to 1.2.2 (and so am now running World), but whilst I was getting a little less than 40 FPS with the settings shown in the attached screen capture at Batumi, this is now more like 20. The settings I'm using are identical in all categories which are the same, and in all new categories, on a low setting.

My system specs are as follows; an i5 2500k on a P8P67 running at 3.9 gHz, 8GB of RAM at 1600mHz, a 7200RPM HDD, an Asus GTX460 (stock speed) all running Windows 7 Pro 64 bit.

I'd like to ask if this is to be expected with DCS: World, or if this is due to something else, and if so, do you have any suggestions regarding how to fix it.

Thanks,

Charlie

[BIGNEWY]

512 every frame will be a hog on resources

[Jona33]

Go 512 rather than 512 every frame. Might help.

[creed]

hmm, I just tried getting rid of HDR lighting, it doesn't look as pretty, but it seems to have done the trick.

Thanks,

Charlie

[Lange_666]

OK but then looking at the screenshot of your previous settings, HDR was on in 1.1.1.1 and now it isn't anymore so your actual settings are lower just to give you the same result.

Which means World performs less good then standalone 1.1.1.1 (which confirms my own test results).

[f-18hornet]

Reduce your MSAA from 16x to 8x or 4x. It takes a lot of performance too.

[FZG_Immel]

same.. from A-10 to World, I went from 80FPS to 50FPS with the same settings..

[ENO]

Question for you guys-

 

Does high fps on a client side have an impact on how frequently the server needs to send data? If an update on vehicle movement needs to be sent to 120fps versus 40... That would be a pretty big draw on resources...

 

Or am I away off?

[msalama]

Does high fps on a client side have an impact on how frequently the server needs to send data?

 

Probably not, because shouldn't the server only tally events created by clients and then distribute / resend them? A highly loaded or connection-restricted client mightn't be able to send data as fast as the situation called for and thus induce lag and warping, but that's a different problem altogether and not the server's fault as such IMO.

 

Or that's my guess anyway, having not seen how they designed and coded the bugger :)