Results 1 to 20 of 34
03-01-2012, 02:51 PM #1
A few simple notes on performance.
With performance, I mean how well Arma runs on your computer. I do not mean your performance in shooting other people. The ARPS group does not care about scores (I do care about my own score, but that is because I am bloodthirsty, and an exception). This page is about making Arma run decently fast. You will be aiming for something 'round 20 fps, and things generally are playable. If you are struggling to reach playable framerates, here are a few notes:
Interface resolution should always match 3d resolution.
You will notice that ARMA has two settings for resolution: Interface resolution (the resolution of the menus) and the 3d resolution (the resolution of the actual gameplay). Although this sounds like a neat idea at first, to keep the interface resolution at your display's native (say, 1080p) and reduce 3d resolution (say, 720p), it does not work half as well as it should. In fact, it may actually reduce performance. Therefore, if you want to reduce 3d resolution, reduce interface resolution accordingly (so that 3d resolution is always 100%). I recommend that you only lower your resolution after setting all your other settings to "very low" or similar, and keep 3d resolution at your display's native.
Set "Video Memory" to default
Doing so allows Arma just to use everything at its disposal.
Just do it. Enjoy the greatly increased performance.
Check your "AToC" setting in Arma2oa.cfg in your My Documents/Arma 2 folder when using Anti-Aliasing
Arma was one of those games that did not have "Alpha to Coverage Blending" (neither does Crysis, by the way, so much for fancy graphics!). AToC enhances anti-aliasing for textures that use a lot of transparacy, such as tree leaves. The downside to this is that performance is reduced when using AToC, and since the patch that has introduced it, it has been enabled by default. The default setting is 7, which means all the foliage. You can set it to 0 which disables AtoC for an additional performance boost. Here's what each setting does:
0 - disabled
1 - AToC on grass
2 - AToC on new OA trees (takistan, zargabad, proving ground, shapur)
4 - AToC on old A2 trees (utes, chernarus)
3 - AToC on grass & OA trees
5 - AToC on A2 trees + grass
6 - AToC on A2 + OA trees
7 - AToC enabled on grass, A2 & OA trees (default)
Note that disabling anti aliasing will also disable AToC.
Check your FXAA setting while you are at it.
FXAA is "fast aproximate anti-aliasing", a post processing form of anti aliasing. This setting runs independenlty of the normal anti aliasing, so disabling anti aliasing will not affect this setting. Neither will AToC have anything to do with this, FXAA sia post processing filter. However, disabling post processing in the game does not affect FXAA. This is set to 'off', by default. This setting goes from 0 to 17, where 17 is the most power hungry mode available, and 0 is completely disabled. FXAA can be used along with 'normal' anti aliasing for an enhanced effect.
Each number corrosponds to a certain FXAA quality preset:
0 - Disables
1 to 6 - FXAA quality preset 10 to 15
7 to 16 - FXAA quality preset 20 to 29
17 - FXAA quality preset 39
This page by FXAA's creator explains a bit more what each quality preset means.
When setting post processing to "Low" or higher, remember to use Okt-NoBlur
This removes the annoying motion blur which only works well if you have very high FPS (so, never), and increases your performance.
Your performance will be significantly higher whilst playing online
Arma is probably an exception in this, but your performance will increase greatly due to the server doing all the neccesary CPU calculations for you. So even if you have FPS on the low side but have no interest in playing SP, all will be well.
Now, there are obviously some other settings in the Advanced Video Settings tab in the Arma 2 options screen. I have tested each value, and here are my reccomendations per value. I recommend that you set everything except video memory to very low or off at first, and then change accordingly to match your needs.
Resolution: I recommend setting both to your display's native resolution. I recommend that you keep it there, and only change it to lower if you absolutely need that performance.
View Distance: This is probably one of the major factors in Arma performance and playability. This factor can influence gameplay. I recommend putting this at 1600 at first, which is AFAIK the maximum range of the longest range sniper rifles in the game. Only lower this if you absolutely need the performance, but it is not as vital as resolution. (the original operation flashpoint had 900 as the default, which works too. If you really have to set it lower then this, you may need to seek elsewhere to fix your performance problems). Most missions set View Distance to a value specified by them, so don't worry about any PvP missions: They have fixed view distances which are the same for everyone.
Texture detail: Set this to match your video memory. I have not detected any performance loss or increase by changing this value, whilst there is an obvious difference in quality. Note that, if you set this higher then your video memory, your video memory will change along with it, but if you putit down again, your vid mem will stay the same.
Low = 256 mb
Medium = 512 mb
High = 768 mb
Very high = 1 gb
Video Memory: See above, - Set this to default. If you are having problems, you may want to change the hting according to your graphic's card onboard memory:
Low to high = Unknown.
Very high = 512mb
Note that these values are estimates, and that I do not know what happens if you put stuff too high.
Anistropic Filtering: A really nice algorithm which affects the sharpness in textures that are drawn further away from the player, and which the player is not looking directly at. Noticable on the ground. Very noticable on the roads.
Low - 2x anistropic filtering. Makes a small difference.
Medium - 4x anistropic filtering. Makes quite a bit of difference, although stuff that is quite far away still is a bit blurry, but not blurry enough to stand out.
High - 8x anistropic filtering. Nothing is blurry.
Very high - 16x anistropic filtering. No discernable difference between this and high.
Anti Aliasing: Increases resolution around edges so you get less jaggedness. Note the AToC notes above: If disabled, trees will not be affected (But AToC is enabled by default).
Low = 2x MSAA
Medium = 4x MSAA
High = 8x MSAA
Very High = 16x MSAA
Note that you can use FXAA as well with an ini setting. See above. FXAA can be used in conjuction with or without MSAA, as it is a postprocessing setting. FXAA can make AToC redundant as well.
Terrain Detail: Mainly influences the distance at which grass is drawn.
Very low - (Almost) no grass drawn, depending on location and map.
Low to very high - increased grass draw distance.
Terrain detail also affects terrain geometry (how many pixels a mountain uses), but I was not able to see any noticable differences. There might be significant effects when sniping from long distances, however. Men at very long distances seem to clip trough the ground somewhat, probably the effect of optimizations. Setting the setting to very high whilst sniping might resolve those visual glitches.
Object detail controls the amount of objects drawn in the Distance as well as LOD switching (LOD switching is switching a detailed model for a less detailed one when it is further away). It also controls how far away objects are drawn. Very low means very little grass and no objects in the distance, whilst medium means lots of grass and quite a few objects in the distance, and very high means same amount of grass as with medium along with every tree rock and such being drawn in the distance
Note that the drawing of grass is also a setting which can be specified per mission. So don't worry if you think that changing these settings gives you an unfair advantage: in PvP missions (and some performance hungry co ops), this setting is set in stone and the same for everyone.
Shadow Detail: This can be set entirely to your prefference.
Normal - Very basic shadows which are very sqaurical and blocky. IMO it does not look good. Think square shadows for round objects.
High - Good shadows. They appear to be a bit blocky when you look at them in detail, but you don't most of the time.
Very high - same as high, but now they never look blocky.
HDR Quality: You can't turn HDR off, and changing this setting does not appear to affect image quaility for me, but it does affect performance greatly. Keep it at Normal.
Very low - "Noise", found using night vision goggles and the 80s filter used in some folk missions, as well as some other effects which are applied to the entire screen. This setting does not affect performance.
Low - Adds bloom and motion blur. You can disable motion blur using the okt_noblur mod (linked above). Motion blur affects performance quite a bit, but bloom not so much.
Medium - Adds Depth of Field (blurs objects at certain distances to simulate that the eye can not focus on everything) and SSAO (a form of self shadowing, which greatly enhances the look of several objects in the game, including the grass). There is no option for enabling them seperatly, and I do not know of any mods which mods them, so it is either both or none. SSAO greatly affects performance, but it looks great.
High and Very High - more performance hungry and better looking SSAO
Interface size: Does not affect performance. Change to suit your own tastes.
Aspect ratio: A no brainer.
Vsync: Always turn it off.
Audio Channels: A feature found under "sound", Audio Channels determines how many sounds can be played at once. OA set this to 32 by default, whilst Arma 2 sets this to 16 by default. However, this only impacts performance when you have an on-board soundcard (on board soundcards draw processing power from the CPU). If you happen to have a soundblaster or similar audio card, you can set this to 128, which can solve some sound glitches you might experience whilst rapidly firing hydra rockets and/or using JSRS. I highly recommend that you get a sound card, because now that I have one, I can not live without it :D.
Some Ini Tweaking:
Yes, you can tweak INI files. Noticably, when going to your "My Documents folder", try and find the .arma2profile and .arma2oaprofile files. You will see a lot of text. Now find these values and set them to this:
sceneComplexity=150000; ShadingQuality=0; MouseSmoothing=1;
Note that you have to change the settings both in *.arma2profile as well as *.arma2OA profile in order to see an effect, for some reason.
Some usefull links:
Some things concerning processors. The BIS thread on optimizing performance.
Custom Memory Allocators (added in the 1.6 patch). Try and see if it makes a difference for you. So far, I have gotten the best results with the "TCmalloc".
Last edited by Grizzly; 19-07-2012 at 11:15 AM.
03-01-2012, 03:15 PM #2
- Join Date
- Dec 2011
I assume I will be ok with a HD5870 and Phenom II 3.4GHz quad core? I don't expect perfection, but I'd like to see some detail.
03-01-2012, 03:21 PM #3Shadow Detail: This can be set entirely to your prefference. Note that Normal means very blocky shadows, whilst high menas shadows which actually appear to be based on the models casting them. Very high means really detailed shadows. Higher is more performance hungry. Personally, I switch between off and high depending on my mood, but keep away from normal because I think they are too ugly.
Terrain Detail: Mainly influences the distance at which grass is drawn. Higher values mean that grass is drawn at longer distances. This greatly affects performance. I have personally set this at very low, since grass is not that important for me.
03-01-2012, 03:32 PM #4
Cheers! This actually gave me a lot of FPS at very little actual cost to my experience in the game. Much appreciated.Snatching defeat from the jaws of victory since 1982.
03-01-2012, 03:45 PM #5
First of all, I salute you for this post Grizzly. Here's a medal, but you need to return if after the photo op.
Keep in mind though that you will NEVER get framerates like you get in other games on good-looking settings. For whatever reason ARMA2 is the most power-hungry game ever and getting a steady FPS of 60 everything maxed on a good resolution is not going to happen.
03-01-2012, 04:00 PM #6
Glorious thread, Grizzly!
Defines max memory allocation as limit. Not sure how this works after 1.60 with allocators, if at all effected/affected?
Reverts to use of older Direct 3D for Vista/Win7 systems. "... the most visible feature the Ex version offers is a lot faster alt-tabing".
That and more, with descriptions, at: http://community.bistudio.com/wiki/A...tup_Parameters
03-01-2012, 09:47 PM #7
04-01-2012, 06:55 PM #8
- Join Date
- Jun 2011
Grizzly, you are a beautiful bear. I will read through this during the weekend and set up my copy properly.
09-01-2012, 01:51 PM #9
- Join Date
- Jun 2011
Thanks Grizzly for this, I applied some of the changes before last night's game. I think it run better, although now I notice the tearing with the Vsync off (I always thought I had it off but turns out not to be the case). Couldn't verify though as my Arma crashed when I use any application to measure FPS. In any case, it felt smoother!
09-01-2012, 07:03 PM #10
- Join Date
- Dec 2011
Well, the Op Arrowhead benchmark tells me I get an average of 58fps, which is enough, I think :D
09-01-2012, 08:29 PM #11
Also, I keep updating the post, so keep checking for some hints. I may need to restructure it, but some others are probably better at ensuring that information is... well-presented.
09-01-2012, 11:01 PM #12
- Join Date
- Dec 2011
Ah yes...average FPS of 20. Plenty of explosions in that one.
10-01-2012, 10:56 AM #13
Getting 20 FPS on the second one is extremely good, feel free to pat yourself on the back now.
10-01-2012, 11:01 AM #14
Lowest of all settings, running in windowed mode 800 x 600:
first benchmark: 15 FPS.
second benchmark: 10 FPS.
I'll go cry in that corner now.
10-01-2012, 04:46 PM #15
10-01-2012, 05:00 PM #16
Processor: Intel Core i5 CPU M 450 @ 2.40 GHz
RAM: 4 GB, 3.79 GB avail.
NVIDIA GeForce 310 M
DirectX version: 11.0
DirectX support: 10.1
CUDA Cores: 16
Total available graphics memory: 2707 MB
Dedicated video memory: 1024 MB DDR3
System video memory: 0 MB
Shared system memory: 1683 MB
10-01-2012, 06:30 PM #17
Every time I see this thread I think of the same topic often found in my spam email folder.
That's all, Carry on.All times I have enjoyed greatly, have suffered greatly, both with those that loved me, and alone.
10-01-2012, 08:26 PM #18
Also, dailing down the view distance to 900 or even 500 may help, although 500 might give you some problems shooting men. You should try it out.
Also, you were using hte Arma 2 benchmarks... Chernarus is rather power hungry for some reason.
30-01-2012, 08:34 AM #19
I made a few changes to the guide - Apperently, setting Video Memory to default is much better for performance then just setting it manually, as default sets it to how it should be: Arma uses every bit of your video card.
21-05-2012, 08:35 AM #20
- Join Date
- Apr 2012
A quick question about the okt_noblur. Ever since I've installed it I can't connect to any DayZ server because "@okt_noblur isn't signed by a key accepted on this server". Does it mean I did something wrong or should I just wait until they add this plugin to their whitelist?