User talk:Taltharius: Difference between revisions
Taltharius (talk | contribs) mNo edit summary |
Taltharius (talk | contribs) mNo edit summary |
||
Line 18: | Line 18: | ||
* Using Radeon Chill and setting both "Min FPS" and "Max FPS" to 120. | * Using Radeon Chill and setting both "Min FPS" and "Max FPS" to 120. | ||
* (Not recommended) Using | * (Not recommended) Using Frame Rate Target Control to enforce a 120FPS limit. This is an older method than Radeon Chill, and often considered worse for input lag. | ||
== Method that only works with an Nvidia GPU == | == Method that only works with an Nvidia GPU == | ||
* Using the Nvidia Control Panel to set "Max Frame Rate" to 120. | * Using the Nvidia Control Panel to set "Max Frame Rate" to 120. |
Revision as of 14:50, 20 February 2024
In Red Faction: Guerrilla (both the Steam Edition and the Re-Mars-tered version), when the framerate exceeds 120FPS for too long, a rendering glitch that causes most of the terrain to vanish can occur in the Badlands. Harpoons fired from Marauder turrets will also frequently get stuck in the turret at framerates exceeding 120FPS.
Capping the framerate at 120FPS will prevent both of these problems from occurring, and may also prevent other subtle bugs/glitches from occurring.
One of several methods can be used to cap the game's framerate. They will be listed below.
Methods that should work with any GPU
- Using the Rivatuner Statistics Server to enforce a 120FPS limit.
- Setting the game's refresh rate to 120Hz, then enabling VSync. This only works if you have a 120Hz-capable monitor.
Methods that only work with an AMD GPU
- Using Radeon Chill and setting both "Min FPS" and "Max FPS" to 120.
- (Not recommended) Using Frame Rate Target Control to enforce a 120FPS limit. This is an older method than Radeon Chill, and often considered worse for input lag.
Method that only works with an Nvidia GPU
- Using the Nvidia Control Panel to set "Max Frame Rate" to 120.