Are you experiencing low FPS in Borderlands 2? Here’s what to do.
Borderlands 2 offers players exciting gaming experience. However, one issue that has been a blight on the game’s reputation is the issue of low FPS. And while this could easily be attributed to low-end, substandard, CPU, it’s been encountered on even high-end PCs.
To get around this issue, we’ve come up with some solutions.
How to Fix Borderlands 2 Low FPS Issue
A number of Borderlands 2 players have reported a drop in FPS, in the range of 30 to 40 (even <20). This constitutes a serious game lag, which consequently kills the fun of the game.
The cause of the error has been attributed to a cache error (in Steam), game configuration or system malfunction. In any case, below are some fixes you can try:
Note: Ensure that your system is standard enough to support the game.
- Verify cache’s integrity
To apply this fix;
- launch Steam and go the Library tab;
- right-click Borderlands 2;
- select Properties;
- go under the Local Files tab; and
- select Verify Integrity of Game Cache.
Relaunch the game and allow Steam to do its magic. If the low FPS issue persists, proceed with the next fix.
- Reset/Disable Physx
Physx is a GPU optimizer/accelerator, which is embedded in NVIDIA. However, it’s been known to have a reverse effect on CPU and FPS rate, and this is especially worse on low-end computers.
Therefore, it’s recommended to disable the feature if you’re experiencing low FPS.
To do this:
- navigate to NVIDIA Control Panel.
- click on Set Physx configuration > Select a Physx processor; and
- click on Apply.
Now, launch Borderlands 2; if the issue persists, proceed with the next fix.
- Run DirectX
This procedure has also been proven to speed up FPS in games. And its steps have been outlined below:
- Navigate to Steam’s installation folder for Borderlands 2:
- “C:\Program Files (x86)\Steam\steamapps\common\Borderlands 2\Binaries\Redist\DirectXRedistCutdown”.
- Locate the setup package (DirectX) tagged “DXSETUP.exe” and run it.
If the low FPS issue persists, you can try the next fix.
- Reconfigure entries
This is another proven fix, which entails resetting some entries under “WillowEngine”.
To apply this fix, simply open the “WillowEngine.ini” file and assign a uniform value to the entries below:
This should resolve the issue.
Was this helpful?