Optimization, or: How to play at a silky smooth 20 FPS

Jun 30th, 2015
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. ---Shitty, retarded .ini tweak guides---
  2. In the past, certain settings could only be changed by editing UserOptions.ini, but the interface has since been updated to allow for changing all the important settings (sans RenderQuality and the newly-implemented framerate smoothing) in-game. If you've found a guide claiming to double your framerate and graphic quality by setting everything to "5", they don't know what they're writing about.
  4. Remember, SOE put thousands of combined man-hours into PU01 - if fixing performance were as simple as changing a few .ini settings, you can bet your tits it's the first thing they'd have tried.
  6. For the few tweaks that do require .ini modification, the easiest way to get to the relevant file is to open the launcher, click the engineer icon and find the "open game directory" option. Find UserOptions.ini and open it in a text editor such as Notepad++.
  8. Unless otherwise noted, every tweak in this guide should be set through the in-game graphics menu.
  10. ---FPS Counter---
  11. First off, while in-game, type /fps in the chat box to display the FPS counter; if next to it reads [CPU], that means your CPU is the bottleneck for FPS; likewise, if it reads [GPU] your GPU is the bottleneck. If there is no [CPU]/[GPU] next to your FPS counter, framerate smoothing is probably capping it out at 60, or the game client hasn't rendered enough frames to decide where the bottleneck is yet.
  13. ---The Graphics Menu---
  14. - Resolution, Brightness, VSync:
  15. These should be self-explanatory if you've played any PC game. Figure it out.
  17. - Display Mode:
  18. Full Screen usually runs the best, Windowed mode runs in a window, Fullscreen Windowed runs in a window set to the same dimensions as your monitor. It's usually best to leave this on Full Screen for performance, but alt+tabbing will be slower and will occasionally cause a client crash as a result. Fullscreen Windowed will generally run slightly slower, but alt+tabbing should be instant and shouldn't crash.
  20. Note that your brightness setting only works in Fullscreen mode: on windowd and fullscreen windowed, you're always stuck at the darkest brightness setting.
  22. - Render Quality:
  23. This is a multiplier for the resolution your game is rendered at. At 100% (1.0), the game is rendered at a ratio of 1:1 for your resolution, no up or downscaling. At 50% (0.5), the vertical and horizontal resolution the picture is rendered at is multiplied by 0.5 independently (1920*1080 -> 960*540), or effectively 1/4th resolution, then upscaled. At 0.75 the game is rendered at 1/2 resolution and upscaled (1920*1080 -> 1440*810). For settings above 1.0, see ---Supersampling--- below. This setting has a major impact on FPS, but reducing it also dramatically reduces graphical quality.
  24. Some users experience a bug where some things, such as terminals or the optics' dots, aren't rendering. To solve this, set render quality to 99% instead of 100%.
  26. - Vertical Field of View (vFOV):
  27. This isn't the same as hFOV that most other games use (unless your monitor is perfectly square), but obviously affects hFOV too. Low settings can cause motion sickness in some users.
  28. At an aspect ratio of 4:3, 74 vFOV equates to 90 hFOV.
  29. At 16:10, 74 vFOV = 100 hFOV; 64 vFOV = 90 hFOV.
  30. At 16:9, 74 vFOV = 104 hFOV; 59 vFOV = 90 hFOV.
  32. A typical setting for most PC games is ~90 hFOV, but the more competitive types tend to max their setting out at 74 vFOV.
  34. Here's a calculator to convert between vFOV and hFOV for your screen resolution:
  35. http://www.rjdown.co.uk/projects/bfbc2/fovcalculator.php
  37. - GPU Particle Quality (PhysX):
  38. As of PU01, SOE has disabled GPU physics because it conflicted with some of their optimizations and are waiting for nVidia to fix it before it's re-enabled.
  40. - Render Distance:
  41. This adds a wall of fog beyond a certain distance, in meters, and stops rendering anything beyond that fog. Low settings should be avoided by pilots, and can completely block visibility of the ground while drop podding. A setting around 2500 or so is recommended, and should provide a slight performance increase without much of a graphical impact. Note that this doesn't affect infantry or vehicle render distance (300 and 700m, which automatically lowers in very high-pop areas) unless set extremely low, only static terrain and props.
  43. - Smoothing:
  44. Enables FPS smoothing, which essentially dynamically caps framerate to prevent large FPS swings and make lower FPS feel more playable. This can be tweaked through .ini editing, see ---Framerate Smoothing--- below.
  46. - Overall Quality:
  47. Presets for subsequent settings. Leave this alone if you're going to fiddle with the other settings manually.
  49. - Graphics Quality:
  50. This setting has a fairly dramatic effect, both on the game image and GPU utilization. High includes all the bells and whistles, bloom, atmospheric fog, smoke and so on. Medium disables certain superfluous effects, but also breaks Thermal/IRNV optics. Low disables even more superfluous effects, breaks Thermal/IRNV slightly less than medium, significantly reduces the impact of smoke grenades and variably breaks cloaked infiltrators (occasionally makes them very visible, other times completely stops their model from being rendered at all, which one of these it does varies wildly from patch to patch). This seems to be where DGC dumps all their graphical settings that they can't be bothered making separate options for.
  52. - Texture Quality:
  53. Controls the resolution of textures on almost everything. This setting has almost no effect on FPS. Only set below ultra if your GPU doesn't have very much vRAM. Indeed, on some systems, using a setting lower than Ultra will actually decrease FPS.
  54. That's because ultra uses the standard textures, whereas lower settings take the standard textures, compress them, and then use those: this puts less stress onto your GPU, but it adds load to your CPU, which is already performing a fuckload of operations.
  56. - Lighting Quality:
  57. Subtly changes some lighting effects. While GPU-limited, has very little effect on FPS, maybe 3-5% between low and high. There's also almost no graphical change between low and medium, but medium will perform slightly worse than low. This setting should probably be left on high.
  59. - Shadow Quality:
  60. This setting controls how shadows are rendered, and will significantly impact FPS on CPU-limited systems - the FPS hit between high and off can be anywhere between 20 to 50%. Also taxes the GPU slightly, but not that much. Off doesn't render shadows at all and looks awful, but can dramatically improve FPS. Low renders very simple shadows and only at close range. Medium renders better shadows out to slightly longer range. High renders medium-style shadows out to even further range.
  62. - Fog Shadows:
  63. Renders shadows through fog, which increases graphic quality very slightly in exchange for a noticeable FPS hit. Turn this off if you want a few extra frames in exchange for a very minor quality hit.
  65. - Effects Quality:
  66. Allegedly changes the quality of explosions, in practice really doesn't have any measurable effect on graphics or FPS whatsoever. Just set it to whatever, it doesn't matter.
  68. - Terrain Quality:
  69. Like "Effects Quality", this setting doesn't actually do anything either. Just set it to whatever, it doesn't matter.
  71. - Flora Quality:
  72. This setting controls flora quality (grass, bushes, tree leaves and so on), and has a slight effect on CPU-limited systems, but nowhere near as much as shadows. Settings between high, medium and low only seem to change flora resolution slightly, and not much else. Off completely disables most flora. For performance, turn this setting to low or off.
  74. - Model Quality:
  75. This setting controls LoD for models: lower poly-count models will be used as distance from the player increases on lower settings, which will moderately increase performance on GPU-bound systems for very little graphical impact.
  77. - Particles:
  78. This setting controls LoD for particles. Reducing this setting will provide a slight-to-moderate FPS increase on GPU-bound systems, and will generally render fewer particles over longer distances.
  80. - Motion Blur:
  81. Currently disabled by SOE; when it works it blurs the screen slightly any time the camera is being turned, in exchange for a small FPS hit. Many players find this effect annoying.
  83. - Ambient Occlusion:
  84. Subtly improves graphical quality for a moderate FPS hit on GPU-bound systems.
  86. - Bloom:
  87. Turning this off reduces bloom - you know, the blinding effect from bright things - down to a less blinding level. This setting probably doesn't do much for performance, but turning it off does improve visibility under some circumstances.
  88. However, if you're going to use thermal sights, it is recommended that you play on high graphics quality and with bloom on, as this marshes thermals much more usable.
  90. ---Framerate Smoothing---
  91. Here's one of the few settings partially only modifiable through the .ini. By default, framerate smoothing attempts to keep your FPS around a consistent value by capping the maximum value at 60, and smoothing it out if it's between 20 and 59. DGC recommends leaving this turned on in order to prevent overuse of hardware (e.g. FPS at 500 and CPUs/GPUs on fire in menus), and to lessen the impact of frames that take unusually long to render for whatever reason.
  93. In UserOptions.ini, under [Rendering], add the lines:
  94. SmoothingMaxFramerate=60
  95. SmoothingMinFramerate=20
  97. Set SmoothingMaxFramerate to the refresh rate of your monitor; if it's an LCD and you're unsure, this is almost always the default of 60. If you're still a dinosaur with a CRT or have a 120Hz monitor, this can be different.
  98. SmoothingMinFramerate is the value at which smoothing automatically disables itself. Either leave this at default, or change it to whatever you think is a good value.
  100. For more information, see: https://forums.station.sony.com/ps2/index.php?threads/frame-rate-smoothing.155313/
  102. ---I'm CPU-limited, what do?---
  103. A note on being CPU limited: previously, the vast majority of people was CPU limited, mainly because of DGC's incompetence. The game now uses some form of multithreading, so a fair share of people is GPU limited. If you're not new to the game but coming back, your performance will likely be much better now.
  104. - Try normal Fullscreen mode; if already on Fullscreen mode, try False Fullscreen. Use whichever performs better on your system.
  105. - Turn off Shadows and Fog Shadows (this looks fairly ugly, but has a huge impact on performance)
  106. - Turn Flora to low or off (this will also help, but much less than shadows)
  107. - Leave everything else on high/ultra
  109. ---I'm GPU-limited, what do?---
  110. This usually means that your framerate is already fine, or you're running a toaster.
  111. You can choose to:
  112. - Turn down Model Quality, Particles, and turn off Motion Blur and AO.
  113. - Turn off Shadows
  114. - Turn down Render Quality (try not go go lower than 70%, the game starts looking really ugly then)
  115. - Try a lower resolution (running at your monitor's native resolution is highly recommended; if you can't do that, try picking a resolution with the same aspect ratio)
  116. - Try GustavoM's potatomode settings - but don't get your hopes up
  117. - Purchase or assemble a more powerful computer
  119. ---Supersampling---
  120. If you're CPU-bound, especially with a very powerful graphics card, but want to improve the look of the game without FPS loss, you can opt to increase RenderQuality in the .ini, which enables supersampling.
  122. A setting of 1.0 is default, which renders the game at 1:1 resolution. 1.414 (sqrt(2)) renders the game at 2x resolution (if 1920*1080, that's effectively 2715*1527), 1.732 (sqrt(3)) = 3x res, 2 = 4x res, 3 = 9x res, etc.
  124. Modern high or medium-high end PCs ought to be able to handle 1.414 without too much issue, beyond that is getting into the realm of Titans and the like. You might also consider values less than or between these, but remember that any value set is the square root of what your effective resolution will be before downsampling, so "1.5" renders at 2.25x res.
  126. If you're playing specifically to take screenshots, don't be afraid to crank this setting up really high, which will make the screenshots look great.
  128. Give it a shot, but dial it down if you start getting poor framerates while being GPU-bound.
  130. ---Toaster Mode: Sound Settings---
  131. Some users report squeezing out a couple more FPS on very low-end machines by changing their sound settings. In UserOptions.ini, under [Sound], change the following settings (add a new line if they're not already there):
  133. MaxVoices=20 (Last resort setting, this will cause many fewer sounds to play concurrently. Default is 96. Optionally set it higher or leave this alone.)
  134. SampleRate=1000 (Also a last resort setting. PS2 internal default is 192k, and Windows default is 44.1k, so this can alternatively be set to 41000 to very slightly reduce CPU load with less distortion)
  135. UseFloat32Output=1 (This will reduce CPU usage and increase sound quality slightly. According to SOE, this causes distortion on a minority of shitty sound drivers so it's turned off by default.)
  137. ---Super potato mode---
  138. If your toaster REALLY can't run this game but you REALLY want to play it, you can opt for the super potato mode. Be aware, this isn't going to be pretty, but it should give you a decent framerate.
  139. AMD: http://pastebin.com/vraspTTT
  140. NVidia: http://pastebin.com/MhiH3UBs
  142. ---
  144. For posterity, the old, outdated optimization pastebin can be found at the following: http://pastebin.com/MEqFBUut
  145. Last updated: July 2015
RAW Paste Data