Stutter, fps drops, and the frame cap
Both the 2011 game and Remastered ship a 120fps cap that PCGamingWiki calls poorly implemented. Some physics stay at 60. Fullscreen can lock the display to 60Hz. Cutscenes were 30fps until a November 2021 change removed that lock.
What the pages agree on
Turn on triple-buffered vsync before you install anything. That is the first step both the wiki and the MixFix readme orbit. If the cap itself is the problem, SR.MixFix can lift it. The same tool is the one cited for engine audio dying at high frame rates, which is why the car-sound page points here too.
HDR brightness on Remastered has a slider bug measured in 50-unit jumps on PCGamingWiki. That is a picture bug, not a stutter bug, but people hit it while chasing “performance.” I am not building a GPU tier list. A 690-volume search for performance issues does not create a benchmark I can cite.
Nitro lag and spikes
Search logs bundle “nitro lag,” dropped frames, and spikes. I do not have a separate nitro-specific cause from two sources, so I file those words under this cap-and-vsync guidance instead of inventing a nitro bug.
FAQ
Should I unlock the frame rate?
Only after vsync. Unlocking without a fix is how the car-audio bug shows up. Read the MixFix page on the car-sound article before you drop an ASI file in.
Are cutscenes still 30fps?
PCGamingWiki says the original 30fps cutscene cap was removed in November 2021.
Sources
| Coverage | Status | Checked |
|---|---|---|
| Source groups cited on this page | 2 source groups | 2026-10-31 |
- PCGamingWiki — Remastered — pcgamingwiki.com · checked 2026-10-31
- GitHub — SR.MixFix — github.com · checked 2026-10-31