Recently, Deep Silver Volition released the latest instalment to the Saints Row franchise, Saints Row: The Third Remastered. Since the release, many players have complained about the bothersome FPS issues. One of such issues is the Saints Row: The Third Remastered capped FPS issue.
In some instances, this issue causes the scenes to render even below 60 FPS, while the cutscenes are capped at 30 FPS. While Deep Silver Volition is yet to address this issue, there is a solution that you can try to fix it. In this article, we will explain how you can fix the Saints Row: The Third Remastered capped FPS issue.
How To Fix Saints Row: The Third Remastered Capped FPS Issue?
On a few systems, the frame-rate drops to 22 FPS or even 15 FPS during cutscenes, and 67 FPS or even below 60 FPS in open-world environments. For a solution to the low FPS in cutscenes, you can read our How To Fix Saints Row: The Third Remastered Low FPS Cutscenes On PC article. If you’re facing FPS drops in open-world environments, follow the steps mentioned below to remove the FPS caps in Saints Row: The Third Remastered.
- Download and run Cheat Engine from here.
- Set the Executable, Writable and CopyOnWrite options to “Don’t Care“, and the memory scan option to SRTTR.exe.
- Disable the Fast Scan option and search for the value “0.00833333” as a float in rounded (extreme) mode.
- Select all values.
- Disable the Fast Scan option and search for the value “0.03333333
"as a float in rounded (extreme) mode. - Select all values.
- Disable the Fast Scan option and search for the value “0.01666666” as a float in rounded (extreme) mode.
- Select all values.
- Disable the Fast Scan option and search for the value “0.00833333
"as a double in rounded (extreme) mode. - Select all values.
- Disable the Fast Scan option and search for the value “0.01666666” as a double in rounded (extreme) mode.
- Select all values.
- Set all the values to the below-mentioned 1/FPS values for your desired FPS;
- “0.00694444” for 144 FPS (floats).
- “0.00277777” for 360 FPS (floats).
- “0.00256410” for 390 FPS (floats).
- “0.0069444444444444” for 144 FPS (doubles).
- “0.0027777777777777” for 360 FPS (doubles).
- “0.0025641025641026” for 390 FPS (doubles).
If you encountered a crash past the title screen with this solution, try only selecting values closer to the actual 1/FPS value instead of all the given values (for instance, “0.01666666754” rather than “0.01666666567)”. We also highly recommend using the in-game triple-buffered V-Sync for better frame-pacing due to the implementation of FPS caps. This will, however, decrease the input latency for lower frame rates.