#How to use sweetfx with fps limit Patch
#How to use sweetfx with fps limit Pc

Optimization friendly - Useful addons that can be configured to use less resources (and how).To enable borderless window mode press Esc -> Customize Interface -> Video tab and deselect Show Frame and Use Fullscreen checkboxes.īelow I list addons that have the most impact on performance and separate them in to three groups: According to some relevant information I found on stackoverflow the penalty is negligible. Borderless window mode performs slightly worse than fullscreen mode.Using settings menu to change window modes causes no issues. This only happens when using the key combination. If you then try to reload UI the client will crash. For example, group icons in Enemy will stop scaling correctly. Switching back to fullscreen mode by pressing Alt+Enter will mess with some addons.Running the game in a borderless window fixes this issue but has two drawbacks: Tabbing in and out of the game while in fullscreen mode triggers a painfully long mesh retexture:

#How to use sweetfx with fps limit Pc

If you are playing on a laptop or an older desktop PC I would not recommend changing this setting.įullcreen VS Borderless window - which is better? If you are playing on a computer with a dedicated graphics card that has 1GB+ of VRAM you are likely to benefit from maxing the slider. Judging by the testing I've done it looks like increasing the slider does make the game use more VRAM: Texture memory cache - does it actually do anything? On a lower end computer I would also turn off grass. If you are crashing during keep fights the first thing you should do is set Shadows to None or Balanced and set ability filter to Self. Worst offenders for your framerate are Effects and Shadows settings. Here is the most balanced setup in terms of performance vs quality that I could find: This means that UI actions should execute quicker. The other thing it does is disable the 'debug' version of the LUA library.

#How to use sweetfx with fps limit Patch

The 4gb patch is already applied to this executable as well. It enables multi-threading options by default (previously had to pass command line args to enable it, which would require a new launcher) and changes the memory cap on the executable to 3000MB from 1250MB for the texture cache, which means that less cpu cycles are spent recycling textures and instead they can sit comfortably in memory.