– Advertisement –

Ever since Valorant evolved from its beta phase in June 2020, Riot has left no stone unturned when it comes to polishing their FPS project with new content and regular game updates. In fact, today’s the day when Riot released Valorant, while the latter was still in its beta phase and had been previously dubbed as ‘Project A’.

But even after a year, sudden FPS drops would still continue to haunt the game developers and have been a nightmare to find a fix for. Irrespective of the fact that whichever hardware you use to make everything tick, occasional Frame rate issues are bound to arise. The recent deployments of Patches 2.05 and 2.06 have reportedly created havoc for some of the players as they have been facing the above-mentioned FPS drops while playing the game. 

Also Read | APEX goes animated, calls out VALORANT as “SHITLORANT”

Luckily Reddit user “mackfan” had come up with a fix that addressed the issue to be a part of your CPU affinity. The recent 2.06 patch might have triggered the game to use just 1 out of 4 available CPU cores and that might be the reason behind the constant hindering. Do follow the steps added below if you’re still facing the above-mentioned issue. Before you make the changes, do note that this fix has been quite old and doesn’t guarantee to resolve the same. But the developers have acknowledged the recent bugs and intend to fix them asap. 

How to fix the FPS issue in Valorant?

• Launch Valorant, and minimize the game
• Open your Task Manager (by right-clicking the Windows Task Bar and clicking “Task Manager”)
• Click “More Details”, and select the “Processes” tab
• Right-click Valorant, and select “Go to details”
• Right-click “VALORANT-WIN64-Shipping.exe”, and select “Set Affinity”
• A window will pop up showing which CPU threads are currently enabled for Valorant.
• If they’re all checked, this fix probably doesn’t apply to you. If there’s only a couple checked off and everything else is unchecked? Check the box “<All Processors>” and click OK.
• Repeat steps #5 and #6, but on “VALORANT.exe”